[00:00] I suspect it related to upstart-job being a virtual package somehow breaking the world here, but... Meh. [00:01] relates* [00:01] I'll give it some more brain time to sink in [00:12] Oh, *urgh*. cups 1.5.3-0ubuntu2 was broken. [00:12] infinity: Can I get a second opinion on this: http://launchpadlibrarian.net/109781750/cups_1.5.3-0ubuntu1_1.5.3-0ubuntu2.diff.gz - you're looking at the postinst, “if dpkg --compare-versions "$2" lt-nl "1.5.3-3"; then”... [00:14] infinity: That looks like it'll break on any upgrade to cups, such as the 1.5.3-0ubuntu3 update that's [00:14] recently been published. [00:24] RAOF: It certainly could, depending on the contents of said file, yeah... [00:25] RAOF: Same broken comparison later in the postinst too. === skaet_ is now known as skaet [00:34] I don't know how widespread the problem is, so I'm not sure quite what to do next [00:34] Also, baby impedes my typing speed [00:37] RAOF, any other evidence that folks are seeing this, or isolated incident? [00:37] (possible user error) [00:38] Still possible user error [00:38] The packaging *is* wrong, though [00:44] RAOF, can you start off a new bug to track the packaging error? [00:51] skaet: bug #1037845 is your winner. [00:51] Launchpad bug 1037845 in cups "[precise-updates] Cups 1.5.0-0ubuntu2 has incorrect postinst" [Undecided,New] https://launchpad.net/bugs/1037845 [00:52] Thanks RAOF. [01:29] infinity, stgraber, any updates on when we'll be getting cardamom and kapok back on line? [01:42] stgraber, infinity - chinese images appear to have built on the buildds now. Am kicking off the rest of the rebuilds for precise on nusakan. [01:45] skaet: I'm back, looking at all the highlights. Will trigger whatever's left [01:46] stgraber, I've kicked off the desktop ones (executed set from pad), if you want to do the alternates and core, that will complete the set. [01:46] right, done catching up, starting a rebuild of everything (might as well) [01:47] full desktop is already building [01:48] all of them... [02:02] skaet: Ok, the poster followed up on that bug; it's still not entirely clear what's happening, but user-error is increasing in probability. [02:03] RAOF, thanks for following up. [02:03] * skaet keeping fingers crossed its user error. ;) [02:14] just an update for anyone reading the backscroll and intersted in the state of the builds... [02:14] full set of precise daily images is being produced and published to iso tracker right now. [02:15] crontab has been turned back on for quantal, so those images should be emerging as well in their regularily scheduled times. [02:15] * skaet --> EOD [02:15] night skaet [02:16] thanks. [03:16] Subject: LiveFS (built by kate) ubuntu-studio-dvd/precise/amd64 failed to build on 20120817 [03:16] skaet: looks like a typo in the pipeline, ubuntu-studio -> ubuntustudio [06:13] Did the -updates regression get passed off to anyone? [06:15] ScottK: The cups one? [06:16] ScottK: RAOF was looking into it further to see if it might actually have just been user error. [06:16] Yes. [06:17] There's a definite chance of user-error; the user has replied on the bug that the bug they replied on is not actually the bug they were seeing. I've asked to verify that they're seeing an actual regression. [06:17] On the other hand, the cups postinst is *definitely* wrong. [06:18] Was it wrong in the previous release or is this new wrongness? [06:18] There was some wrongness introduced in 1.5.0-0ubuntu2 [06:19] There was also some wrongness introduced in 1.5.0-0ubuntu1. I don't think 1.5.0-0ubuntu3 introduced any further wrongness. [06:20] That's all regression-update though. [06:20] Right. [06:21] My vote is fix it ASAP then. [06:21] I need to ask til what the practical upshot of that wrongness is; it looks like it might be as benign as needlessly deleting a cache. [06:22] If that's it, I guess it can wait until after 12.04.1, but since we've got a zero tolerance policy on regressions in updates it needs to be addressed. [06:23] Yes. [06:24] I updated your bug. [06:24] I pointed it at 12.04.1 for the moment. [08:27] are the quantal desktop isos under building now? still can not find them on the cdimage server [08:28] You probably should expect continuing disruption there until the datacentre move is complete. [08:28] i.e. check back next week. [08:28] cjwatson, ack. thanks for the info [08:29] If you get anything today, it's a bonus. :-) [08:30] cjwatson, hehe [09:20] Well, looks like we have i386/amd64 buildds for the images at least. [09:32] ah, someone recronned it [09:36] cjwatson: hey, would you be able to NEW review ubuntu-cloud-keyring please? [09:37] Daviey: It occurred to me while I was offline: any reason this shouldn't just go into cloud-utils, which already includes a keyring? [09:37] cjwatson: well they serve different purposes TBH [09:38] Yes, they would need to be different actual keyring files. But is cloud-utils perhaps already installed everywhere that might want this keyring? [09:38] cloud-utils means installing software people potentially don't need [09:38] So it isn't already installed everywhere relevant? [09:38] hmm [09:39] i didn't think it was in the server seed, but i'll double check [09:39] Only cloud-image apparently. [09:39] OK, so perhaps that wouldn't make a great deal of sense. [09:40] cjwatson: The funny thing is.. this package only really makes sense on Precise. :) [09:41] ie, there won't be an archive series for Quantal [09:43] well, accepted anyway and you can figure out what to do with it in post-precise series later [09:44] cjwatson: thanks. [12:12] uhm, nspr on precise is trying to uninstall my language packs [12:14] infinity: ^ [12:16] oh, hrm, I see they are obsolete packages [12:17] trouble is, update-manager refuses to uninstall packages, so some precise users will be unable to update now [12:19] slangasek: ^ [12:21] mdeslaur: I thought that was debugged in ubuntu2.2 [12:22] https://launchpad.net/ubuntu/+source/nspr/4.8.9-1ubuntu2.2 [12:22] 2.2 is what's causing it [12:22] actually, update-manager seems to now handle uninstalling properly if you go through the "partial upgrade" dialogs [12:24] ok, the partial upgrade worked...so, it's not critical...just probably confusing for users [12:24] no biggie [12:25] mdeslaur: uh, unattended-upgrades will probably hold it back too, what package is causing this? could we do something to woraround it? [12:25] mvo: it's nspr ubuntu2.2, see #1036794 [12:26] oh right, unattended-upgrades...hrm, yeah, we probably need to fix it then [12:27] mdeslaur: its ok(ish) as update-manager will at least popup on the next session [12:29] mvo: assuming the usual user of the machine who has unattended upgrades turned on actually has admin rights [12:29] mdeslaur: yep [13:13] 17:04 < stgraber> hmm, I'm actually wondering what update-manager will do as the upgrader will require removing packages on these weird precise systems [13:13] 17:04 < stgraber> though at least it'll do the right thing when upgrading from oneiric, so that's already a big win [13:13] 17:04 < stgraber> infinity: thanks! [13:13] mvo, mdeslaur: ^ [13:13] 17:05 < infinity> stgraber: update-manager pretty much flat out refuses to remove packages (same as "apt-get upgrade"), but there's not much we can do about that situation. :/ [13:13] 17:06 < infinity> stgraber: Thanfully, we didn't really have nearly as many "normal users" back in jaunty times, and even fewer "normal users" who've probably upgraded through [13:13] all the releases since, so there's a fair chance that anyone in said predicament can hit a console and type "apt-get dist-upgrade", which should work. [13:15] stgraber: why jaunty? this will hit anyone who's upgraded from lucid [13:15] or natty [13:16] stgraber: I don't see how installing natty and upgrading to oneiric and precise is considered to be a "weird precise system" [13:18] cjwatson, thanks for sorting the typo and respinning up the images for ubuntu studio. Have fixed it in the ubuntu-release pad now. [13:19] skaet: I didn't respin [13:21] "* lamont fires off the buildlive command and watches| [13:22] at like 1am today, not sure if it is related. [13:22] xnox: unrelated [13:22] stgraber: oh well... =) [13:23] skaet: rebuilding [13:23] was me, sory forgot to mention [13:23] Laney: oh well, they'll have two rebuilds then ;) [13:23] makes them twice as good [13:23] it was 10ish UK [13:23] thanks Laney. [13:24] mdeslaur: if "installing an old release and upgrading to each new release as it comes out, with the upgrader" is considered a "weird and unsupported system", then we hate our installed base and should all be shot in the head [13:24] stgraber: ^^ [13:25] the original problem only occurred to systems that were upgraded from jaunty, but the fix that went in now triggers an issue for people coming from lucid or natty [13:25] mdeslaur: hmm, I think we somehow missed that language-support-en was only removed in oneiric... the initial problem was with language-support-translations-en which was indeed deprecated after jaunty [13:26] stgraber: yeah, that makes sense [13:26] slangasek: what was the reason for also breaking against language-support-en? I vaguely remember language-support-translations-en being the real problem here [13:26] stgraber: so this is going to hit a _lot_ more users than you had planned [13:27] mdeslaur: yeah, will check with slangasek for the reason of the breaks against language-support-en, we might get away with re-SRUing another update breaking only language-support-translations [13:27] but slangasek rarely does something without a very good reason, so we'll see... [13:28] stgraber: yeah, isn't that annoying? it makes the rest of us look bad :) [13:30] mdeslaur: so, from a UI point of view, what's happening to the user at the moment? do they have to go to a terminal to force a dist-upgrade or can they somehow do it from update-manager? [13:31] stgraber: update manager will give a scary dialog that says updates can't be installed, and suggests trying a partial upgrade [13:31] you then go through a few dialogs that asks to remove packages, etc. [13:32] stgraber: if you use unattended-upgrades, it stops working [13:32] stgraber: ie: if someone changed their preferences to automatically install updates, or in a corporate environment [13:32] right, though in my experience unattended-upgrades stops working every month or so (whenever there's a potential conffile prompt), so users should be used to doing a standard upgrade from time to time [13:33] stgraber: there shouldn't be any conf file prompt on normal desktop systems [13:33] stgraber: or rather, no conf file changes in security updates and srus [13:36] mvo: what happens to unattended-upgrades if there are conf file changes? so it keep those packages back, or does it default to something? [13:36] keeps them back [13:36] stgraber: so the other updates still get installed? [13:36] I mostly see that on my servers/containers with updates like apache [13:36] yeah, it usually updates as many as possible [13:37] stgraber: I believe the partial upgrade situation grinds unattended upgrades to a half [13:37] halt [13:38] mdeslaur: by default keeps it back and notifies about it [13:38] mdeslaur: all the ones that can be installed wil lbe installed [13:39] mvo: ok, and in the partial upgrade scenario, it just aborts? [13:43] mdeslaur: it will skip the package that requires the removal but upgrade everything else [13:43] mvo: oh, good, that's not as bad as I thought [13:43] thanks mvo [13:43] yw === smartboyhw is now known as ubuntustudio === ubuntustudio is now known as smartboyhw [13:47] stgraber, mvo, if you can figure out a safe way to verify that yes, this upgrade really should remove a package, please do so ... I hate that partial upgrade dialog with a passion [13:49] (bug 955022) [13:49] Launchpad bug 955022 in update-manager ""Not all updates can be installed" requires a decision most people can't make" [Medium,Confirmed] https://launchpad.net/bugs/955022 [13:50] I wonder if we could add some metadata, something like "XB-Removal-Ok: old-package-that-really-really-can-go-away" [13:50] i totally agree with the bugreport fwiw [13:50] slangasek, mdeslaur: I uploaded a new nspr to -proposed removing the language-support-LANG Breaks, only keeping the language-support-translations-LANG ones. I'm not sure that'll work, but at least we'll have it in the queue if it does. [13:51] mvo: I think extra metadata on the binary package would be reasonable. That way when we add a Breaks in a SRU we can just add it there too and give a good upgrade experience to the users. [13:51] mvo, and in I included a "These applications conflict and must be removed:" list that could take care of the rest. [13:53] stgraber: that would help with security updates too, we've been doing some crazy things to prevent package removals in security updates [13:53] in preparation for a sru it would be great if the build score for https://launchpad.net/~mvo/+archive/freeglut-multiarch could be raised [13:54] mvo: rescored the individual builds [13:54] mdeslaur, stgraber: that actually makes me wonder if security updates simply should always trump and allow removal, but I guess its safer if we have a allowed-removal list - do you have a good example case where htis is used/needed? [13:54] stgraber: \o/ [13:55] mvo: hmm, I'm wondering, could we get away with a breaks/provides/replaces kind of thing or would that still lead to partial upgrade? [13:55] stgraber: currently I think any removal will cause it to be defensive :/ [13:57] mvo: this was an example I can think of: http://launchpadlibrarian.net/36531850/bind9_1%3A9.4.2.dfsg.P2-2ubuntu0.3_1%3A9.4.2.dfsg.P2-2ubuntu0.4.diff.gz [13:58] wow, 2009, back when I was young and fresh-faced [13:58] ah those were the days [14:02] mdeslaur, stgraber: but I think you have a point about using conflicts/provides/replaces, it could similar honor that and we don't need a extra field or am I missing something? [14:03] mpt: thanks for the spec link [14:04] mvo: both seem equally ugly, so I guess we might as well support conflicts/provides/replaces as it's already part of the standard :) [14:06] stgraber, mdeslaur: were lucid and natty actually installing language-support-en? It hadn't been revved since karmic, and AIUI was supposed to have been obsolete as well. I didn't miss that it was still present in natty, but didn't anticipate that forcing its removal on upgrade would cause problems. Is this actually a problem when dist-upgrading? Or only when trying to install the SRU? [14:07] slangasek: my laptop was installed with natty, and I had it installed [14:07] hmm. [14:07] slangasek: dist-upgrade isn't a problem, it's just causing the problem for people on precise with language-support-LANG [14:07] ok, then it was less obsolete than I believed, sorry [14:08] slangasek: do you expect any problem by removing these from the Breaks? [14:08] stgraber: so we need to test whether the Breaks: on language-support-$thingy-en is enough to get the right lucid->precise upgrade path [14:08] there's a *possibility* of problems if we leave those out [14:09] because apt may go "oh, language-support-en is broken, let's try readding language-support$thingy-en" and it'll cascade from there [14:09] slangasek: right. If you can review my upload to -proposed and accept it, I have a VM I can use to test the new package [14:10] fwiw https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1038113 [14:10] Ubuntu bug 1038113 in update-manager "support conflicts/provides/replaces and allow removal in this case" [Undecided,New] [14:10] mdeslaur: fyi, my system was installed as lucid and I don't have language-support-en installed [14:11] so I don't think "anyone who has upgraded" is accurate [14:11] slangasek: hrm...isn't that the metapackage that gets installed by the language support tool? I usually install in english, and install french using the language tool for testing [14:12] slangasek: I guess we should SRU a new update-manager (can be post-12.04.1) adding these to the obsolete list so the dist-upgrader takes care of removing them [14:12] I'm not quite sure why I had it installed [14:12] * mdeslaur fires up lucid vm [14:14] mdeslaur: can you kill one of the security builds on PPC? they just came back to life and we need to have two SRUs built in the next hour or so (if we want them to make it by the time we freeze) [14:15] slangasek: my pristine lucid vm that's installed using preseeding has language-support-en installed [14:15] mdeslaur: ok, my mistake [14:15] I scored them at 9000 in the past but apparently that wasn't enough to get in front of your security builds... I now bumped to 50000 which should ensure I get the buildd as soon as one of the two security builds disappear [14:15] stgraber: those will be done within that time frame [14:16] jdstrand: good, was affraid it was libreoffice, kernel or some other fun things like that [14:16] no [14:16] there are a lot of things queued, but they shouldn't take long [14:16] well, with my last rescore, I should get ahead of these anyway [14:17] (IIRC private PPAs get 15000 and I rescored at 50000) [14:18] mdeslaur, slangasek: confirmed that a clean 10.04.4 + updates comes with language-support-en and language-support-writing-en [14:19] well, then I guess the alternate CD doesn't do this correctly and it's yet another reason to get rid of the alternates :) === knome_ is now known as knome [14:38] Is anyone on the cups regression in -updates? [14:42] slangasek: running a test upgrader with a locally built nspr [14:49] * cjwatson tries to think of a way to do an HFS+ mount as root during image building [14:49] the hfsplus tools are just complete no-hopers :-( [14:49] I wonder if I could abuse the fact that bits of livecd-rootfs run as root [14:50] lamont: do the livefs builds have specially trimmed-down kernels, or is it possible that I might be able to do mount -t hfsplus? [14:50] Linux kapok 2.6.32-42-server #95-Ubuntu SMP Wed Jul 25 16:10:49 UTC 2012 x86_64 GNU/Linux [14:51] cjwatson: does that clarify things? [14:51] it's not particularly cut back other than being lucid [14:51] So basically a normal Ubuntu kernel image [14:52] I might just about be able to wedge something useful out of that [15:09] slangasek: upgrade succeeded [15:09] slangasek: I'll grep through the logs to ensure it used the new nspr though :) [15:11] slangasek: no mention of -1ubuntu2.2 in the logs, only of -1ubuntu2.3 so that looks like a success [15:11] will mark the bug verification done [15:22] jibel: can you re-trigger the jenkins upgrade for 12.04.1 (these with -proposed enabled)? [15:22] want to check we don't get any regression with the nspr in proposed [15:25] stgraber, started profiles desktop, server, server-tasks for lucid and oneiric. main and universe are scheduled to start in 90min [15:25] thanks [15:25] stgraber: great, thanks! [15:26] slangasek: I think we should copy directly to -updates once we have the result from Jenkins. I know it's Friday but I don't see how that change can make it any worse ;) [15:26] stgraber: agreed, this is effectively an SRU regression [15:26] speaking of which, let me catch up on this cups thing [15:29] knome: so, xfwm4 is finally built on all architecture. Do you guys want it pushed to -updates today so it makes it by freeze time (in 30 minutes) or do you prefer to wait until Monday, meaning the Xubuntu images built today won't be true candidates. [15:29] oops, forgot to rescore nspr on powerpc... done now, should be built soonish [15:32] ScottK: I'm confused by bug #1037845; we're never going to have 1.5.0-3 in precise-updates, true, because the version in precise is already greater than this [15:32] Launchpad bug 1037845 in cups "[precise-updates] Cups 1.5.0-0ubuntu2 has incorrect postinst" [High,Confirmed] https://launchpad.net/bugs/1037845 [15:34] slangasek: Isn't 1.5.0-0ubuntu2 < 1.5.0-3 [15:36] ScottK: certainly, but that's not the version we have in precise [15:36] cups | 1.5.2-9ubuntu1 | precise | source, amd64, armel, armhf, i386, powerpc [15:36] cups | 1.5.3-0ubuntu3 | precise-updates | source, amd64, armel, armhf, i386, powerpc [15:36] Both of which are < 1.5.3-3 [15:37] So I'm now confused about your confusion. [15:37] ScottK: you just said < 1.5.0-3 (15:34 UTC) [15:37] Can't type [15:37] Meant that. [15:37] Oh. [15:38] Can't read either. [15:38] You're sorted, then. [15:38] Yeah. [15:38] RAOF: ^^^ so that's not the problem. [15:38] right, the condition will never match, so not a problem [15:38] Yeah. [15:38] There's still apparently some undiagnosed issue with Bug 973270 [15:38] Launchpad bug 973270 in system-config-printer "Printer does not provide REQUIRED job history." [High,Fix released] https://launchpad.net/bugs/973270 [15:42] balloons: do we have any non-zero number of currently-engaged community Mac testers? [15:42] in which the commenter says his bug is probably actually bug #995111 [15:43] Launchpad bug 995111 in cups "Print failure since upgrade to 12.04" [High,Fix released] https://launchpad.net/bugs/995111 [15:43] balloons: I am in the middle of an evil plan, but it only works if I can get it validated on some Macs [15:43] cjwatson, by mac do you mean ppc or amd64mac? [15:43] We have one, sometimes two for Kubuntu. [15:43] balloons: the latter [15:43] shadeslayer: ^^^ [15:44] k.. then yes, we have some [15:44] ideally a range of models [15:44] sec, need to read the backlog [15:44] I know at least one persn with a imac and a couple with macbook pros [15:44] cjwatson: hey hey, I have a mac :) [15:45] I was told that the amd64+mac iso was there because the standard ISO can't boot on some machines [15:45] cjwatson: if you just need to boot a media to check the xoriso change, I can probably borrow jocarter's mac ;) [15:45] stgraber: well, I did commit a preliminary change earlier today yes, but that's not the whole thing [15:45] I also have a technique that allows you to EFI boot the ISO using GRUB's loopback mechanism, though I haven't documented it anywhere [15:46] so I'm working on incorporating something that's roughly equivalent to the technique used in Fedora [15:46] \o/ [15:46] I'm having to be a bit creative, because the Fedora approach relies on being able to loop-mount a filesystem as root [15:47] oh, that explains the hfsplus question ;) [15:47] I *think* that if I rely on all the features of xorriso 1.2.4 that I can lay my hands on and run it twice, I can work around that [15:48] (because it has code to generate ISO9660/HFS+ hybrid filesystems, and I can by definition presumably rely on that being readable as HFS+) [15:49] cjwatson: any plans for the install stage ? [15:49] what I'll want to do is generate a test ISO and get people to boot it on as many Macs as possible, and find out (a) whether it boots at all (b) what the boot screen looks like (c) whether it boots as BIOS or UEFI (d) what ubiquity does as a result [15:49] ev: errors still gives timeouts for all the lists... what's the status of breaking out the launchpad bits? [15:49] I'm particularly interested in d) [15:49] slangasek: RT 55342 [15:49] I will probably need somebody with hardware to work on that [15:50] but hopefully the answer can be that it just does an EFI install [15:50] slangasek: webops is in the middle of a datacenter move this weekend, so getting deployments out is unlikely to occur before monday [15:50] cjwatson: oh and fwiw, there's a bug in X where it tries to address out of bound memory under EFI boot [15:50] ( macbook pro 8,2 ) [15:50] well that's unfortunate, perhaps you could harass the X people? [15:50] cjwatson, ohh. awesome.. so this would let us drop the amd64+mac iso? [15:50] ev: phooey, escalating [15:50] if so.. you better believe I'm all for helping make it happen :-) [15:50] ev: why are we not being all devops on this? :) [15:50] balloons: that's the intention, but it relies on quite a lot of bits [15:50] slangasek: :) [15:51] cjwatson: one just needs to put this into xorg.conf : http://paste.kde.org/536090 [15:51] but yeah, the X people would know [15:51] shadeslayer: X needs to auto-figure-that-out by default, then [15:51] slangasek: charms of the infrastructure are in progress, but so are lots of things [15:51] *nod* [15:51] we aren't going back to the bad old days of writing xorg.conf [15:51] especially not during live CD boot :) [15:51] hehe :) [15:52] cjwatson, yes.. let's put up an image, and I'll put together a mini call for testing specific for mac users [15:52] I do miss hand rolled mode lines [15:52] slangasek: ^- FWIW the other purpose of this plan is making EFI USB hybridisation work [15:52] just saying that just getting EFI boot is not enough ;) [15:52] slangasek: I think the change I committed to debian-cd earlier today should take care of that [15:52] shadeslayer: yeah, I know, but I suspect it's a more viable forward path [15:53] balloons: before doing that, I think I'd like to work with one or two people like shadeslayer directly - since otherwise if it's completely broken I'll be swamped [15:53] cjwatson: yes, I'm sitting here cackling gleefully at the discussion :) [15:53] :) [15:54] feel free to ping when you have a ISO, it'll take a bit of time since my connection is a bit slow, but I can surely help [15:55] it'll take even longer to squeeze up my connection, I expect [15:56] ^_^ [15:56] shadeslayer: do I recall correctly that your Mac(s) boot the amd64 images natively? [15:56] as EFI? [15:56] cjwatson: yes [15:57] I mean, leaving aside X and installer troubles [15:57] I can even install it, just need to pre partition the disks [15:57] OK; ideally I'd also like coverage from systems that don't, but perhaps that can be the second stage [15:57] cjwatson: however, if I write the image to a usb, the system doesn't boot the USB [15:58] I have to take special measures to partition the USB, write grub efi to the USB, etc [15:59] * xnox managed to boot EFI usb sticks, if in Mac OS X I wrote into nvram that the usb stick is blessed for next boot only [16:01] cjwatson, yes,. I wouldn't push it out to tons of people [16:01] I have a couple in mind I would ask directly [16:02] shadeslayer: Most of that may just be hacks in the installer to try to avoid doing things on Macs that previously didn't work [16:02] ah :) [16:03] cjwatson: any progress on the lb merge? [16:03] infinity, hey, did you break nvidia users on purpose by moving the xorg stack from quantal-proposed to quantal? ;-) [16:04] infinity, e.g did you know there was issues with nvidia? [16:04] seb128: not to mention ATi users :P [16:04] ATI users can use the ati driver [16:04] it's harder to use nouveau [16:04] shadeslayer: not as yet sorry [16:04] card too new [16:05] cjwatson: ah ok ... because my merge is a bit screwed up, the iso it builds doesn't boot, doesn't have a boot/preseed/other files and folders [16:05] just isolinux and casper :P [16:06] cjwatson, ping and send me the link as well [16:06] I'll onboard a couple folks to test [16:07] balloons: I'll let you know when I'm ready; I'd prefer to work with a single person initially [16:07] cjwatson, yes.. don't want to overload [16:07] ok, why in the world am I looking at bug #837054 [16:07] Launchpad bug 837054 in ubuntu-geonames "Time Zone selection shows about 20 different "New York"s and doesn't autoselect my location" [Medium,Confirmed] https://launchpad.net/bugs/837054 [16:10] slangasek: because it takes time to scroll past New York, before you get to 17 Portlands? [16:11] slangasek, because plan moving to new york and want to know about the dangers in advance ? [16:11] xnox: no... someone must have mentioned this bug somewhere, but I've now lost track of the reference [16:21] dobey, we're contemplating letting ubuntuone-installer, ubuntuone-sso-client in to 12.04.1 without 7 day period in proposed? what is the testing confidence like, how great is the regression risk? [16:21] slangasek, stgraber, Daviey, ^ [16:22] seb128: Blame tjaalton, he's the one who told me it was good to go. [16:22] Riddell: can you please do qt4-x11 uploads to quantal-proposed, not to quantal? As a core library, architecture skew has an impact on multiarch installability of the dev release [16:22] infinity, I though it was clearly flagged last week that nvidia was broken :-( [16:22] the risk is minimal i think. there's basically no risk for ubuntu-sso-client. there's a little more risk with ubuntuone-installer as the main fixes are basically an invasive behavioral change (not ignoring errors where we once were before), but i don't think there should be any new crashes in installer as it should just show the errors in the UI now and let the user retry or cancel [16:23] slangasek: mm right, yes [16:23] skaet: is that informational only, or is there a question for me? [16:23] Riddell: ok, thanks :) [16:23] slangasek, for information only, and a chance to raise concerns ;) [16:23] When did it become a policy that only X updates with binary only support were allowed in the development release? [16:23] slangasek: when uploading to -proposed is there a convenient way to remind yourself when it's ready to be copied over or do you just have to check back lots? [16:24] infinity: As far as I can tell it was 'ready'. [16:24] Riddell: I think infinity has made the copies his problem :) [16:24] thanks dobey, stgraber, you ok with including it too? [16:25] I still want to look at errors.ubuntu.com first, but if nothing bad showed up there (when it eventually loads ...), we should be good [16:26] stgraber: per-package reports should still load I think [16:27] Riddell: Yeah, until the automation is all sorted, I just look at the list occasionally, it's not rocket surgery (except when people decide to stage a large transition there). [16:27] stgraber, how much time with errors.ubuntu.com before it makes sense to spin the first set of images? [16:27] skaet: I'm looking at it now. Other issue is cedarview... at this point if we want candidates, that means they'll miss .1 [16:28] skaet: as they haven't been tested [16:29] stgraber: All it takes is verifying jockey DTRT by one person. Surely, someone with hardware in, say, PES, can make that happen. :P [16:29] * infinity pokes jmleddy again. [16:30] Or, rather, I would poke him, were he online. [16:30] I'm going to think really hard about poking him and see what happens. [16:30] skaet: ubuntu-sso-client looks good, no spike on the release in -proposed [16:32] skaet: nothing scary for ubuntuone-installer either [16:32] skaet: so these two are good to go I think [16:32] still waiting on knome for xfwm4 [16:36] awesome [16:43] slangasek, infinity: can one of you please release ubuntu-sso-client and ubuntuone-installer? [16:43] I'll keep monitoring errors.ubuntu.com for the next 5 hours in case we missed something [16:44] stgraber: Sure. [16:45] stgraber: what's our rollback plan if there are problems? [16:45] because we can't assume there will be time to fix any regressions before 12.04.1 [16:46] slangasek: re-upload of former version with an ugly version number [16:46] dobey: ^^ you're ok with that rollback plan in the event of a regression? [16:47] i guess so [16:47] ok [16:47] infinity: pull the trigger (if you haven't already) :) [16:50] slangasek: I can pull it again, if you like echoes. [16:50] nah [16:50] stgraber, for what? [16:51] stgraber, ah, today works if you can do it. :) [16:52] knome: are you happy with the same plan as dobey? that's if anything breaks in the new xfwm4 we simply revert to the previous version for 12.04.1? [16:53] stgraber, sure. i don't expect anything to break though :) [16:53] stgraber: https://errors.ubuntu.com/?launchpad=false for more reliable loading [16:54] slangasek: yay! [16:55] infinity: based on the above, can you also release xfwm4 please? [16:56] stgraber, infinity: thanks [17:02] stgraber, sounds good. [17:05] stgraber: Copied, BTW. [17:05] thanks [17:09] * slangasek reopens bug #734376 for seb128_ [17:09] Launchpad bug 734376 in jockey "jockey-gtk crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.NoReply in shutdown()" [High,Triaged] https://launchpad.net/bugs/734376 [17:09] slangasek, thanks, I wish we had a maintainer for jockey :-( [17:09] seb128_: no one on desktop team is maintaining it? [17:09] slangasek, same as that half a dozen list of unmaintained component that get most of the top issues atm that I listed on one of my -release emails [17:10] slangasek, no, in fact it's deprecated in quantal, the only one who ever really worked is pitti and I think he lost interest for it, especially since he move to Qa [17:11] jibel: how are the Jenkins tests going? [17:11] slangasek, same as update-manager, update-notifier, sessioninstaller, etc [17:11] "Deprecated in Quantal" is no reason to not maintain it in previous LTSes... === seb128_ is now known as seb128 [17:11] seb128: incorrect; update-manager and update-notifier are maintained by the foundations team [17:12] slangasek, ok, so jockey is "maintained" as well ;-) [17:12] it's as maintained as update-manager and update-notifier are [17:12] seb128: I'm not handwaving definitions here. Foundations ported update-manager and update-notifier to python3, and we've fixed the top crashers for them in 12.04.1. [17:13] they're on the list of packages owned by foundations, and we're responsible for keeping them in working order [17:13] I would expect the same to be true for desktop and jockey [17:15] slangasek: did you have a chance to look at the logs I posted at http://www.stgraber.org/download/bug1017001/ ? [17:16] slangasek: based on the discussion with infinity yesterday it seems to be linked to upstart-job being virtual (provided by upstart) and that somehow messing with the resolver [17:16] stgraber: I've looked at them but they don't really give me any more insight on how to resolve this [17:16]