#dput-ng

Thanks, y'all!

Big release notes since 1.0: We've got a new list -- [[email protected]](http://lists.alioth.debian.org/pipermail/dput-ng-maint/) -- feel free to subscribe! 1.3: * Avoid failing on upload if a pre/post upload hook is missing from the Filesystem. * Fix "dcut raises FtpUploadException" by correctly initializing the uploader classes from dcut (Closes: #696467) 1.2: * Add bash completions for dput-ng (Closes: #695412). * Add in a script to set the default profile depending on the building distro (Ubuntu support) * Fix a bug where meta-class info won't be loaded if the config file has the same name. * Add an Ubuntu upload target. * Added .udeb detection to the check debs hook. * Catch the correct exception falling out of bin/dcut * Fix the dput manpages to use --uid rather then the old --dm flag. * Fix the CLI flag registration by setting required=True in cancel and upload. * Move make_delayed_upload above the logging call for sanity's sake. * Fix "connects to the host even with -s" (Closes: #695347) Thanks to everone who's contributed! 7 Bernhard R. Link 4 Ansgar Burchardt 3 Luca Falavigna 2 Michael Gilbert 2 Salvatore Bonaccorso 1 Benjamin Drung 1 Gergely Nagy 1 Jakub Wilk 1 Jimmy Kaplowitz 1 Luke Faraone 1 Sandro Tosi This has been your every-once-in-a-while dput-ng update. We're looking for more code contributions (to make sure everyone's happy), doc updates (etc) or ideas.

Yeah, wait, what? No, really! I took a look through [clojure-py](https://github.com/halgari/clojure-py), and found out something pretty rad. In order to get clojurepy scripts to load other clojurepy, it had to shim out and add a new importer for clojure scripts. What this *really* means, is that you can import Clojure from Python, which is pretty sweet. I abused the internals here, and added it to [dput-ng](http://dput-ng.debian.net) as a quick hack. Basically, I just had to `import clojure.main`, and let the main function set up the sys shim. I would set it up in dput, but I'd have to import that module anyway. Remember, when doing this, the namespace (`(ns ...)`) needs to match the filename. So, I present the first Clojure hook for dput-ng: ; Copyright (c) Paul R. Tagliamonte , 2012, under the ; terms of dput-ng itsself. (ns clojtest (:require dput.core dput.exceptions)) (defn log [x] ; for debug output (.debug dput.core/logger x)) (defn dput-checker [changes profile interface] (cond (>= (-> changes (.get "maintainer") (.find "[email protected]")) 0) (throw (dput.exceptions/HookException. "Maintainer's Arno. Aborting upload")) :else (log "Nah, it's not arno, we're good"))) This, of course, checks if the maintainer is [Arno](http://daemonkeeper.net/), and throws a fit if it is. [Gist is over on gist.github](https://gist.github.com/4281134). After, [Algernon](http://asylum.madhouse-project.org/) added his own checker, which throws a fit if you have a package in the B-Ds that you aught to not use (such as dpatch) ; Copyright (c) Gergely Nagy , 2012, under the ; terms of dput-ng itself. (ns bd-blacklist (:require dput.core dput.exceptions dput.dsc)) (defn prune-build-deps "Prune a string representation of the build-depends so that only a list of packages remain." [bd-string] (map #(first (-> % (.strip) (.split " "))) (.. bd-string (split ",")))) (defn has-blacklisted? "Given a dsc file and a blacklist, check if any of the build-depencencies are in that list. Throws an error if there are matches." [dsc-file blacklist] (let [dsc (dput.dsc/parse_dsc_file dsc-file) build-deps (prune-build-deps (.. dsc (get "build-depends")))] (if-let [bad-bd (some blacklist build-deps)] (throw (dput.exceptions/HookException. (str "Blacklisted build-dependency found: " bad-bd))) (-> dput.core/logger (.trace "Build-Dependencies do not have anything on the blacklist"))))) (defn blacklist-checker "Checks whether the dsc has blacklisted build-dependencies, ignores the check when no dsc is to be found." [changes profile interface] (if-let [dsc-file (.. changes (get_dsc))] (has-blacklisted? dsc-file (set (get profile "bd-blacklist"))) (-> dput.core/logger (.trace "No .dsc found, build-dependencies cannot be checked")))) You can check that out in the [git tree](http://anonscm.debian.org/gitweb/?p=collab-maint/dputng.git;a=blob;f=examples/hooks/bd-blacklist/code/bd-blacklist.clj;hb=HEAD) Hacks welcome!

I've been working (although; slowly) on dput-ng. I need to finish `dirt` (a tool to modify the config files, sorta like how `git` works at times), but it's otherwise mostly in the state it will be in upon our upload to unstable. good-intentioned co-maintainers and contributors are welcome. Code's in collab-maint, be sure to run big changes through us over in `#torabora` on `irc.oftc.net`. I've also spent some time on [debuild.me](http://debuild.me/), and I've written out most of the krufty bits, more changes to come. If anyone has ARM hardware suggestions, I'm open to them, but I'm thinking (from some `debian-arm` advice) that it'd be best to wait for the v8 goodies to drop. Godspeed!

Hello, World! [Arno](http://daemonkeeper.net/) and I have been in the middle of a 3 week long quest to [rewrite dput](http://people.debian.org/~paultag/dput-ng/). We feature tons of improvements over the old dput, such as: * Enhanced and configurable pre-upload checks baked in and enabled by default to make sure you do not accidentally upload a package which is not suitable for archives * Support for external third party checkers * Fragmented configuration, to allow external packages to include checks. * Real SFTP support * Dynamic checker behavior depending on host / profile * Support for all checksums, Debian Changes files support (MD5, SHA1, SHA256) * Full dcut support, including Debian Maintainer permission handling Support for even core features are treated as plugins, so derivative distributions should be able to add features without maintaining a patch against dput (current situation). In addition, I've implemented some show-ey post-upload hooks, such as a Twitter plugin. Here's how it's defined: import twitter import json import os def tweet(changes, profile, interface): tweet = "I've just uploaded %s/%s to %s's %s suite #debian" % ( changes['Source'], changes['Version'], profile['name'], changes['Distribution'] ) if len(tweet) > 140: tweet = tweet[:140] obj = json.load(open(os.path.expanduser("~/.twitter.json"), 'r')) t = twitter.Api( consumer_key=obj['consumer_key'], consumer_secret=obj['consumer_secret'], access_token_key=obj['oath_token'], access_token_secret=obj['oath_secret'] ) t.PostUpdates(tweet) This file is placed in `~/.dput.d/scripts`, as `tweet.py`, and the plugin def file is placed in `~/.dput.d/processors` (since it's a post-upload processor), which looks like: { "name": "Tweet after an upload.", "path": "tweet.tweet" } I know this sounds confusing, but it's actually quite nice. Check out the [plugin in action](https://twitter.com/paultag/status/257981606139133954) Feedback, and contributors more then welcome! Documentation is at [dput.rtfd.org](http://dput.rtfd.org). It's all a bit pre-beta at the moment, but the authors are using it for all their uploads, and should be stable for users who don't mind a bit of breakage. We've filed the ITP, and updates on it & and upload will follow shortly. We're just weeding out some final major issues. Should be stable enough for general use in the next 30 days or so.