[03:20] <micahg> do FTBFS qualify for SRU by themselves, or do you need another bug to upload it with?
[03:21] <ScottK> micahg: That's generally sufficient.
[03:21] <micahg> ScottK: does that include something that if rebuilt at the moment, it won't build, but not on the FTBFS list?
[03:27] <micahg> master: identity crisis?
[03:27] <master> micahg: always
[03:27] <master> :P
[03:39] <ScottK> micahg: If the package is not out of date (e.g. the binary in the archive is built from the current source), then I don't think it's SRU worthy. it would be documenting in a bug how to get it to build if a package update were needed for other reasons.
[03:41] <micahg> ScottK: well, the issue is gnome-chemistry-utils, an update to libgdk-pixbuf makes it so the current source cannot build anymore so if an update was needed, that would need to be fixed
[03:42] <ScottK> Right, but since an update isn't otherwise need it, I think it's sufficient to document what needs changing.
[03:42] <ScottK> (for maverick)
[03:42] <ScottK> Fix it in Natty after it opens, of course
[03:43] <micahg> ScottK: k, will keep in mind, thanks
[03:44] <ScottK> micahg: Also I'm not on ubuntu-sru, so that's just my opinion.
[06:45] <micahg> is it possible to do syncs from Debian to -proposed (Just a new Debian revision, not upstream)?
[07:10] <AnAnt> do I need SRU even for a theme update ?
[07:12] <micahg> AnAnt: what do you mean?
[07:12] <AnAnt> micahg: I wanted to update plymouth-theme-sabily package, does that require an SRU ?
[07:13] <micahg> AnAnt: at this point, yes
[07:13] <micahg> AnAnt: that or a backport
[07:22] <AnAnt> ScottK: Hello
[08:39] <micahg> hyperair: would you be willing to comment on my MOTU app?
[08:40] <hyperair> i could try later, but not now. i'm preparing for a barcamp talk
[08:40] <micahg> hyperair: k, no rush, I'm not applying for 2 weeks
[09:01] <chalet16> Will there php 5.3.3 backport for lucid LTS?
[09:01] <micahg> chalet16: not in the archive
[09:02] <chalet16> mean that there is no plan for offical backport?
[09:07] <micahg> ttx: there's no possibility of officially backporting PHP, right?
[09:07] <ttx> micahg: I'd say no... but you can ask the question to zul for a definite answer
[09:08] <micahg> I thought I asked once, but I can't seem to find a record of it
[09:09] <micahg> chalet16: normally security updates and high priority fixes are provided, but not new versions for PHP, looking at the history of the last 5 releases
[09:09] <chalet16> for backports too?
[09:13] <micahg> chalet16: well, it hasn't been backported in the past, you could ask the server team what it would take to have it backported, #ubuntu-server or<EMAIL_ADDRESS>[09:14] <chalet16> ok
[09:14] <chalet16> thanks
[09:14] <micahg> chalet16: mailing list might be better since it's the weekend
[09:14] <chalet16> ok
[10:49] <Rhonda> Are there troubles with the launchpad debbugs connection? It doesn't seem to update the bug status at all since a pretty long time now, keeping Debian bugs still listed as New :/
[10:57] <ajmitch> Rhonda: I think it used the public bts mirror which was on merkel
[10:58] <wgrant> That's part of it.
[10:58] <wgrant> And it's the main problem now.
[10:58] <wgrant> But it's not the original issue.
[10:59] <Rhonda> ajmitch: Hmm, then I think that might have changed, there were a fair amount of parts going on with merkel.
[10:59] <wgrant> Right, it's gone.
[10:59] <wgrant> Without a replacement :(
[11:00] <Rhonda> Did anyone ask don about it? Or was it just accepted that it's gone?
[11:00] <wgrant> The email about it said it probably wasn't going to be replaced.
[11:01] <ajmitch> that could have been because there wasn't any public outcry about it
[11:01]  * ajmitch only asked in #debian-qa, didn't ask on a mailing list
[11:20] <ajmitch> good to see another release
[12:13] <CapeTownParty> geek farming
[12:13] <persia> Hrm?
[16:11] <bdrung> didrocks: so you want us to carry the eclipse patch in debian until a better solution is found?
[16:11] <didrocks> bdrung: if you are willing to, I think that's the best option
[16:11] <didrocks> bdrung: sorry, I wasn't clear enough?
[16:12] <bdrung> didrocks: it wasn't very clear. i'll take care of it. just let us know once it should be changed.
[16:13] <didrocks> bdrung: sure, I'll (hoping that we can export the menu through dbus for those apps in natty)
[16:43] <Rhonda> Oh. Ah. I think it's time for another packages.ubuntu begging-for-applying-changes round.
[16:44]  * Rhonda . o O ( No, haven't commited yet )
[16:44] <Rhonda> Has natty got created yet?
[16:45] <persia> Nope.  Be a few days, at least.
[16:45] <persia> There's usually a mail to u-d-a when the new archive is really open (post-toolchain-fussiness)
[16:45] <Rhonda> Then I guess I don't have to rush the commit. Is any release EOLed now?
[16:46] <micahg> Rhonda: jaunty won't be EOL for another 13 days
[16:46] <Rhonda> But dapper is gone?
[16:46] <persia> Nope.  That lasts until sometime in June 2011
[16:47] <micahg> Rhonda: not on server for another 8 months
[16:47] <Rhonda> http://wiki.ubuntu.com/#Releases doesn't mention it anymore?
[16:47] <persia> (although it's hoped most of the remaining dapper users will have been able to update to lucid in the next 3-4 months)
[16:48]  * persia edits
[16:48] <Rhonda> micahg: Hmm, I guess I'll remove jaunty right ahead from the packages code, I have very little hope that the changes will get applied within the next 2 weeks. Or 2 months, FWIW.
 debian-www: rhonda ubuntu-master * r8838986 packages/ (3 files in 3 dirs): Add maverick, remove jaunty
[17:05] <Rhonda> http://git.debian.org/?p=webwml/packages.git;a=commitdiff;h=8838 - yet again the changes to config.sh.in needs to get applied to the config.sh file on the server after the git pull.
[19:42] <nhandler> Does anyone haves any suggestions for packaging training sessions that they would like to see or does anyone want to volunteer to give one?
[19:51] <persia> nhandler, https://wiki.ubuntu.com/MOTU/School/Requests is full of ideas
[19:51] <persia> Some of them are pointlessly obsolete at this point.
[19:52] <nhandler> persia: Yeah, and many of them have been done as well (we had copied them to Packaging/Training at some point)
[19:52] <persia> Might be worth decommissioning that page then :)
[19:52] <Rhonda> I still should do my git talk me thinks at some point.
[19:53] <persia> With a new cycle starting, it might be worth having one about UEHS: new upstream, bug fixes, bug forwarding, etc.
[19:56] <nhandler> persia: True. We had a few on bug forwarding in conjunction with Project Cleansweep. And I'll look through the MOTU/School pages to see if there is anything valuable that hasn't been merged into other pages yet and get rid of the page if not
[19:56] <persia> nhandler, Please keep w.u.c/MOTU/School as a page, but maybe rewrite to talk about history, and move all the real content over to Packaging/Training.
[19:57] <persia> All the subpages can probably go at this point: Packaging/Training has long taken over, and we'd do better to not be confusing.
[19:57]  * nhandler nods
[22:26] <ari-tczew> does anyone have an information how many merges were available when lucid/maverick started?
[22:28] <persia> I think MoM has some historical statistics, used for the charting.
[22:29] <persia> They have minor inaccuracies for complex reasons, but it ought be correct to within less than a percentage point.
[22:29] <persia> Note that Natty will open with fewer pending Debian changes than usual: one of the best ways we can ensure Natty has new and updated software is to help Debian release Squeeze.
[22:33] <ari-tczew> persia: look @ https://merges.ubuntu.com/main-trend.png
[22:34] <ari-tczew> it looks like history, but the number is strange - 4000?
[22:34] <persia> Right.  Those would be the historical statistics from MoM
[22:34] <persia> Might be a count of packages in main.  Might be a count of all packages that were ever in main.  Check the code.
[22:35] <ari-tczew> persia: good point, red color is interesing for me.
[22:35] <ari-tczew> but in this case is not good readable
[22:36] <persia> No, it isn't.
[22:36] <persia> You might look at the MoM code to see how they are generated: it may be that you can get something closer to what you seek from that.
[22:37] <ari-tczew> persia: but from universe trend we can compare 2 points - red line with lucid release and with maverick release
[22:37] <ari-tczew> the conclusion is following: we've reduced a lot of merges during maverick cycle
[22:37] <persia> Anyway, the current MoM information is very likely to be of limited use, as either squeeze will release before DIF, meaning everything needs to be remerged, or it won't meaning we'll have a huge swath of DIFes to process, which probably requires coordination or something.
[22:38] <persia> Sure, but that doesn't reflect on us: it's also that Debian has been frozen for most of the Maverick cycle, so there's less to be merged.
[22:38] <ari-tczew> also, the number of to-merge packages are smaller in universe than to-merge in main!
[22:38] <ari-tczew> it's nice achievement
[22:38] <persia> This is not uncommon.  Stuff in main tends to get tweaked more, and historically there has been weaker coordination with Debian.
[22:40] <persia> If you're willing to track history further, you might notice that for the 5.04 cycle, there were *zero* pending merges in universe.
[22:40] <ari-tczew> persia: I trust, but number of packages is growing up always
[22:40] <ari-tczew> :)
[22:41] <persia> No, I think we got a reduction in total packages for feisty->gutsy by clearing out a bundle of stuff.
[22:41] <persia> But there are usually more, indeed :)
[22:41] <micahg> persia: so working on Debian RC bugs in Debian at this point is like working on Ubuntu?
[22:41] <persia> micahg, Yes, in two ways.
[22:41] <micahg> persia: cool, will keep in mind
[22:42] <persia> Firstly, by solving the Debian RC bugs, we get to apply those fixes in Ubuntu, to issues that are likely RC (and probably ought be SRUs)
[22:42] <persia> Secondly, by helping Debian release squeeze, we allow the hundreds of Debian Developers to easily upload the newest upstream stuff, and we can autosync it.
[22:43] <persia> So, it's fixing 200 bugs that we need to fix anyway to get ~1000 extra developers helping us get new software.  Seems more than a fair tradeoff to me.
[22:43] <micahg> yep
[22:44] <ari-tczew> persia: I would believe that sync package which fixes RC bug is enough.
[22:47] <persia> ari-tczew, sync from where?  The RC bugs need to be fixed *in Debian*
[22:48] <ari-tczew> persia: so what about column Fixed Version ?
[22:49] <ari-tczew> http://qa.ubuntuwire.org/bugs/rcbugs/
[22:49] <persia> ari-tczew, Those are RC bugs that have already been fixed in Debian but aren't yet fixed in Ubuntu.  We need to review them, and if they are critical for Maverick, SRU them.
[22:50] <micahg> ari-tczew: I think persia means we need to fix the RC bugs not on the list yet in Debian, so they can be sync'd to Ubuntu
[22:50] <persia> http://bts.turmzimmer.net/ is a reasonable place to look for RC bugs that need to be fixed in Debian
[22:51] <persia> micahg, Actually, at this point in the Ubuntu cycle, I think it's more important to get squeeze released than to worry about syncs (especially as we're supposed to cherry-pick for SRUs)
[22:52] <micahg> persia: right, I meant after squeeze was released
[22:52] <tumbleweed> these days: there's also http://udd.debian.org/bugs.cgi
[22:53] <persia> UDD is making all my carefully memorised URLs obsolete
[22:54] <highvoltage> heh
[22:55] <tumbleweed> persia: yeah I never remembered turmzimmer
[23:50] <ari-tczew> persia: do you remember today case about plymouth bug?
[23:50] <persia> Yes.
[23:50] <ari-tczew> persia: I found resolution (note: work-around) for this problem.
[23:51] <persia> Excellent!
[23:51] <persia> So you have a graphic logo now?
[23:51] <ari-tczew> but I didn't use this, because I want have system to fix the patch, not work-around script.
[23:51] <ari-tczew> I can suggest people affected by this bug to use workaround
[23:53] <ari-tczew> persia: http://techblogparade.blogspot.com/2010/09/fix-ugly-plymouth-screen-on-ubuntu-1010.html
[23:56] <persia> Oh, too bad.  I was hoping for something sharable.
[23:56] <persia> At least it makes your device pretty :)
[23:57] <persia> Maybe it's worth talking to the #ubuntu-x folks about considering something like that for postinsts or something.
[23:57]  * persia isn't sure that would really work for everyone, but it works around the limited kernel support from the binary drivers, and confirms that it isn't a bug in plymouth
[23:58] <RAOF> Detecting BIOS-settable resolutions is somewhat of a black art.
[23:59] <persia> RAOF, Do we not have EDID info when we use those drivers?
[23:59] <RAOF> The EDID isn't what we're after.
[23:59] <persia> What do we need beyond resolution and bit depth?