[09:29] <BUGabundo_remote> morning
[14:46] <Dimmuxx> any news on the beta ppa?
[16:16] <nxvl> chrisccoulson: ping
[16:24] <chrisccoulson> hi nxvl
[17:07] <gnomefreak> back to normal :)
[17:07] <gnomefreak> almost
[17:16] <gnomefreak> no gwibber daily for maverick anymore?
[17:30] <fta> jdstrand, mdeslaur-afk: http://googlechromereleases.blogspot.com/2010/07/stable-channel-update_26.html
[17:35] <micahg> fta: the security guys are off or at blackhat, sbeattie should be available, but chrisccoulson should be able to take care of getting it into -proposed, you don't really need the security guys until next week to copy to -security :)
[17:35] <fta> k
[17:36] <micahg> fta: actually, you can upload yourself to -proposed and just ask pitti to accept
[17:37] <fta> is this still 0ubuntu0.10.04.1 ? or .2 now?
[17:38] <micahg> .1 since it's the first upload for this version
[17:38] <micahg> it's not actually connected to the point releases for Lucid
[17:38] <fta> hm, i thought it was to match lucid.1
[17:38] <fta> oh
[17:39] <fta> ok, good then
[17:39] <micahg> it's just a way to upload the same version to multiple releases
[17:43] <chrisccoulson> this is crazy, we need to sort out getting an exception for chromium so we can just upload directly to the security PPA and then copy to -security
[17:43] <chrisccoulson> rather than going through -proposed
[17:43] <chrisccoulson> did anyone look at doing that?
[19:29] <micahg> chrisccoulson: I think for chromium not to go through -proposed, the TB needs to make an exception
[19:30] <micahg> fta: were you aware the chromium is a transitional package for chromium-bsu?
[19:32] <fta> micahg, chromium used to be the game
[19:32] <fta> that's why i had to name the browser differently
[19:32] <micahg> fta: right, but the guy transitioned it because of chromium
[19:33] <fta> micahg, yes, but it's still impossible to reuse the name
[19:33] <micahg> fta: not true
[19:33] <micahg> fta: in fact the guy had a blog fit recently about it
[19:34] <fta> micahg, if you had the game, even after the transition, reusing the name will make the browser appear even if you don't want/need it
[19:34] <micahg> fta: http://rss.sourceforge.net/~r/SourceforgeCommunityHub/~3/lMSnlqgHg90/
[19:34] <micahg> fta: most people want the browser, not the game
[19:35] <micahg> fta: even the source was renamed back before karmic
[19:36] <fta> micahg, i have the game installed here, had it for years, long before the browser
[19:36] <micahg> fta: that's fine, but there's plenty of confusion still
[19:37] <fta> reading the blog, he seems to just ask us to drop his transitional package to stop the bogus bug reports
[19:43] <micahg> fta: yeah, well the thing is Debian's stuck, they have to use the transistional package for squeeze
[19:44] <fta> version wise, we can take over that package name, but i'm not sure it's wise
[19:44] <fta> asac, ^^, thoughts?
[19:49] <fta> also, it would be hard to do in the ppa, because of hardy
[19:50] <fta> ..and jaunty
[19:51] <fta> when are those two supposed to die?
[19:51] <micahg> fta: forgot about PPA, it would be a real problem then
[19:51] <micahg> fta: Jaunty OCt 2010, Hardy/Karmic Apr 2011
[19:52] <fta> hm, still far then
[19:52] <micahg> fta: I guess you're right, we can't feasibly do this till next LTS
[19:54] <fta> micahg, we should probably drop the transitioning packages in maverick (and if possible in lucid) to stop messing up with the bsu bugs
[19:54] <micahg> fta: lucid needs it for hardy upgrades
[19:54] <micahg> maverick we could drop it
[19:56] <fta> or maybe it's possible to stop accepting bugs in lp for it
[19:56] <micahg> fta: can't due that until hardy is EOL
[19:56] <fta> damn
[19:56] <micahg> then the source will have no stable packages using it
[19:57] <micahg> *releases
[20:14] <chrisccoulson_> dear ubuntuzilla, please stop breaking our firefox installs, thank you :)
[20:15] <micahg> heh
[20:17] <micahg> chrisccoulson_: looks like a post for identi.ca :)
[20:19] <fta> chrisccoulson_, hi, added you to the drobotik watchers list for umd and ucd last week, hope you don't mind
[20:20] <fta> and that you'll find some use to it at some point
[20:20] <micahg> fta: BTW, you can take me off of UMD watch since I am part of PPA now
[20:20] <micahg> unless it's tied to ucd
[20:20] <micahg> in which case, it's fine
[20:20] <fta> the bot's email?
[20:20] <micahg> fta: no, the failures
[20:21] <micahg> unless it's all tied together
[20:21] <fta> micahg, hm, do i redirect that to you?
[20:21] <micahg> yeah, for umd and ucd
[20:22] <fta> * ^X-launchpad-ppa:\ .*-daily
[20:22] <fta> * ^X-launchpad-build-state:\ (FAILEDTOBUILD|CHROOTWAIT)
[20:22] <fta> so it's all that matches "-daily"
[20:23] <micahg> chrisccoulson_: if you get a chance, can you get the enigmail fix for Lucid uploaded to -proposed so that it can be ready for when 10.04.1 is released
[20:23] <micahg> fta: k, no worries, I have it filtered properly on my end
[20:24] <fta> micahg, which one do you want to keep? ucd ?
[20:24] <fta> or none?
[20:25] <micahg> fta: ucd, but since your filter is set like that, just leave it, I have the dupe umd filtering in the trash
[20:26] <fta> changed it to * ^X-launchpad-ppa:\ .*chromium-daily
[20:26] <fta> well, no, i can't, as it's also my own filter
[20:28] <chrisccoulson_> micahg - yeah, will do that after dinner
[20:30] <micahg> fta: like I said don't worry, thanks
[20:30] <micahg> chrisccoulson_: thanks
[20:34] <fta> hm.. i have a fix for python-pysnmp4 in lucid, i wonder if i should just upload it or add it to a bug..
[20:34] <fta> and wait
[20:34] <micahg> fta: fixes for Lucid require bugs with SRU info, then you can upload to -propsoed
[20:50] <fta> micahg, like that? bug 610570
[20:50] <ubot2> Launchpad bug 610570 in python-pysnmp4 (Ubuntu) "python deprecation warnings for md5 and sha (affects: 1) (heat: 8)" [Low,In progress] https://launchpad.net/bugs/610570
[20:50] <fta> hm, where is the debdiff..
[20:51] <micahg> fta: debdiff isn't attached, subscribe ubuntu-sru (motu-sru is deprecated) and attach to bug and upload
[20:51] <micahg> fta: test case (what to expect before and after) is good
[21:01] <fta> done
[21:02] <micahg> fta: BTW, it's suggested to modify the source directly rather than adding a patch system.  Also, is this fixed in Maverick?
[21:03] <fta> no, i tried to contact the DD, no answer
[21:03] <fta> the package hasn't been touched recently
[21:04] <micahg> fta: you can upload the fix to maverick w/out going through Debian if there's no answer
[21:05] <fta> yep, i know. my dev box is still using lucid, and that's where i needed the fix in the 1st place
[21:07] <fta> but i assume no one will care, it's a pretty specialized package
[21:09] <micahg> fta: there's a new upstream 4.1.14a
[21:09] <fta> i know
[21:09] <fta> that one of my question to the DD
[21:09] <fta> but it's not for lucid anyway, so i went for the fix
[21:13] <micahg> fta: right, you can update maverick to the latest version if you want