[00:01] <infinity> If only I could spell Ubuntu...
[00:02] <infinity> phillw: How does that look, other than my typo?
[00:02]  * stgraber likes alphabetical order ;) at least until someone creates Abuntu or similar
[00:02] <infinity> Aardbuntu.
[00:03] <infinity> For aardvarks, of course.  Not to be confused with Arrbuntu, for pirates.
[00:03] <skaet> stgraber, going through the b2 milestoned bugs - https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/862867 looks resolved from comments,  can it be closed?
[00:03] <ubot2> Launchpad bug 862867 in ubiquity-slideshow-ubuntu "Screenshot for Web slide in Ubuntu slideshow is focused on English text" [Medium,Confirmed]
[00:03] <phillw> infinity: looks great, thanks. It is little things like that which I get nagged at for :)
[00:04]  * infinity wonders if there's a way to make "The cdimage server also hosts other Ubuntu images not found on this server" either more vague or more usefully informative, without writing a long paragraph about how some of the Ubuntu images on cdimage are "supported", but not published to releases, while others are community best-effort, and, and...
[00:05] <infinity> Maybe I'll just leave it the vague way I wrote it.
[00:06] <phillw> infinity:  The cdimage server also hosts other Ubnuntu images not found on this server. ???
[00:06] <phillw> Now, I know I'm tired.... but that does not make sense!
[00:07] <stgraber> skaet: yeah, I quickly confirmed we indeed have the olpc website now and marked as fix released
[00:07] <infinity> phillw: "this server" being the one you're reading (releases.ubuntu.com).
[00:07] <infinity> Maybe I need to spell that out instead of using a pronoun.
[00:07] <skaet> thanks stgraber.  :)
[00:10]  * infinity also thinks it might not be a bad idea to have a short plug/tagline for each derivative in brackets after the link...
[00:11] <infinity> Edubuntu (stgraber can write this one), Kubuntu (featuring the KDE desktop), Lubuntu (featuring the LXDE desktop), etc...
[00:11] <slangasek> infinity: sounds like asking for a maintenance headache to me, updating the text in response to requests?
[00:12] <slangasek> the references are there to tell users "this is wrong page, go -->there"
[00:12] <infinity> slangasek: Well, I didn't mean a full-blow advertisement, just an obviously-correct "uses XFCE".  But yeah, a link to the homepage would work too.
[00:12] <phillw> infinity: may be a link to the wiki page for each would be better (less for you guys to maintain)
[00:13]  * infinity shrugs.
[00:14]  * infinity glares at queuebot.
[00:14] <infinity> stgraber: That should be a binary, not a translation. ;)
[00:14] <phillw> infinity: so, for example, lubuntu would be https://wiki.ubuntu.com/Lubuntu
[00:14] <stgraber> infinity: https://launchpad.net/ubuntu/precise/+queue tells me the bot is right ;)
[00:15] <infinity> stgraber: Note that it's "i386,raw_translations"
[00:15] <infinity> stgraber: The i386 bit being slightly more important. :P
[00:15] <infinity> (d-i would have the same problem)
[00:16] <infinity> It would say (arch,raw-installer)
[00:16] <infinity> Actually, probably (arch,raw-translations,raw-installer)
[00:16] <infinity> stgraber: But any binary with stripped translations will come out that way, so it should probably DTRT. ;)
[00:17] <stgraber> infinity: for releases.u.c, I guess we could go with Edubuntu (Educational flavour of Ubuntu) (http://www.edubuntu.org)
[00:18] <stgraber> infinity: yeah, the trick is that it's showing up as a single entry...
[00:18] <stgraber> infinity: should the bot announce binary + translations separately in that case?
[00:18] <stgraber> infinity: (don't accept that binary, I want to keep it around to test the fix ;))
[00:19] <infinity> stgraber: No, we don't care about the raw-* components from the bot.
[00:19] <infinity> stgraber: Just the arch bit.
[00:19] <infinity> stgraber: So, "linux [i386]" is fine.
[00:20] <infinity> stgraber: Won't be accepting until all the arches roll in, you have many hours. ;)
[00:20] <stgraber> infinity: so are there cases where the bot should show the "New translation" message then?
[00:21] <infinity> stgraber: I suppose if an upload has a raw-* component and no arch component, that would be something special to handle, but I'm not even sure LP allows that, and I'm sure no package does it.
[00:21] <infinity> stgraber: In practice, raw-* is always tacked onto an arch upload, and it's the arch upload we care about.
[00:22] <stgraber> k, I'll try to update the bot to ignore raw-* then
[00:22] <infinity> stgraber: So, no, there's no call for "new translation" or "new debian-installer bits" or "new ddebs" or "new other junk you can do with raw-"
[00:23] <skaet> slangasek,  who does accepts on ubuntu-font-family?   spotted something that looks like its been fixed, but fallen through the cracks.
[00:33] <phillw> skaet: what happened to the early night?
[00:33] <skaet> phllw,  started on cleaning up milestoned bugs....
[00:33]  * skaet must walk away from terminal...
[00:34] <phillw> my body clock is that messed up, it thinks it is currently half past Tuesday!
[00:35] <skaet> pitti,  I'll finish the review/moving of the beta 2 milestoned bugs tomorrow,  would like to do it.  Some interesting patterns in them.
[00:37] <skaet> beta 2 milestone has be closed now.
[00:37] <skaet> will work on the beta + 1 day checklist more tomorrow.
[00:38] <skaet> good night all.
[00:38]  * skaet --> dinner.
[00:43] <phillw> skaet: enjoy, with a glass of richly deserved wine!
[00:44] <knome> may the glass be overflowing... but not too much so none of the wine is spilled on the floor
[00:54] <slangasek> skaet: not sure what you mean wrt accepts on ubuntu-font-family?
[01:22] <micahg> can someone please look at skype (i386) in partner?
[01:22] <micahg> in NEW I mean
[01:40] <infinity> micahg: Done.
[01:40] <micahg> infinity: thanks
[05:11] <pitti> skaet: we have a script in ubuntu-archive-tools to mass-move them over, can do
[05:20] <pitti> move-milestoned-bugs.py  ubuntu-12.04-beta-2 ubuntu-12.04
[05:20] <pitti> running now
[08:25] <pitti> cjwatson: do you have an opinion about bug 968121? I don't really see how we can not do it, but I'd appreciate a second pair of eyes
[08:25] <ubot2> Launchpad bug 968121 in apport "[FFE] crashdb.conf needs a way to disable reporting of particular problem types" [High,New] https://launchpad.net/bugs/968121
[08:26] <micahg> FYI, I asked for molybedenium to be switched to i386 to help with the rebuild (only needed for hardy)
[08:30] <pitti> ah, appreciated, especially with rothera being out
[08:37] <Laney> did something go wrong with the LO builds?
[08:37] <pitti> yes, bug 930217
[08:37] <ubot2> Launchpad bug 930217 in launchpad "Make proposed pocket useful for staging uploads" [Low,Fix committed] https://launchpad.net/bugs/930217
[08:37] <pitti> the -proposed builds failed to upload
[08:37] <Laney> ah, that's what it looks like if the release gets unfrozen in the interim?
[08:37] <pitti> Laney: I asked Sweetshark to reupload to precise
[08:38] <pitti> I didn't think that it would reject the binaries, just that it wouldn't allow uploads
[08:38] <pitti> yes, apparently
[08:38] <Laney> i see, good to know
[08:38] <Laney> not that it should be happening in the future :-)
[08:55] <pitti> infinity: FYI, http://people.canonical.com/~ubuntu-archive/pending-sru.html has precise again now
[09:02] <cjwatson> pitti: I haven't gone through the code, but the need seems reasonable enough ...
[09:03] <cjwatson> pitti: Binaries go through much the same upload path in some ways.
[09:03] <pitti> I'm quite convinced about the implementation, I'm mostly wondering about the concept
[09:03] <pitti> I discussed it in-depth with Evan, and that's what we came up with which makes both of us happy
[09:03] <cjwatson> Your description seems sound enough
[09:04] <pitti> the configuration change is future proof, and the implementation temporary until we support whoopsie in apport more properly
[09:05] <cjwatson> I was a bit scared that you might be trying to land that proper implementation; a less intrusive hack seems more appropriate for the moment
[09:05] <pitti> cjwatson: right, I targetted bug 957177 to Q for thaht
[09:05] <ubot2> Launchpad bug 957177 in apport "support multiple crashdbs" [Medium,Triaged] https://launchpad.net/bugs/957177
[09:06] <pitti> this patch is about as small as I can make it, and much of it is tests anyway
[09:06] <pitti> the gut of the change is just 5 lines
[09:10] <cjwatson> pitti: approved
[09:10] <pitti> thanks for the review
[09:10]  * cjwatson goes off to QA proposed-as-staging-pocket
[09:11] <pitti> cjwatson: aside from LibO this has worked really wonderfully
[09:11] <pitti> cjwatson: not a single second of archive breakage due to gnome 3.4 and unity, and we could use the builders during freeze
[09:11] <pitti> how could we ever not have that! :-)
[09:12] <cjwatson> mm, the compiz / gtk+3.0 thing did point out why it isn't a panacea; I wonder if it would be possible to improve things so that the builder could use packages from release if the ones in proposed are uninstallable
[09:12]  * pitti just gets way too happy and verbose about improvements like that
[09:12] <cjwatson> but in general, yeah, should be nice
[09:13] <pitti> right, we encountered that problem in SRUs as well
[09:13] <cjwatson> yep, same thing
[09:17] <Daviey> cjwatson: I have NFI how whoopsie reporting is supposed to work on servers... but we are now installing it by default.  Are there doc's i'm missing?
[09:25] <cjwatson> Daviey: ask Evan :)
[09:27] <Daviey> ev: ^^
[09:29] <ev> Daviey: it has an inotify watch on /var/crash. Apport drops crash files in there, you run apport-cli to process them and in doing so it touches /var/crash/$report_file.upload which tells whoopsie to upload the report to the crash database.
[09:30] <Daviey> ev: So it's purely done by manual intervention ?
[09:31] <pitti> admins can do http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/README#L51
[09:31] <pitti> if they care
[09:31] <ev> at the moment, yes
[09:41] <micahg> pitti: can you delete the amd64 binaries of libreoffice in -proposed, they're broke
[09:41] <micahg> pitti: precise-proposed
[09:42] <pitti> micahg: I'll delete the whole source; it can't build in -proposed anyway ATM
[09:42] <micahg> pitti: sure, as long as the binaries go with it :)
[09:46] <Daviey> pitti: thanks
[09:53] <pitti> micahg: all gone
[09:53] <micahg> pitti: thanks :)
[12:25] <didrocks> bdmurray: skaet: is the rls-p-tracking daemon is opening downstream bug task?
[13:08] <ogasawara> when someone has a moment, can I get the 3.2.0-21.34 kernels approved in the new queue?
[13:14] <pitti> ogasawara: looking
[13:15] <pitti> ogasawara: don... ah, big brother beat me to it :)
[13:16] <ogasawara> pitti: heh, thanks anyways
[13:16] <pitti> ogasawara: I mean beat me to the announcement; I binNEWed them now
[13:20] <cjwatson> is there a release meeting today?
[13:21] <pitti> traditionally we skip it after a release
[13:21] <pitti> and just send our reports
[13:21] <pitti> but haven't heard something definitive
[13:24] <ogasawara> I recall skaet mentioned yesterday that the meeting is canceled for today and she'd call an impromptu meeting on monday if needed
[13:28] <cjwatson> good
[14:04] <skaet> good morning
[14:05] <stgraber> skaet: good morning
[14:05] <skaet> pitti, cjwatson, ogasawara yes,  meeting is cancelled but email reports please,  and we can assess later if we need a meeting on monday.
[14:05] <skaet> good morning stgaber, :)
[14:06] <pitti> skaet: thanks for confirming
[14:06] <pitti> skaet: and good morning!
[14:06] <pitti> skaet: congrats for wrapping beta-2
[14:06] <skaet> :)  thanks for all you help with getting those images out the door.
[14:24] <Laney> stgraber: highvoltage: bug 935147 - any opinion either way?
[14:24] <ubot2> Launchpad bug 935147 in liferea "FFe: Please merge liferea 1.8.3-0.1 (main) from Debian unstable (main)" [Unknown,Fix released] https://launchpad.net/bugs/935147
[14:25] <stgraber> Laney: looking
[14:29] <stgraber> Laney: would have preferred to hear about it earlier, but as we have to support it for 5 years, I think it'd be good to have a version upstream actually supports
[14:29] <Laney> stgraber: OK, so I'll grant the FFe then. You can sponsor if you want, otherwise I'll leave it in the queue.
[14:30] <stgraber> Laney: I'm not a user of liferea myself but the UI is very similar to what I remember so even if we have it in our install slideshow we won't need to update it and we haven't made the final screenshots for the website, so that part is fine
[14:32] <Laney> there we go, all yours
[14:32] <Laney> looks like he nuked the last Debian changelog entry for some reason, otherwise the diff seems reasonable on first glance
[14:38] <stgraber> Laney: it actually looks like diff being pretty confused by the added entry having some identical lines with the latest debian entry
[14:38] <Laney> oh yeah, I see it further down
[14:41] <stgraber> right, diffs look reasonable and it's been built in his ppa so assuming it'll build in the archive too. uploaded
[14:45] <Laney> nice
[14:48] <highvoltage> Laney: not having looked at the bug report yet... I'm currently using 1.8.3 on Debian and it has a nasty regression with summarizing feeds in Unread
[14:49] <Laney> stgraber already sponsored it :P
[14:49] <highvoltage> good, maybe someone in ubuntu might end up fixing it too then :)
[14:56] <ogasawara> pitti: could I also get linux-backports-modules-3.2.0 approved in the new queue please?
[14:57] <pitti> ogasawara: ah, that's just for i386/amd64 anyway; accepted
[15:05] <skaet> pitti,  cjwatson, slangasek (and release team members as well as others interested...),  have created blueprint to catch ideas and thoughts about how we'll use the new staging in -proposed capability
[15:05] <skaet> https://blueprints.launchpad.net/ubuntu/+spec/other-q-freeze-use-of-proposed
[15:06] <skaet> please add to the whiteboard ideas, concerns, etc. as they occur through this next month,  and we can then discuss at UDS.
[15:24] <cjwatson> skaet: could we please reuse foundations-p-upload-intermediary instead?
[15:25] <cjwatson> obviously it's fine to move it to other-q etc. but I feel we should keep that history
[15:36] <pitti> in case someone wonders about the gccgo binary rejection, see #ubuntu-devel from 20 minutes ago
[15:52] <skaet> cjwatson, agree on keeping history is important.   I'll move the history over to the q whiteboard, since there are likely to be q workitems come from this, and would need to set up one anyway for tracking then.    I'll paste any workitems postponed to the new workitem tracker as well.
[16:23] <infinity> Why are we rejecting gccgo-4.7 binaries?
[16:23] <cjwatson> infinity: 15:58 <pitti> doko: hm, should gccgo-4.7 really produce the gcc-4.7-base, fortran, and other packages as well?
[16:24] <infinity> Ahh.
[16:24] <infinity> I suppose if I'd looked in the queue, I would have noticed. ;)
[16:59] <knome> can somebody look at bug 969252 ?
[16:59] <ubot2> Launchpad bug 969252 in shimmer-themes "[UIFe] Bluebird rebased against Greybird for Gtk3.4" [Undecided,New] https://launchpad.net/bugs/969252
[17:11] <infinity> knome: Rebasing seems sane to me.
[17:12] <knome> is there something i need to do, or will somebody get it uploaded now?
[17:13] <knome> err, i mean, what to do next; can i tell our uploader to upload or what :)
[17:14] <infinity> Make sure it's well tested, but yeah, have him upload.  User Interface Freeze doesn't mean "your UI must remain broken". :P
[17:15] <knome> okay, thanks. so when he does, i will see the package name appearing in this channel automagically, and somebody will take care of it after it's uploaded?
[17:15] <infinity> That's the general theory.
[17:16] <cjwatson> if we were frozen ...
[17:16] <cjwatson> there was discussion of that but we don't appear to be
[17:16] <knome> oh, right... :)
[17:17] <infinity> Oh, there's also the not actually frozen part, yes.
[17:17] <infinity> (Didn't we stay frozen between the last Beta and release last cycle?)
[17:17] <skaet> yes
[17:18] <skaet> I'll send a proposal around by email after lunch.
[17:18] <knome> so uh,  i don't even need an exception? :D
[17:18] <infinity> knome: Oh no, you still needed an exception.
[17:18] <skaet> we're still frozen for features,
[17:18] <knome> okay, can somebody throw an ACK to the bug
[17:18] <infinity> knome: The archive not being frozen doesn't mean feature/UI freezes don't need to be respected socially.
[17:18]  * skaet --> lunch biab
[17:22] <infinity> knome: Bug updated with a request for more info, but I'm tentatively fine with the idea.  Broken themes need to be fixed and sane, freeze or no.
[17:22] <knome> okay, thanks
[17:22] <knome> i'll have a look at it :)
[17:30] <micahg> do we have a problem with binaries in a tarball if they're not used?
[17:42] <infinity> micahg: You mean from upstream tarballs?
[17:42] <infinity> micahg: If the binaries are produced from the source in the tabrall, it's distasteful, but allowed.  If they're there without source or any meaningful way to create them, it's generally considered non-free, and should be repacked (or beg upstream to release it properly).
[17:43] <infinity> micahg: In neither situation should the binary be used, of course (either for the build, or shipped).
[17:43] <micahg> infinity: generated in this case :), I just noticed a bunch in the now 400MB chromium tarball
[17:43] <infinity> micahg: It's my impression that chromium upstream aren't complete twits, maybe you could ping them to repack their source without the binaries?
[17:44] <micahg> infinity: it's generated from the repo, no upstream source, I guess I'll just exclude them
[17:44] <infinity> micahg: But yeah, if it's all a product of the source, it's not world-ending, just ugly.  And don't use them in the build or ship them in the final binary packages.
[17:45] <infinity> Oh, if it's produced from elsewhere, yeah, repack a +dfsg tarball or something.
[17:45] <infinity> (Well, don't bother renaming it if you don't want an ugly version number, but you know what I mean)
[17:49] <knome> updated 969252 with diff :)
[18:12] <infinity> knome: Looks good.
[18:13] <knome> thanks, i'll let our uploader know
[18:13] <knome> re: px/no px, i don't know... :)
[18:17] <infinity> Yeah, was just odd.
[18:17] <knome> mm-hmm, i noticed that too ;)
[21:57] <skaet> infinity, slangasek, pitti, cjwatson, Riddell, Daviey - we had someone making inappropriate changes to our TechnicalOverview/Beta* pages.   They should now be locked down by IS to just be editable by members of the release team.
[22:03]  * slangasek nods
[22:05] <skaet> ScottK, Laney, tumbleweed, NCommander, ^  FYI.
[22:25] <Riddell> thanks skaet
[22:26] <phillw> hi guys, before I go prod Julien in the ribs about the modemmanager falling off the standard packages for lubuntu, would he need to request an exception, or are you guys okay with it being a bug-fix?
[22:27] <slangasek> phillw: sounds unambiguously like a bugfix to me
[22:29] <phillw> slangasek: thanks, I'll go poke him in the ribs. Heck, these things happen :)
[22:58] <micahg> what do you think of pulling in the new librsvg from debian that restores the rsvg script for precise?
[23:02]  * skaet figures slangasek or inifinty is better answering that one ^
[23:07] <infinity> micahg: I may need you to elaborate on what that means. :P
[23:07] <infinity> skaet: Inappropriate changes?
[23:08] <micahg> infinity: there are are quite a few rebuild failures due to the rsvg script being removed upstream, Debian decided to add it back until the reverse dependencies are fixed
[23:08] <skaet> infinity,  Ubuntu Kernel -> Linux Kernel a few places too many
[23:08] <skaet> we don't want to get upstream irritated
[23:09] <infinity> micahg: Ahh, yeah, that seems fair.
[23:10] <infinity> micahg: If that's the only meaningful change, go nuts.
[23:10] <micahg> infinity: unfortunately, they didn't multiarch it yet, so it's still a merge
[23:10] <infinity> Good thing you're good at merges, right?
[23:10] <micahg> heh
[23:11] <micahg> I think I've done more syncs than merges this cycle
[23:15] <infinity> skaet: I'm not sure reverting all of those Ubuntu->Linux things wholesale is really a great idea either. ;)
[23:16] <infinity> skaet: Especially not with a commit message of "credit had been given to linux", as if that's somehow a bad thing.
[23:18] <skaet> infinity, language on beta 2 was worked out with kernel team to keep from getting upstream mad at them.   Beta 1 revert was ammended to insert extra "linux" to be explicit to match Beta 2 wording.
[23:19] <infinity> Hrm.  Kay.
[23:30]  * skaet --> eow,  TGIF.  :)
[23:30]  * infinity tosses out beer.
[23:31] <skaet> :)