[00:04] cjwatson: I don't have the context of the conversation, but if you need my team to flag certain packages for some reason and coordinate that with you, let me know and we'll make that happen [00:05] cjwatson: (referring to the libssl conversation in backscroll) [00:09] jdstrand: this is specifically to do with ABI changes and d-i not respecting versioned dependencies [00:09] shouldn't be a problem for security updates [00:09] ok, thanks [00:09] we're here if you need us :) [00:10] d-i is good now.. thanks :) [05:39] Good morning [05:44] cjwatson: FYI, cd image cronjobs on manual now [05:54] cjwatson: I set OFFICIAL="Beta" in cdimage now; that's a reason to rebuild everything, marking in the tracker [05:54] err, pad [05:54] pitti: I think that needs to be set to 'Beta 2' to avoid confusion [05:55] (it was set to 'Beta' last time rather than 'Beta 1', but at least 'Beta 2' will still be unique) [05:55] slangasek: oh, ok; I wasn't sure whether that gets parsed and compared anywhere [05:55] I believe it winds up in the iso diskinfo [05:55] I don't think it's *parsed* anywhere, but it's confusing to have two images called 'Beta' [05:56] hm, beta-2 to be safe, or do you know that a space works? [05:56] tools like usb-creator parse the version (but that comes much ealier in the string) [05:56] * pitti digs history for lucid [05:57] I'm reasonably certain that 'Beta 1'/'Beta 2' was what we used last cycle [05:57] ahh, there's precedent for "beta 2", nevermind [05:57] done [05:58] cheers [05:58] * slangasek wanders off to bed now [06:56] pitti, IIRC wubi uses this info to identify the image and the regex fails if there is a version in the sub-version e.g Beta 2 [06:56] jibel: bonjour [06:56] pitti, morgen :) [06:56] jibel: oh, so did that break in hardy/lucid/oneiric as well? [06:57] pitti, In natty I think [06:58] unless that was fixed in wubi, let me check [07:00] pitti, it is the regex used by wubi to parse disk/info [07:00] disk_info_re = '''(?P[\w\s-]+) (?P[\d.]+)(?: LTS)? \"(?P[\D]+)\" - (?P[\D]+) (?Pi386|amd64) \((?P[\d.]+)\)''' [07:01] so it still fail with "Beta 2" [07:06] jibel: ok, thanks; so I better change that to Beta-2 [07:07] jibel: done [07:08] https://launchpad.net/ubuntu/precise/+bugs?field.milestone%3Alist=44328 [07:08] hmm, 43 bugs [07:12] * pitti gardens them a bit [07:22] ^ csync is unseeded, and a no-change rebuild to fix uninstallability, accepting === rsalveti` is now known as rsalveti [07:46] pitti: I still want to kill sqlite2, but I guess the rebuild's ok (will send e-mail to -release when I'm ready to work on it) [07:47] micahg: thanks [07:47] micahg: yeah, at least it's installable now [07:47] pitti: being that no one's complained yet, I'm guessing it's not very used [07:47] micahg: it was an easy thing to get off the beta-2 bug list; sorry if I got in your way [07:48] pitti: not at all, only reason why I added to beta 2, was I was hoping to have sqlite done by now [07:48] pitti: actually, was tempted to ask you to remove [07:49] csync, not sqlite [07:49] can do that as well, if there's a good reason for it [07:49] if it's the only package that still uses sqlite2, that would be a good reason :0 [07:49] pitti: sqlite2 deprecated :), I guess at this point, it might as well wait until the rest of the sqlite cleanup === mmrazik is now known as mmrazik|lunch [09:36] https://launchpad.net/ubuntu/precise/+bugs?field.milestone%3Alist=44328 is a bit shorter now [09:58] * cjwatson has a look through archive admin bugs [09:59] * Laney arghs at still not having filed the other haskell removal one === greyback is now known as greyback|lunch [10:02] newlib should be safe despite being in main; it's only there for newlib-spu which is a build-time-only thing only on powerpc [10:07] Laney: https://bugs.launchpad.net/ubuntu/+source/haskell-attoparsec-text/+bug/955521/comments/3 [10:07] Launchpad bug 955521 in haskell-xml-enumerator "Various discontinued Haskell packages to remove from precise" [Undecided,Confirmed] [10:09] and comment 4 [10:09] yeah there's some yesod syncage to do [10:10] and hledger-web [10:11] yeah [10:11] brb === mmrazik|lunch is now known as mmrazik [10:41] i'm syncing some more stuff which should make the rdeps go away === greyback|lunch is now known as greyback [10:54] * Laney pulls at threads [11:01] cjwatson: thanks for the newlib fix, accepted [11:02] cjwatson: FYI, I'm accepting the GNOME 3.4.0 bits; they go into -proposed, and only update translations [11:02] OK; do you want to get them onto beta-2 images? [11:02] so that we can stash up 3.4 in -proposed, and move it to precise after the freeze [11:03] ah right [11:03] cjwatson: I see no need for this [11:03] translations are stripped anyway, and we dont' get new b2 langpacks [11:03] cjwatson: it's mostly for seb128 to get them out of the way, and in -proposed they avoid arch skew [11:03] I mean uninstallability due to arch skew [11:04] certainly [11:04] hum [11:04] https://launchpadlibrarian.net/98386576/buildlog_ubuntu-precise-armel.gnome-panel_1%3A3.4.0-0ubuntu1_CHROOTWAIT.txt.gz [11:04] "bzip2: Data integrity error when decompressing." [11:04] erk [11:04] does it mean the builder is buggy? [11:05] I think I'd be inclined to just mash retry [11:05] that sounds like a network transmission error on the chroot [11:05] and bzip2 has done part of its job and spotted it [11:05] thanks [11:05] if it happens multiple times we can be more worried [11:06] hmm, seems nusakan didnt do the DST switch ... i just got the daily health checks mail 1h late [11:06] (or didnt the uk switch ?) [11:07] cjwatson, https://launchpadlibrarian.net/98386775/buildlog_ubuntu-precise-armel.gnome-panel_1%3A3.4.0-0ubuntu1_CHROOTWAIT.txt.gz [11:07] it's intentionally on UTC [11:07] cjwatson, same issue on second try [11:07] (same build, caph) [11:07] oh ... silly me, indeed [11:07] seb128: hmm - ask #launchpad-ops (internal) [11:07] builder [11:07] cjwatson, ok [11:07] all servers should stick to UTC :) [11:07] Daviey, all the world should :) [11:07] would aviod me getting confused [11:07] ogra_: I'm happy to stick my working day to UTC :) [11:09] cjwatson: I found a fix for bug 963069, the breaker du jour for the lucid->precise universe auto-dist-upgrade test [11:09] Launchpad bug 963069 in gtk+2.0 "Lucid -> Precise universe: pkgProblemResolver::Resolve generated breaks - does not replace gir1.0-gtk-2.0 with gir1.2-gtk-2.0" [High,New] https://launchpad.net/bugs/963069 [11:09] cjwatson: would you consider accepting this for beta-2 at this point? it's just adding a new Conflicts: [11:09] err, breaks [11:10] I'm test-building locally now to ensure it still builds [11:10] cjwatson: I can also use -proposed if you want [11:11] what's the state of image testing? [11:12] a few tests registered, not lots [11:13] so yeah, I'd consider it [11:16] cjwatson: we need to rebuild everything anyway still, for the OFFICIAL change [11:21] oh, you didn't do that already? OK [11:21] cjwatson: I did it this morning [11:21] but images haven't rebuit since then [11:22] cjwatson: and I updated it to say "Beta-2" instead of "Beta 2" to avoid breaking wubi (cf. jibel's ping around 0700 UTC here) [11:26] sure; for lucid we just said Beta in both cases [11:27] I'm actually fairly sure that "Beta 2" would have worked in the specific case of wubi; jibel misread the regex [11:27] ... actually, both of them break equivalently, thinking about it [11:28] \D matches anything that's not a digit [11:28] hm, so just "Beta" after all? [11:28] I understand slangasek's point about confusion, but I think avoiding triggering bugs ought to take precedence [11:29] +1 [11:29] and that's only for the .disk/info stamp, right? [11:29] or does it go anywhere on the .html pages? [11:29] (these are edited manually anyway) [11:29] html is done separatey [11:29] +l [11:29] and the .iso file names are a publish-release argument [11:32] * pitti adds ^ to the etherpad [11:34] accepted [11:35] thanks [11:36] cjwatson: I'll move it to precise once it's built everywhere [11:36] erk, powerpc build ETA in 15 h [11:37] seems the wesnoth backports own the ppc builders for a while [11:38] wesnoth is release critical [11:41] oh, blast, I was just clearing them while I remembered. surely you can just score things up though? [11:42] otherwise feel free to ask #launchpad-ops for build cancellations [11:43] cjwatson: scoring doesn't help, already tried [11:43] cjwatson: yeah, will do that [11:44] * pitti questions the utility of maverick backports at this point.. [11:45] cjwatson, pitti: #launchpad-ops sorted the armel builder issue btw [11:45] seb128: cool, thanks [11:56] gtk+2.0 ppc building now [12:33] just subscribed release-team for bug #963498 [12:33] Launchpad bug 963498 in ubuntustudio-default-settings "[FFe] menu is not ubuntu studio version" [Undecided,New] https://launchpad.net/bugs/963498 [12:34] cjwatson: FYI, out for doctor appointment for ~ 1 hour; gtk 2.0 still building :/ [12:35] pitti: ok [12:35] scott-work: I'm not sure I see why this is an FFe; isn't it just a bug? [12:36] cjwatson: i would think this is just a bug and could be addressed without the release-team's approval, but i was just being cautious [12:37] confirmed anyway [12:38] cjwatson: thank you [12:38] i think there is a bit of a culture in some quarters to be cautious about bugs after freezes...perhaps, overly cautious, i will try to be more judicious in the future however [12:47] it's fine to be cautious, but don't hamstring yourself :) === bladernr_afk is now known as bladernr_ [13:13] fyi, I just sponsored a freetype upload to precise for security updates. it is not required for beta-2, but is fine if it is pulled in [13:21] cjwatson, the unity guys might have a fix for https://bugs.launchpad.net/ubuntu/+source/unity/+bug/963633 (or a best a partial fix) [13:21] Launchpad bug 963633 in unity "Unity 5.8: Login to blank screen (all black or just wallpaper)" [Critical,In progress] [13:21] cjwatson, dbarth has more info [13:22] OK, they can ask somebody from desktop to apply it to the package as a patch, and then we (release team) can review it once it's in the queue [13:22] cjwatson: hi [13:22] or one of their own people with upload privileges if possible [13:22] until then it doesn't need to go through me :) [13:22] we're testing a small fix in the gconf backend from which we suspect the hangs and corruptions come from [13:22] cjwatson, more of a heads up that a respin will be needed [13:23] pgraner: we haven't spun yet [13:23] it's 4-5 lines of changes, but means a respin would be needed to integrate the change [13:23] the existing images still say alpha, we were waiting for gtk+2.0 to land [13:23] cjwatson, ah ok, I thought we had spun then nevermind.... [13:23] but certainly if you could get something uploaded ASAP rather than later that would help [13:23] * dbarth hopes we'll beat gtk+2 [13:24] I doubt it, it was well on its way building [13:24] ugh, well [13:52] question! We found a security issue on ubuntuone-client on friday. We have fix today, is there ay chance of uploading a fixed package? [13:57] you can in any case upload to the queue, letting the package in is a manual process during beta freeze [13:58] ogra_: thanks! [13:59] (assuming you talk about precise indeed :) ) [13:59] ogra_: yes, this is for precise. So, just dputting to ubuntu will leave the package in the proper queue? [13:59] (hi there!) [13:59] nessita: yes [14:00] nessita, right, you should see it being announced here by the queuebot [14:00] ogra_, cjwatson: thanks! [14:02] ralsina: is this only in the precise version? [14:02] jdstrand: yes [14:02] ok [14:26] pitti: FWIW most of my sponsored uploads from today can happily wait for post-beta2; in particular I'd prefer if busybox weren't accepted [14:26] cjwatson: ack [14:26] it's not a disaster if it is but I'd have to respin d-i [14:29] pitti: pgraner/dbarth asked for us to wait until they've got a fix for bug 963633 uploaded before we start rolling images [14:29] Launchpad bug 963633 in unity "Unity 5.8: Login to blank screen (all black or just wallpaper)" [Critical,In progress] https://launchpad.net/bugs/963633 [14:29] (scrollback ~ 1 hour ago) [14:29] cjwatson: I was told this only affects upgrades [14:29] but ok [14:29] pitti, no true I got it on a freshly installed system as well [14:29] s/no/not/ [14:30] pgraner: ah, thanks for the update [14:37] Daviey, today's CD report still has server amd64 oversize. Will we get one today that fits? [14:42] skaet: Today's was built before i made nay changes. :) [14:42] hold out.. still on track. [14:43] :) ok [14:51] skaet: sorry for being brief, otp [14:52] Daviey, np [14:59] hi skaet and dbarth [15:00] cjwatson, pitti, pgraner: sorry to report that the fix we were on is not working so far [15:00] so, it will take us still a couple of hours to confirm a fix [15:01] perhaps we should go ahead and spin images anyway? [15:01] hiya rickspencer3, about ^ ? [15:01] skaet, https://bugs.launchpad.net/ubuntu/+source/unity/+bug/963633 [15:01] Launchpad bug 963633 in unity "Unity 5.8: Login to blank screen (all black or just wallpaper)" [Critical,In progress] [15:01] gtk+2.0 armhf/armel are in pkgbinarymangler stage [15:02] i don't think we can give you a fixed package within the next 2-3h [15:02] :/ [15:02] but I guess if we'll respin anyway, or don't care about gtk 2 being out of date on the images, that's not a blocker [15:02] skaet, my gut tells me that unity is not going to be shippable before tomorrow [15:02] rickspencer3, +1 [15:03] I'm watching didrocks et al debug it ... they are working hard, but there are no easy answers [15:03] pitti, can we revert the pocket copies, and go with the original one? [15:03] (ie. one at freeze) [15:03] skaet: for unity? no, we can't [15:04] we could upload the whole stack as 5.8+really5.6 again [15:04] in -proposed [15:04] and then move over everything in a couple of hours when everything is built [15:04] pitti, skaet I would propose that we set a deadline for such a reversion [15:04] pitti, might be prudent to do that then, and if no resolution by the time it builds. [15:05] we switch over [15:05] yes, sounds good to me; not sure if we also need to revert the compiz bits, or just unity [15:05] skaet: reverting as +really5.6 is a giant mouthful [15:05] didrocks: ^ ? [15:05] do we REALLY want that? [15:05] I don't mind setting a deadline for it, but I don't like the idea of doing it up-frfont [15:05] I would propose that we prepare to do that tomorrow [15:05] *up-front [15:05] well, it doesn't impact beta2 as per see, the issue are only on upgrade [15:05] give the unity team 1 day to sort it out [15:05] didrocks: pgraner says otherwise [15:06] hum, for the interface not showing? [15:06] didrocks, ^ comments from pgraner... [15:06] cjwatson, I hit the blank desktop on a fresh install about an hour ago [15:06] -> didrocks [15:06] pgraner: ah, can you please talk about it to duflu? he's on something else then [15:06] there are 3 bugs in fact [15:07] dbarth, didrocks, how tightly is compiz tied in with unity fixes? [15:07] cjwatson, a netboot install then a apt-get install ubuntu-desktop and a reboot [15:07] and everyone is puzzled in it [15:07] skaet: we can revert compiz only, we didn't try it [15:07] skaet: because new compiz + old unity showed the hang that we workarounded [15:08] didrocks, so, best advice is to revert the entire stack and have it ready in proposed to switch to? [15:09] if we don't get this sorted by end of day? [15:09] skaet: well, reverting the stack will take some hours still, so I continue to work like hard and try to get dx people on board… [15:09] also reverting the stack will make it harder for people to reproduce and help ... [15:09] skaet: the revert will take approx 5 hours to proceed with the dep chain [15:10] cjwatson, pitti, skaet, didrocks thoughts about letting the unity team work for the next 24 hours to fix the bugs, and then work on reverting if it's not substantially closer to be being solved tomorrow? [15:10] we could do with a bit under 24 hours really [15:10] that gets really tight then [15:11] rickspencer3, not sure we have 24 hours, need to get the testing happening, and there could be follow on problems [15:11] agree with cjwatson , if we want to test it properly [15:11] that means we'd be looking at candidate images Wednesday morning [15:12] yes, particularly if we revert the whole stack that means it will take another 5 hours for the fix to build as we have to unrevert everything [15:12] and adds that much more source of human error [15:12] suggest we have until 1900 UTC and then decide, revert or not. And then have the images built. [15:12] perhaps something like "give them 24 hours, and stage a reversion in -proposed in parallel when there is no solution in sight in 16 hours"? [15:12] pitti, that works for me [15:13] pgraner: so, when you upgrade [15:13] didrocks, uploading reverted stack - when? [15:13] do we have any idea what percentage of users this affects? [15:13] skaet: well, if I upload the reverted stack now [15:13] that would mean nobody more will work on the fix [15:13] seeing as I'm the only one active on it… [15:13] didrocks: no need for "now"; we need it (fix deadline minux 5 hours) [15:13] are we sure it affects lot of "new install"? [15:13] what! [15:14] everybody who did a unity --reset got it fixed so far [15:14] didrocks: why not, don't they want to fix it asap? [15:14] err, shoudln't the whole DX team be all over this? [15:14] it seems out pgraner most issues are upgraded profiles [15:14] seb128: seems not, with his new install + ubuntu-desktop metapackage [15:14] pitti: … [15:14] * cjwatson wonders if pgraner has a separate bug; after all the symptom is quite generic-sounding [15:14] seb128, I don't know, I hit it like I said with a net install with the alternate installer then did a apt-get install ubuntu-desktop, rebooted and got the blank screen issue [15:14] hmmm [15:15] that's quite a special install [15:15] that seems rather round-a-bout [15:15] not a standard desktop install [15:15] do we have any proof it happens with desktop images? [15:15] perhaps worth a file-by-file comparison of that with a standard install [15:15] can someone who has the bug from upgrade do a fresh install and see it happens? [15:15] also reverting would make us loose 1 week or trying to get that issue fixed for final [15:15] rickspencer3: until now, I didn't see any of this [15:15] we can't stay on 5.6 for the lts [15:15] cjwatson, let me burn a usb stick and install on the same box [15:16] can someone take the responsibility of determining the scope of the problem? who is impacted (only upgraders?) and how many upgraders are impacted? [15:17] pgraner, someone from QA? [15:17] rickspencer3, sure jibel and I will work this [15:17] bug 957805 is the oldest dupe, and reported against oneiric already [15:17] Launchpad bug 957805 in unity "Black screen after update on unity (with solution) (dup-of: 963633)" [Undecided,Confirmed] https://launchpad.net/bugs/957805 [15:18] Launchpad bug 963633 in unity "Unity 5.8: Login to blank screen (all black or just wallpaper)" [Critical,In progress] https://launchpad.net/bugs/963633 [15:18] aside from that, it piled up some 25 dupes over the past two days [15:19] pitti, so it seems very widespread to you? [15:19] so I think the first dupe was something diffent, or 5.8 just greatly aggravated the conditions under which this occurs [15:19] pitti, indeed, which indicates its going to be fairly common, and critical is not unwarrented. [15:19] yes, I think critical is appropriate [15:20] pitti, can we tell why some people get affected and some don't? [15:20] one issue to consider is that going through with that will increase the chances to get it fixed by hard freeze, rolling back will put us behind on the goal [15:20] just to have all options on the table, we could also release on Friday, couldn't we? [15:20] rickspencer3: I can't [15:20] pitti, yes, we could release on Friday [15:20] but, let's not :) [15:20] it's not my favourite either, as it extends the freeze quite a bit [15:21] but we have -proposed for staging uploads, if people really want to [15:21] let's stick with Plan A (fix Unity) if at all possible [15:21] I'm fairly sure that's everyone's favourite :) [15:22] so, unity --reset works for most of cases [15:22] * skaet nods [15:22] but can we ask for some more DXers to help out with this, instead of just didrocks? [15:22] we can even envision doing the settings revert ourselves [15:22] pitti: well, that's why I'm trying since this morning [15:22] duflu was on it, but it's late for him now [15:22] pitti, dbarth said duflu is working on it as well. [15:23] and he's not around anymore [15:23] it's like 2am for him yeah... [15:23] * skaet thought that was sam? [15:24] there's bug 965390 as well; we could debate critical or high for that, but at any rate it looks like an easy fix [15:24] Launchpad bug 965390 in ubiquity "prompt to remove cryptsetup on an encrypted LVM install during end user setup" [Critical,Triaged] https://launchpad.net/bugs/965390 [15:25] (the alternate-ness there is not intrinsic; if we supported that partitioning mode on the desktop CD, as we'd like to do for Q, it would have the same problem there) [15:26] skaet, sam and duflu both live in australia and both work on compiz [15:26] thanks seb128 [15:26] damn that round planet anyway [15:26] cjwatson: sounds like we'd have plenty of time to accomodate that fix.. [15:27] * skaet nods [15:27] cjwatson, you going to be working on that fix? [15:28] yes [15:28] * skaet can take over kicking images out later today [15:28] just need half an hour or so for a test install to make sure I know the right fix [15:28] * skaet nods [15:29] skaet: we could then at least start building the non-ubuntu images and the ubuntu arm preinstalled [15:29] * pitti wonders what's up with that gtk-2.0 build -- it's been sitting at pkgbinarymangler for an hour [15:29] pitti, yes, that seems appropriate. [15:30] skaet: oh, edubuntu has compiz, too [15:31] get a webops to attach strace or get a ps dump or something? [15:31] * pitti asks in the channel [15:45] * didrocks can at worst try to do a http://launchpadlibrarian.net/60658417/compiz_1%3A0.9.2.1%2Bglibmainloop3-0ubuntu2_1%3A0.9.2.1%2Bglibmainloop3-0ubuntu3.diff.gz === x4 is now known as Guest39014 [15:57] ^ accepting gtk+3.0, it's for -proposed === Guest39014 is now known as x4 [16:01] everything else in unapproved is seeded somewhere [16:08] ^ is used by Edubuntu (AFAIK we're the only one shipping it), this upload contains a fix to a bug preventing arkose from working at all [16:09] skaet, cjwatson: I wonder if I can go to Taekwondo now, or rather stay online for the evening? [16:10] pitti: go on, I'll be around off and on for a bit [16:11] ack; good night then! [16:11] pitti, go to Taekwondo. we're in wait mode now. If you could check in when you get back [16:11] would be appreciated [16:11] skaet: yep, can do [16:11] thanks pitti [16:19] ^- that's for -proposed since ubiquity wants to be in sync across all architectures; please review/accept [16:24] stgraber: accepted [16:27] cjwatson: thanks [16:29] cjwatson, looks like straightforward extra checking. accepted. [16:30] thanks [16:37] cjwatson, skaet, pitti: just an update about the bug; we're going with another workaround for now, since none of our fixes has proved to be 100% reliable so far [16:37] cjwatson, skaet, pitti: didrocks is building a package with a patch he used some time ago, to force a --reset on the plugin list [16:37] the difference is that I'll only do it on the plugin list [16:37] on the whole configuration [16:37] (and only once) [16:37] ie, the list of plugins is fixed-set, but the settings are preserved [16:38] but still, the real issue has to be worked on [16:38] eta? (sil2100 volunteered to do a sanity check on the packages) [16:39] he has a broken setting? [16:45] didrocks: no, just verify that there is no obvious regression, for whatever reason (since this patch is known to have worked before) [16:46] so I guess you want to punt this into -proposed first? [16:46] cjwatson: yeah, seems better [16:47] cjwatson: I'm buiding it, it's a silly patch, but at least, it should unblock the situation for now [16:48] cjwatson: while we are at it, there is an unity patch which can make beta2 (bad interaction with software-center which can cause in a crash) [16:55] didrocks: will need to see the patch, but ok ... [16:56] jibel: the latest upgrade failures of lucid-main are a strange regression that I can't reproduce locally by installing the lucid version of puppetmaster and then upgrading to the precise version. Do you have any more info about what's happening here? [16:58] are we expecting the fix for bug #916291 in before beta-2? [16:58] Launchpad bug 916291 in libreoffice "failed to upgrade from Oneiric to Precise: ERROR: Cannot determine language! - exit status 134" [Critical,In progress] https://launchpad.net/bugs/916291 [16:59] well, in progress as of 4h ago; but not sure if that will land on CDs [17:01] the build is 31 hours on armhf [17:01] and pretty long even on x86 [17:02] * slangasek nods [17:02] (12-13 hours) [17:04] * skaet *blinks* at 31 hours on harmmhf... [17:05] welcome to libreoffice :-/ [17:06] * cjwatson -> dinner [17:12] jibel: btw, I can't quite figure out why /etc/init/console-setup.conf is being shown as an obsolete conffile of console-setup in the lucid->precise upgrade, given that keyboard-configuration replaces this conffile and is shown as being unpacked... could we perhaps get a copy of /var/lib/dpkg/status from one of these systems post-upgrade? [17:12] wow, what is wrong with the javascript in jenkins? It pegs my CPU [17:14] cjwatson: sorry for the time taken for the workaround, but compiz is making bad implication about what it should copy/erase under your feet [17:15] making a final build to ensure everything is fine [17:23] Riddell, pad doesn't seem to have kubuntu active on it for rebuilds, can you add? [17:25] doko: You were discussing a rebuild test last week, did you still plan to do that? [17:32] Daviey, when the fix lands from didrocks, will the changes be there for server images to fit, or will we still need to wait on that? [17:32] s/fix/workaround/ [17:35] skaet: thanks for hilighting it's a workaround, because it really is :) [17:36] (uploaded to -proposed, tested with a lot of reboot here) [17:36] but as I never got a hang… at least, for everyone it fixed with a --reset, it should work the same [17:36] pgraner, jibel ^ who will be around to test the image once its built later today? [17:37] skaet: no, not yet. Unity isn't on the server cd btw :) [17:37] skaet, myself & hggdh [17:37] Daviey, it was more, want to kick them all off at the same time. Assumed you want to pick up the ubiquity bug [17:37] or rather bug fix. :) [17:38] pgraner, thanks. [17:38] skaet, I'm here as long as it takes and I'm making hggdh stay too cuz he loves this stuff :) [17:39] skaet: I am a mere paw in this game, I do what my manager volunteers me to [17:39] pgraner, glad of the company. ;) [17:41] hggdh, glad of your company too. :) [17:42] :-) [17:42] cjwatson: ^ [17:43] didrocks, cjwatson's at dinner, looking [17:44] skaet: I targeted -proposed [17:45] I'll look too. [17:45] thanks infinity, didrocks [17:47] didrocks: ... [17:47] didrocks: You weren't kidding about this being a workaround. :P [17:47] hello! the new ubuntuone-control-panel 2.99.91-0ubuntu2 has a minor fix where I added a missing dependency for a binary package [17:48] infinity: I'm always serious on my speech :) [17:49] * infinity giggles at current_profile_gconfvalue.set_string('fooo') [17:50] infinity: yeah, compiz is aweful with the gconf backend [17:50] infinity: basically, copying you 2 trees [17:50] so if you reset some keys [17:50] you need to force again to copy the keys [17:50] this is triggered by the "profile" change [17:50] Brilliant. [17:50] Well, it appears to do what it's meant to do, +1 from me. [17:51] Were "+1" is "+0.5" with an added "ew". :P [17:51]