[00:37] <kees> isn't apport supposed to be enabled in natty?
[00:48] <crimsun> AFAIK, yes
[01:05] <barry> james_w: i just pushed another branch (test-fixes) which fixes all the tests for me.  there might be some conflict between that and the envar branch, but if you review then separately, and approve them, i'll resolve any conflicts and merge them to trunk.
[01:15] <james_w> barry, this feels wrong to me somewhat. Shouldn't we just change things such that install installs the backends too?
[01:15] <james_w> barry, the __file__ stuff was to support running uninstalled, but that's now not possible, correct?
[01:16] <james_w> ah "develop" is possible
[01:28] <james_w> barry, reviewed, thanks
[01:50] <achiang> hm, how do i update the sources.list inside of a pbuilder?
[02:11] <DasEi> I've got Aurorax on my back in #ubuntu who seems to be up in writing a devicedriver as novice, , wee just installed build-essential and he seems concerned, I'll send him over, couldn't tell him he need more experience
[02:17] <DasEi> seems either I've been pulled forward, or trolled, nvm, quite now :)
[10:58] <mdz> bdrung: bug 637020 looks pretty straightforward; ubuntu-iso is a trivial wrapper around isoinfo and doesn't attempt to parse any command line options
[10:59] <mdz> it should just exit nonzero rather than crash
[11:00] <mdz> a --help option could be added, but it would be minimal (there is already a man page which explains the lack of options)
[11:28] <bdrung> mdz: just exit nonzero or should it print an error message? if yes, what should it print?
[11:31] <mdz> bdrung: currently it raises an exception with the error output from isoinfo. I think it should just print that to stderr (or let isoinfo do it if it will behave), and exit nonzero, instead of raising an exception
[11:33] <mdz> should be a two-liner, replace the "raise Exception, stderr" with "sys.stderr.write(stderr)\nsys.exit(pipe.returncode)"
[11:59] <bdrung> mdz: done
[11:59] <mdz> bdrung: awesome, thanks!
[12:00] <bdrung> mdz: trivial :)
[12:00] <mdz> if I have some time I'll add a simple option parser which responds to --help
[12:00] <mdz> it's not implausible that one day it will grow more functionality
[12:00] <mdz> it would be nice to be able to extract the filesystem manifest, for example
[12:01] <bdrung> mdz: optparse is your friend - look at sponsor-patch for example
[12:04] <mdz> bdrung: yeah, it should be simple enough. I'm just trying to spend my weekend responding to all of the person emails I haven't replied to during the week ;-)
[12:10] <cjwatson> mdz: sounds thrilling ...
[12:10]  * cjwatson has an exciting weekend of housework lined up, and so far today has been procrastinating it by cleaning house in the archive instead
[15:05] <ari-tczew> does anybody know why pbuilder-dist doesn't work longer with ~/pbuilder?
[15:06] <tumbleweed> ari-tczew: do you have the latest version? (You're not running into the sudo -E issue?)
[17:14] <ebroder> bdrung: I'll check out those bugs
[17:14] <bdrung> ebroder: i am on bug #691893
[17:14] <ebroder> bdrung: Though I'm not sure I think it's a good idea to have a -y option
[17:15] <bdrung> ebroder: i am not sure about the other bug reports.
[17:15] <bdrung> ebroder: what sponsor-patch does: it ask to confirm the upload if the upload target is "ubuntu"
[17:15] <bdrung> otherwise it doesn't ask
[17:15] <ebroder> bdrung: Hmm, ok
[17:16] <bdrung> ebroder: i think we don't need to ask if we build the package before uploading
[17:18] <ebroder> bdrung: I also think I'm going to add a -S/--suffix option for the version number suffix (after the ~maverick1 bit or whatever), so you can do ~ppa2 uploads
[17:18] <bdrung> ebroder: good idea
[17:18] <ebroder> Because right now I have a backport in a PPA that I want to submit a rebuild for
[17:21] <ebroder> bdrung: For bug #691897, the .orig.tar.gz has to be in the destination release already, right? Is there any way I can test for that?
[17:22] <ebroder> Like, PPAs won't pull the orig source from other pockets in the PPA or something, right?
[17:22] <bdrung> ebroder: look at sponsor-patch
[17:22] <bdrung> ebroder: yes
[17:22] <ebroder> bdrung: Oh, really? Huh
[17:23] <ebroder> bdrung: Right, sponsor-patch does the standard check - does the last changelog version and this one have the same version, but I can't do that with backportpackage, because the last changelog entry was from a different release than the one I'm about to upload to
[17:24] <ebroder> *same upstream version component
[17:25] <bdrung> ebroder: ok, you have to look at the dsc file and check if these files are available in launchpad
[17:26] <bdrung> ebroder: make this check reusable by sponsor-patch
[17:27] <ebroder> bdrung: Sure
[17:30] <ebroder> bdrung: Do you mind if I push a fix for the bug in 691862 comment 8 (the "global name opts is not defined") directly back to lp:ubuntu-dev-tools, since the fix is simple and obvious?
[17:31] <bdrung> ebroder: i wouldn't mind, but i have already pushed the fix :P
[17:31] <ebroder> bdrung: Oh, good. Thanks
[17:32] <bdrung> ebroder: should i release the current state of u-d-t?
[17:33] <ebroder> bdrung: If you don't mind holding up until tomorrow, I was planning to spend a few hours today working through my todo list
[17:33] <bdrung> ebroder: ok, i'll wait then
[17:36] <ebroder> bdrung: To deal with bug #691896, I'm thinking of changing that to erroring out "if not opts.workdir and not opts.upload". If you're uploading, it doesn't matter that workdir isn't set and it's going to delete the workdir when it's done. If you've set workdir, then you're not going to lose your build products
[17:36] <ebroder> bdrung: This will also solve the issue that right now if you run with -b and not -u or -w, you never get a chance to see the results of the build
[17:36] <ebroder> (which ari-tczew complained about last weekend)
[17:37] <bdrung> ebroder: yes, good idea
[17:39] <ari-tczew> ebroder: last weekend? huh, time is hurry up
[17:39] <ebroder> I'm pretty sure that was when you last tested it
[17:41] <ari-tczew> I don't doubt it, just afraid how quickly is time. (:
[17:42] <ebroder> bdrung: Does it seem reasonable to change the arguments to -u -U ppa:broder/ppa instead of just -u ppa:broder/ppa? That way BACKPORTPACKAGE_UPLOAD -> -U argument, and setting BACKPORTPACKAGE_UPLOAD doesn't force you to always upload when you run backportpackage
[17:43] <bdrung> ebroder: you want "-u" for upload and "-U" for upload target?
[17:44] <ebroder> bdrung: Yes
[17:44] <bdrung> ebroder: and --update?
[17:44] <ebroder> bdrung: Oh, whoops. Too many 'u' options
[17:45] <ebroder> How about -u for upload and -t for upload target?
[17:45] <bdrung> ebroder: better :)
[17:45] <bdrung> ebroder: i have a better idea.
[17:46] <bdrung> "-u foobar" for uploading to foobar. "-u" for uploading to BACKPORTPACKAGE_UPLOAD
[17:46] <ebroder> bdrung: Can't do that with optparse
[17:47] <ebroder> bdrung: (And rightfully so, because short options with optional arguments theoretically can't be parsed consistently. If I pass -u -s, is that -u=-s or two different options?)
[17:48] <bdrung> it should be consistent with sponsor-patch
[17:52] <ebroder> bdrung: So I guess -u for the target and...something else for "upload to BACKPORTPACKAGE_UPLOAD"?
[17:53] <bdrung> ebroder: what speaks against always uploading to BACKPORTPACKAGE_UPLOAD?
[17:54] <ari-tczew> tumbleweed: I have latest pbuilder. I don't know about sudo -E issue.
[17:55] <ebroder> bdrung: The logic is that the "upload to BACKPORTPACKAGE_UPLOAD" option is actually a "go and *do* the upload" option, and gets set automatically if you specify a target on the command line
[17:57] <bdrung> ebroder: i don't get it.
[17:57] <ebroder> bdrung: There's --upload-target and --do-upload. If you just say --do-upload it uploads to BACKPORTPACKAGE_UPLOAD. If you say --upload-target it sets --do-upload automatically
[17:59] <bdrung> ebroder: is there a usecase for not uploading the package if BACKPORTPACKAGE_UPLOAD is set?
[17:59] <ebroder> bdrung: If I do a local build?
[18:00] <bdrung> ebroder: ok
[18:00] <bdrung> ebroder: what about a negative option. "-d, --dry-run" for not doing an upload
[18:02] <ebroder> bdrung: Maybe
[18:05] <bdrung> ebroder: what do you think if i would change the question from "Do you want to upload this to ppa:bdrung/backports? [Y/n]" to "Do you want to upload adblock-plus 1.3.2-1~maverick1~ppa1 to ppa:bdrung/backports [Y|n]?"?
[18:06] <ebroder> That's fine, although I was going to drop the prompt if the upload target isn't ubuntu
[18:07] <bdrung> ebroder: or do you prefer "Do you want to upload adblock-plus_1.3.2-1~maverick1~ppa1_source.changes to ppa:bdrung/backports [Y|n]?"?
[18:08] <bdrung> ebroder: but having the prompt is nice (to check if the backported version is the right one and the target is correct)
[18:08] <ebroder> bdrung: Ok, I guess I can do a -y option instead
[18:08] <ebroder> Anyway, I have no preference for the form of the prompt
[18:09] <bdrung> ebroder: and the -y options should have no affect if you upload to ubuntu
[18:22] <bdrung> ebroder: pushed r845
[18:29] <bdrung> ebroder: shouldn't "Please check the package in file://%s carefully" be before the upload?
[18:30] <ebroder> It is, isn't it?
[18:30] <bdrung> ebroder: nope. it's before building the package
[18:31] <bdrung> ebroder: idea: change "Please check the package in file://%s carefully! Do you want to upload <package> <version> to %s" to "Please check <package> <version> in file://%s carefully! Do you want to upload the package to %s"
[18:32] <ebroder> bdrung: Yes, that's fine
[18:37] <bdrung> ebroder: pushed
[18:42] <tumbleweed> ari-tczew: I was asking about th elatest ubuntu-dev-tools
[18:42] <tumbleweed> ari-tczew: the issue I'm talking about is that sudo used to allow environment through, but recently changed behavior, so -E had to be added in pbuilder-dist
[18:47] <ari-tczew> tumbleweed: ubuntu-dev-tools also up-to-dated
[18:47] <tumbleweed> ari-tczew: so what actually is the problem?
[18:49] <ari-tczew> tumbleweed: pbuilder-dist doesn't look for base in ~/pbuilder
[18:49] <ari-tczew> this is my problem
[18:50] <ari-tczew> I'm asking whether is there a known problem? if not, probably I have to report a bug
[18:51] <tumbleweed> I suspect the problem is with yoru local configuration, but if you can't find it, please report a bug, yes
[18:52] <ari-tczew> tumbleweed: I didn't change anything.
[18:52] <ari-tczew> anyway, where can I fix config?
[18:53] <tumbleweed> I mean .pbuilderrc
[18:53] <tumbleweed> oh, and check the permissions of ~/pbuilder
[19:14] <ScottK> tumbleweed:  If sudo stopped letting the environment through, that would explain exactly the result that ari-tczew is seeing.
[19:14] <tumbleweed> ScottK: that should have been dealt with in the last u-d-t upload
[19:14] <ScottK> OK
[19:15] <tumbleweed> ScottK: btw, the postgrey issue is that the DD can't seem to get his orig.tar.gz to match the one in th edebian archive, so his uploads get rejected. Prodded him.
[19:15] <ScottK> tumbleweed: OK.  This looks like something then that we ought to just fix in Natty so we can SRU Lucid/Maverick ASAP.
[19:16] <ScottK> As is it's breaking uprades from Hardy.
[19:16] <tumbleweed> aah, right. shall I do it?
[19:28] <tumbleweed> ebroder: backportpackage isn't listed in debian/copyright
[19:29] <ari-tczew> tumbleweed: ok, what have I to do to get pbuilder working?
[19:29] <tumbleweed> ari-tczew: are you on maverick?
[19:29] <ari-tczew> tumbleweed: nope, natty
[19:30] <tumbleweed> ari-tczew: please pastebin output, .pbuilderrc, and ls -l ~/pbuilder
[19:30] <bdrung> tumbleweed: are you volunteering to update and convert d/copyright to DEP-5? ;)
[19:30] <ScottK> tumbleweed: Yes.  Please do it (postgrey).
[19:31] <tumbleweed> bdrung: I just considered doing that :P
[19:31] <ari-tczew> tumbleweed: http://paste.ubuntu.com/545367/
[19:31] <tumbleweed> but backportpackage doesn't contain a copyright notice, only a GPL-2
[19:32] <ari-tczew> tumbleweed: http://paste.ubuntu.com/545369/
[19:32] <bdrung> ebroder: do you allow later versions of GPL?
[19:33] <tumbleweed> ari-tczew: that .pbuildrrc is (hopefully) redundant, if you use pbuilder-dist
[19:33] <ari-tczew> tumbleweed: yes, I prefer to use pbuilder-dist. what's next?
[19:34] <tumbleweed> ari-tczew: the actual errors you are seeing
[19:35] <ari-tczew> tumbleweed: sorry, probably I'm blind
[19:35] <ari-tczew> (dunno what's wrong, I didn't change anything)
[19:35] <tumbleweed> I hate those bugs
[19:36] <bdrung> tumbleweed: pbuilder-dist shouldn't be negatively impacted by an pbuilderrc config
[19:36] <bdrung> instead everything should be passed as command line parameter to pbuilder
[19:36] <tumbleweed> bdrung: no, it shouldn't, the command line options should trump the config file
[19:37]  * bdrung nods
[19:37] <bdrung> therefore ari-tczew's problem should be considered as bug
[19:38] <ari-tczew> bdrung, tumbleweed: so, until problem is not fixed, can't I use pbuilder?
[19:38] <ari-tczew> so merges have to wait longer
[19:39] <tumbleweed> ari-tczew: please file a bug, and include the command you are running and output
[19:39] <bdrung> ari-tczew: doesn't moving (or deleting) your pbuilder config file help?
[19:40] <ari-tczew> bdrung: .pbuilderrc?
[19:40] <bdrung> ari-tczew: yes
[19:41] <ari-tczew> bdrung: the same error
[19:41] <bdrung> ari-tczew: then the problem is independent from the pbuilder config file.
[19:41] <bdrung> ari-tczew: file a bug!
[19:41] <ari-tczew> bdrung: target?
[19:41] <tumbleweed> ari-tczew: ubuntu-dev-tools in ubuntu
[19:45] <ari-tczew> bdrung, tumbleweed: what a specific number! bug 691999
[19:45] <tumbleweed> ari-tczew: run it without sudo :)
[19:45] <bdrung> ari-tczew: does it work without sudo?
[19:47] <ari-tczew> tumbleweed, bdrung: hmm... working. trying to build a package
[19:47] <ari-tczew> I gave you a output command! ;)
[19:47] <ari-tczew> ah, not, sorry :P
[19:48] <tumbleweed> no that's a definite usability bug that should be fixed
[19:48] <ari-tczew> please don't hang dogs on me, I always have these aliases with sudo
[19:55] <ebroder> bdrung: I'd prefer to leave backportpackage GPLv2, not v2+
[19:57] <tumbleweed> ebroder: noted, I'll do a dep5ification (bug 692003)
[19:59] <TheLE> Hey I'm having a bit of an issue. Every time I create an About Dialog (built from GLADE->GtkBuilder) from an event on my main window I also get another instance of my main window for no reason.
[20:01] <TheLE> it originates from the gtk_builder_add_from_file(..) function call inside of my About Dialog (the one responsible for retrieving the dialog's UI from the XML file
[20:02] <TheLE> is there a restriction on the number of times that I can call this function during execution? or after the gtk_main() function has been called?
[20:03] <ebroder> TheLE: This channel is more for development of Ubuntu itself than development of apps on Ubuntu. You might have better luck in #ubuntu-app-devel
[20:03] <TheLE> ebroder: thanks
[20:08] <ebroder> tumbleweed: What did I do wrong in backportpackage's header? Oh, I guess I forgot a copyright statement?
[20:09] <tumbleweed> yes
[20:09] <ebroder> tumbleweed: Ok, I'll add one in my next MP
[20:38] <bdrung> ebroder: what do you have against v2+?
[20:39] <ebroder> bdrung: I'm not wild about v3. And regardless of what v3 itself says, I don't like the idea of giving another organization the ability to change the rules of my code
[20:39] <bdrung> ebroder: then "v2 or v3" would be fine?
[20:40] <ebroder> bdrung: Yeah, I'd be OK with that
[20:41] <ebroder> bdrung: I can upgrade it to 2 or 3, but for what it's worth that'd be a new license for dev-tools (right now there's v2, v3, v2+, v3+, but no v2orv3)
[20:44] <bdrung> ebroder: what a mess with v2, v3, v2+, v3+
[20:44] <bdrung> let's move to ISC ;)
[20:45] <tumbleweed> indeed, it's make the dep5 task rather nasty
[20:46] <tumbleweed> I'll have to work out who has touched each file
[20:46] <ebroder> I respect the need for open-source licenses, but I tend to find everything about licensing annoying
[20:46] <bdrung> ebroder: that's why i prefer ISC - it's simple, short and isn't versioned
[20:47] <bdrung> and it's compatible to everything
[20:47] <ebroder> bdrung: Yeah, I license a lot of things MIT because I can fit it all on a screen
[20:47] <bdrung> ebroder: ISC is a little bit shorter than MIT
[20:54] <ebroder> bdrung: Ugh, I'm trying to code up the heuristic for whether to use -sa or -sd. It looks like it's going to be complicated
[20:55] <ebroder> I guess I need to sort the files in the source package into .dsc, debian diff, orig files
[20:55] <ebroder> And I need to deal with source format 3 which can have multiple orig files, and they're not always .orig.tar.gz anymore
[20:55] <ebroder> On the plus side, there will probably be several useful library functions for ubuntutools that fall out of this
[21:02] <bdrung> ebroder: look at my download logic
[21:02] <ebroder> bdrung: Where?
[21:03] <bdrung> mom
[21:03] <ebroder> bdrung: Where do I find the source for mom?
[21:04] <bdrung> mom = give me a moment
[21:04] <ebroder> Ah, ok
[21:05] <bdrung> ebroder: it's in syncpackage
[21:05] <bdrung> line 242
[21:06] <bdrung> ebroder: you might want do use dsc_getfiles(dscurl)
[21:10] <bdrung> ebroder: 'if answer != "yes":' -> 'if answer == "no":'
[21:11] <ebroder> bdrung: Ok, sure
[21:12] <bdrung> ebroder: you shouldn't mention features implemented in the not yet released backportpackage
[21:12] <ebroder> bdrung: I was mostly doing it for the LP closers. Should I drop the closers entirely?
[21:13] <bdrung> ebroder: yes (just bzr ci --fixes lp:123456) and i'll close the bugs manually once merged
[21:13] <ebroder> Ok
[21:14] <ebroder> bdrung: Since the --fixes is already in the branch history, I don't actually need to do anything, right? Just drop the changelog entries?
[21:14] <bdrung> yes
[21:14] <bdrung> (if you used debcommit)
[21:14] <ebroder> bdrung: Fixed
[21:16] <bdrung> is that philosophical? "You say goodbye, and I say hello."
[21:16] <ebroder> bdrung: Beatles reference :)
[21:17] <ebroder> bdrung: http://www.youtube.com/watch?v=Qf2S7kKLtEQ
[21:17]  * bdrung is already watching on youtube.
[21:19] <bdrung> ebroder: is your branch ready for the merge?
[21:19] <ebroder> bdrung: Sure
[21:25] <bdrung> ebroder: merged and pushed
[21:25] <ebroder> bdrung: Cool, thanks
[21:25] <bdrung> ebroder: is there anything left that you want to do?
[21:25] <ebroder> bdrung: Not particularly urgently. If you want to release, that's OK with me
[21:25] <ebroder> bdrung: Though I can't promise I won't have new features for you by tomorrow
[21:27] <bdrung> ebroder: i vote for "release early, release often"
[21:27] <ebroder> So let's say I have an empty PPA. I create a new Debian revision of a package currently in the Ubuntu archive, and I build my source package with debuild -sd. Will soyuz copy the orig.tar.gz from the archive to my PPA, or will it error out?
[21:27] <ebroder> bdrung: Works for me
[21:27] <bdrung> ebroder: it will error out
[21:27] <ebroder> bdrung: Cool. That makes the -sa/-sd detection much simpler
[21:28] <bdrung> ebroder: yes, if target = ubuntu ==> check if it's in the official archive
[21:28] <bdrung> if target = ppa: check if in specific ppa
[21:28] <ebroder> bdrung: I was going to get an lplib object for the archive and then I can use the same code
[21:29] <bdrung> ebroder: what should the lplib object do?
[21:34] <ebroder> bdrung: Something roughly like http://pastebin.com/ALGi0DtX
[21:35] <bdrung> ebroder: "orig = set(['all', 'orig', 'files']"?
[21:35] <ebroder> bdrung: It's pseudocode
[21:35] <ebroder> bdrung: ...but it's Python, so it's almost-functional pseudocode :-P
[21:36] <bdrung> ebroder: what should that do?
[21:36] <ebroder> bdrung: It will get the list of every source file currently in the archive for the source package "whatever"
[21:36] <bdrung> orig = get_orig_files_from_dsc(dsc_filename)
[21:37] <ebroder> Yeah, basically
[21:37] <bdrung> ebroder: i think it should work that way. go ahead :)
[21:39] <ebroder> bdrung: Here's what it actually looks like: http://pastebin.com/D4GZQdm8
[21:39] <bdrung> tumbleweed: how long will it take for you to fix bug #692003? should i wait for it or should i upload 0.108?
[21:42] <tumbleweed> bdrung: hoping to finish it tonight. I went down the rabbithole of scripting licensecheck + bzr output > dep5
[21:42] <bdrung> ebroder: great. can we have an object that have a function for that? one object for the ubuntu archive and one for each ppa?
[21:42] <ebroder> bdrung: Yeah, that's what I'm planning to do
[21:42] <ebroder> bdrung: But don't block the release for it - I'm not sure I'll finish it today
[21:43] <bdrung> tumbleweed: tonight in which timezone?
[21:43] <tumbleweed> same as you, GMT+2
[21:44] <bdrung> tumbleweed: ok, i will do the release before i go to bed. either you make it or it will end up in the next release.
[21:44] <tumbleweed> fine with me
[21:45] <bdrung> ebroder: "Package failed to build; aborting" is a bad error message.
[21:45] <bdrung> ebroder: should the sentences ends with fullstops or exclamation marks?
[21:45] <ebroder> bdrung: I have no preference; whichever you prefer
[22:08] <bdrung> ebroder: please review r851
[22:09] <ebroder> bdrung: ACK
[22:10] <bdrung> ebroder: and r852
[22:11] <bdrung> ebroder: re r851: do you have a better idea for having a common error message in builder.py?
[22:11] <ebroder> bdrung: ACK r852
[22:11] <ebroder> bdrung: I think what you did is fine
[22:14] <bdrung> tumbleweed: re bug #691999: i think you should abort instead of just printing a warning. running pbuilder-dist as root will create files owned by root in your home directory.
[22:16] <tumbleweed> bdrung: no it won't create them in your home directory, it'll use /root/pbuilder
[22:17] <tumbleweed> that's why I went for a warning, it is valid to run it as root, just probably not what you want
[22:18] <bdrung> tumbleweed: nope. "sudo pbuilder-dist natty update" will create a ~/pbuilder directory owned by root
[22:18] <ebroder> tumbleweed: sudo doesn't change $HOME unless you pass -H
[22:18] <ebroder> Maybe error out if os.stat(os.environ['HOME']).st_uid != os.getuid() ?
[22:19] <tumbleweed> err, http://paste.ubuntu.com/545401/
[22:20] <tumbleweed> aah, depends on whether or not you have env_reset
[23:03] <mawst> So what's the deal, why is gstreamer fscking retarded, choking etc all the time on common formats (xvid, mkv) but xine works flawlessly with them, and now there's no option to usethe xine backend on totem?
[23:23] <bdrung> tumbleweed: status?
[23:26] <tumbleweed> bdrung: almost there
[23:27] <bdrung> tumbleweed: did you implement the "os.stat(os.environ['HOME']).st_uid != os.getuid()" check?
[23:28] <tumbleweed> err no, I'll do that and make it fail if true, otherwise just warn
[23:29] <bdrung> tumbleweed: no, it's the other way around
[23:29] <bdrung> ups
[23:29] <tumbleweed> yeah, that's what I mean :)
[23:29] <bdrung> if unequal, fail. if equal, warn
[23:29] <bdrung> i oversaw the '!='
[23:40] <bdrung> tumbleweed: look at your commit message :D
[23:42] <tumbleweed> grr, one sec
[23:44] <bdrung> tumbleweed: your commit message is still broken. :D use '' insead of "" if you don't want $HOME replaced.
[23:44] <tumbleweed> hehe
[23:51] <bdrung> tumbleweed: debian/copyright isn't DEP-5
[23:52] <tumbleweed> bdrung: yeah, something got mixed up due to my branch juggling (that's why I screwed up changeleg entries too)
[23:52] <bdrung> tumbleweed: and long indentation is preferred (look at the dep5 examples)
[23:55] <tumbleweed> bdrung: I can't find my final version, it got lost in the juggling, if you still want to upload tonight, don't wait for it
[23:56] <bdrung> tumbleweed: ok, i will release the current version. let's get the copyright update into the next upload (probably this year).
[23:59]  * tumbleweed curses himself for trying to work fast on more than one thing