[00:31] <bdrung> Laney: not sortable sponsor queue -> adblock plus?
[00:31] <Laney> yeah i do have that on
[00:31] <Laney> seems weird though
[00:33] <bdrung> Laney: whitelist everything on this page
[00:33] <bdrung> micahg: mozilla package set -> ubufox sponsoring (3 bugs)
[00:33] <Laney> that works
[00:33] <Laney> cheers
[00:36] <micahg> bdrung: only 1 I can do
[00:36] <micahg> and it's not really complete
[00:36] <bdrung> micahg: start small
[00:37] <micahg> I'll look at it again
[00:37] <bdrung> tumbleweed: i raised the bar by ~ 5 :)
[00:38] <micahg> bdrung: the script doesn't take into account which series one can upload to
[00:47] <micahg> bdrung: I haven't done it because chrisccoulson is planning an upload of ubufox, so I left it for him
[01:17] <micahg> bdrung: PM?
[02:08] <highvoltage> moo
[02:15] <micahg> highvoltage: builders empty for grazing packages :)
[02:23] <highvoltage> I have some packages to fix but I don't have the energy for them now :)
[02:23] <ajmitch> it's not like it's late there, right?
[02:35] <highvoltage> ajmitch: 21:35, but I have to be up at 4:00 to take someone to the airport
[02:36] <highvoltage> (in eastern canada atm, not south africa :) )
[02:40] <ajmitch> highvoltage: aha :)
[02:48] <zooko> Greetings, people of #ubuntu-motu!
[02:50] <zooko> We Tahoe-LAFS hackers moved up the release date of Tahoe-LAFS v1.8.0 to Wed, Aug 11 in the hopes of getting it included in Maverick.
[02:59] <ajmitch> zooko: still no progress on getting them into debian as well?
[03:10] <zooko> ajmitch: no, no recent progress on getting Tahoe-LAFS into Debian.
[03:20] <zooko> ajmitch: but Tahoe-LAFS v1.8.0 offers some pretty dramatic performance, feature, and bugfix improvements over the v1.6.1 that is currently in Ubuntu.
[03:23] <zooko> ajmitch: http://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/NEWS
[07:20]  * Rhonda cries out loud, https://bugs.launchpad.net/bugs/600100
[07:20] <ajmitch> invalid?
[07:20] <Rhonda> I *explicitly* asked about wether it might go in through a stable release update!
[07:21] <ajmitch> confusion reigns
[07:21] <Rhonda> And was told that there isn't a way. No I receive an invalid for the backports request?!
[07:21] <Rhonda> Sorry, but this is winding me up. :/
[07:21] <ajmitch> bugs aren't serious enough for a SRU, and because they're bugs, no backports
[07:21] <ajmitch> yay for worshipping the process
[07:22] <Rhonda> I would be *more* than happy to have it go in through a SRU, but then, being told that it won't happen I do the other way that makes it possible to offer it, and now this.  :'(
[07:22] <ajmitch> I can understand why you'd be annoyed
[07:23] <Rhonda> And wouldn't a SRU has to go through a bugreport in launchpad, too?
[07:24] <ajmitch> yes
[07:24] <Rhonda> Why not reassign it appropriately instead of marking it invalid, then?
[07:24] <ajmitch> and requires eyballing of the diff
[07:24] <Rhonda> This is so shooting the effort down the drain. :(
[07:24] <ajmitch> because it would still be an invalid task in lucid-backports
[07:24] <Rhonda> Ah, alright.
[07:24] <ajmitch> same bug can be used, just needs a task against wesnoth in ubuntu, targetted to lucid
[07:25] <ajmitch> & why not 1.8.3? :)
[07:30] <Rhonda> Right, should get updated to that. Thanks for the reminder.
[07:31] <Rhonda> Actually I potential would need to bump it to 1.8.4 in a week or two week's time anyway.
[07:31] <Rhonda> And it's definitely not invalid for karmic, there never was a wesnoth-1.8 package in karmic.
[07:32] <Rhonda> The SRU team would only laugh madly at me filing a SRU request for wesnoth-1.8 to karmic.
[07:33] <Rhonda> stalcup: ^^ - can you please take a look, with sugar on top?
[07:57] <dholbach> good morning
[08:04] <ajmitch> morning dholbach
[08:05] <dholbach> hey ajmitch
[08:14] <jdong> stalcup / Rhonda: as a bag of bug fixes new release that was rejected az.
[08:14] <jdong> Err
[08:14] <jdong> as a SRU, I think it's a good backports candidate
[08:15] <jdong> And all those typos means a sleepy jdong
[08:15] <maco> jdong: and no wonder, given the timezone we're in!
[08:15] <jdong> Hey, why are you still up? :)
[08:16] <maco> im up because im a stupid college student who still hasnt gotten it through her head that getting up for work requires going to bed at a decent time
[08:16] <Rhonda> jdong: I still am not clear what you mean. :P  So would you think it does indeed make a good SRU candidate, or not?
[08:17] <jdong> Rhonda: No i mean it's a good backports candidate and was rejected in error
[09:19] <huats> morning
[09:32] <Rhonda> jdong: Can you set it back to new then, I don't want to be involved in status ping-pongs.  %-/
[11:47] <Laney> jdong or ScottK: Could I be added to backporters?
[12:01] <micahg> dholbach: would a bzr merge work better for a new upstream version?
[12:01] <micahg> actually, I'm not sure how to do that
[12:17] <tumbleweed> micahg: bzr merge-upstream? (if you are talking about new upstream versions, not via debian). And yes, that does make for easier reviewing than people attaching tarballs to bugs
[12:17] <micahg> tumbleweed: yeah, idk how to do that yet
[12:18] <tumbleweed> micahg: bzr merge-upstream --version=$VERSON --distribution=maverick $TARBALL
[12:29] <hyperair> debfx: ping
[12:30] <hyperair> debfx: i'm looking at this: https://bugs.launchpad.net/ubuntu/+source/wormux/+bug/541078
[12:30] <hyperair> and i was wondering, why don't you replace the config.guess and config.sub files?
[12:33] <debfx> hyperair: dh_autoreconf replaces them
[12:33] <hyperair> debfx: ah, it does, eh.
[12:33] <hyperair> i'm not familiar with dh-autoreconf, actually.
[12:34] <hyperair> part of the new debhelper, i suppose.
[12:35] <micahg> tumbleweed: k, now do I ask for reviewer from -sponsors?
[12:35] <debfx> it's a fairly new package (dh-autoreconf) but should work with all debhelper/cdbs versions
[12:35] <tumbleweed> micahg: propose it for merging, it'll appear in the sponosr queue
[12:36]  * micahg didn't close the bug right in bzr..trying again
[12:36] <tumbleweed> debcommit should do the right thing
[12:37]  * micahg didn't use debcommit since I already used it for the commit before
[12:38] <micahg> tumbleweed: fixed it, just used debcommit -e :)
[12:39] <hyperair> debfx: yes, i see. okay, let me continue looking.
[12:40] <dholbach> micahg: that'd work too
[12:40] <micahg> dholbach: bzr merge ready :)
[12:41] <micahg> tumbleweed: thanks for your help
[12:41] <dholbach> micahg: I'm going to be a bit busy today, if nobody beats me to it, I'll have a look tomorrow morning
[12:41] <micahg> dholbach: k, thanks
[12:42] <micahg> dholbach: if a bug has a patch and bzr branch, both show up on the sponsoring page
[12:44] <dholbach> micahg: if you do a merge, no need to file a bug
[12:44] <hyperair> debfx: i noticed you dropped README from debian/docs, which looks like it might be useful.
[12:45]  * micahg thought tracking bugs were always a good thing
[13:12] <debfx> hyperair: the README is in wormux.docs
[13:13] <hyperair> debfx: ah, i must have missed it, sorry.
[14:18] <hyperair> debfx: you're missing entries in debian/copyright for vlgothic.
[14:18] <hyperair> debfx: add those and i'll upload
[14:57] <stalcup> 18
[15:07] <debfx> hyperair: done, thanks for reviewing the package :)
[15:07] <hyperair> debfx: sure =)
[16:02] <LucidFox> http://revu.ubuntuwire.com/p/gmail-notifier <-- do we really need *another* gmail notifier for GNOME?
[16:02] <LucidFox> we have like 5 already
[16:45] <directhex> LucidFox, but the other ones are *wrong*!
[17:05] <nigelb> ok, folks! We (Maia and me) need your help.  We're re-branding "Behind MOTU" since everyone in ~ubuntu-dev would be included.  We'd like your suggestions for name!
[17:14] <hyperair> argh.
[17:15] <hyperair> dput finally reached 97343k/97344k of this 90M tarball crawling at 30k/s
[17:15] <hyperair> and then
[17:15] <hyperair> it hung.
[17:15]  * hyperair facepalms
[17:15] <hyperair> whyyyyyyyyyyyyyyyyyy
[17:15] <hyperair> why does this happen to me?
[17:17] <\sh> hyperair: the karma ;)
[17:17]  * hyperair weeps
[17:18] <Laney> hyperair: you should use sftp
[17:18] <Laney> it won't have that problem
[17:18] <hyperair> Laney: eh?
[17:18]  * hyperair tries
[17:20] <Rhonda> stalcup: I should have mentioned that I was guided there after a SRU discussion, right.
[17:26] <stalcup> Rhonda: that would have been helpful :)  although I jumped to conclusions as well
[17:27] <Rhonda> I *think* I did a test in karmic back then as well, but will try so tomorrow again when I am at the place with my chroots.
[17:28] <stalcup> coolio
[17:29] <Rhonda> Given that 1.8 is already in karmic-backports and the development since then is on a stable branch upstream wise so only translation/bugfixes go in, I though don't expect 1.8.3 to be any different here.
[17:29] <Rhonda> But for completeness (and to please my own perfectionist approach) I will give it a shot just to be sure
[17:30] <stalcup> :)
[17:30] <stalcup> excellent
[18:58] <hyperair> debfx: uploaded.
[18:59] <stalcup> Rhonda: ScottK approved your lucid request, care to comment on your package in karmic?
[19:11] <Rhonda> Like said, can do that tomorrow. :)
[19:11] <Rhonda> Two hours doesn't make the day change over here, mind you. :P
[19:14] <stalcup> Rhonda: it's still morning where I am :)
[19:16] <Rhonda> See, day hasn't even changed for you. ;)
[19:17] <ari-tczew> Laney: thanks for sponsoring   ; O
[19:18] <Laney> np
[19:19] <ari-tczew> Laney: just you don't need to set status manually if debian/changelog includes LP: # tag
[19:19] <Laney> I know.
[19:36] <Rhonda> Where are the metting logs again in the wiki?
[19:36] <Rhonda> Ah, I think I just found me a search pattern.
[19:36] <geser> for which meeting?
[19:37] <Rhonda> Found it ^^
[20:17] <fabrice_sp> jtb is waiting in binary new, and this is blocking 4 syncs to get josm at the latest version. Taking into account that FF is around the corner, should I poke an archive admin to get it approved ASAP?
[20:17] <fabrice_sp> or should I request a FFe right now ? :-)
[20:20] <geser> fabrice_sp: if you know that josm will build after the 4 syncs, why not requests sync for all needed packages now? and deal with the build ordering (if necessary) later
[20:21] <fabrice_sp> geser, right. I forgot about that! tbh, I'm releuctant to upload something that will FTBFS. I'll upload it to my ppa before. Thanks!
[20:29] <ari-tczew> tumbleweed: ping
[20:30] <tumbleweed> ari-tczew: pong
[20:31] <ari-tczew> tumbleweed: hello, what's the command for verbose files in .deb (binary)?
[20:32] <tumbleweed> dpkg-deb -c ?
[20:32] <tumbleweed> (or debc for a binary changes file)
[20:32] <ari-tczew> tumbleweed: I'll prepare a patch for ddd package, which misses .xpm install
[20:33] <tumbleweed> cool. please forward to debian (obviously)
[21:34] <ari-tczew> could someone check whether it can be sync'd? the delta for ssl-cert package reffering to jaunty. https://launchpad.net/ubuntu/+source/ssl-cert/+changelog
[21:39] <geser> ari-tczew: what's your opinion?
[21:41] <ari-tczew> geser: the delta is reffering to upgrade packages in jaunty, but jaunty is very old release
[21:41] <ari-tczew> I'd drop the changes, but I'm not 100% sure
[21:42] <geser> because a delta is old, it doesn't automatically mean it can be dropped
[21:42] <ari-tczew> geser: I don't said delta is old, just affected release is old
[21:43] <ari-tczew> geser: what's your opinion?
[21:43] <geser> then I misunderstood you
[21:44] <geser> and I agree that it can be dropped, openssl-blacklist got moved to suggest in the Debian package and the upgrade notice should be a non-issue now
[21:45] <ari-tczew> geser: that's right
[21:57] <Laibsch> Is REVU still the place for sponsorship requests?
[21:57] <Laibsch> it doesn't seem to process my uploads
[21:58] <micahg> Laibsch: REVU doesn't process, people process things in REVU
[21:58] <Laibsch> micahg: not quite correct ;-)
[21:58] <Laibsch> the server needs to process the upload to show it
[21:59] <Laibsch> mine doesn't show up in the list
[21:59] <Laibsch> uploaded it yesterday and today
[21:59] <micahg> Laibsch: are you referring to an existing package or a new package?
[21:59] <Laibsch> new package
[21:59] <Laibsch> natspec
[21:59] <micahg> oh, yeah, well then...
[21:59] <Laibsch> where is the place now?
[21:59] <micahg> Laibsch: same place, just lack of REVUers :)
[22:00] <Laibsch> OK
[22:00] <Laibsch> that's kind of unchanged ;-)
[22:00] <Laibsch> but again, the server doesn't even process my package
[22:00] <Laibsch> it doesn't show up in the list
[22:00] <micahg> Laibsch: is it debian 545151
[22:00] <Laibsch> yes, that's the one
[22:00] <Laibsch> and there is a bug in LP as well
[22:01] <Laibsch> about unzip and encoding issues
[22:01] <micahg> Laibsch: so, getting into debian would be ideal, have you tried that route?
[22:01] <Laibsch> do you remember my nick
[22:01] <Laibsch> ?
[22:01] <Laibsch> no need to always start with the basics ;-)
[22:02] <Laibsch> Yes, I'm maintaining a number of packages in Debian already
[22:02] <Laibsch> and the upload to Debian is in progress
[22:02] <micahg> Laibsch: are you just trying to get in Maverick before FF?
[22:02] <Laibsch> but that won't be in time for maverick (at least most likely it won't)
[22:02] <Laibsch> kind of
[22:02] <Laibsch> DIF
[22:02] <Laibsch> no?
[22:03] <Laibsch> and I think we're already past DIF
[22:03] <micahg> k, I should probably stop now since I'm not helping here...
[22:03]  * micahg will bbiab
[22:03]  * micahg can't REVU anyways
[22:03] <Laibsch> but maybe you can help me find out why the darn server won't process my uploads
[22:04] <Laibsch> :-/
[22:07] <ari-tczew> tumbleweed: ddd patch updated
[22:19] <micahg> Laibsch1: idk, I see the upload, but it says there was an issue and idk who admins REVU
[22:20] <Laibsch1> some special restricted-access area?
[22:20] <Laibsch1> because I don't see anything
[22:20] <Laibsch1> and I did not get a mail about it, eithr
[22:20] <micahg> Laibsch1: http://revu.ubuntuwire.com/details.py?upid=8500
[22:21] <Laibsch1> it's now showing in the list, too
[22:21] <Laibsch> thanks
[23:02] <ari-tczew> bdrung: could you sync this one? bug 614210 it's necessary for some packages to merge
[23:56] <siretart>