/srv/irclogs.ubuntu.com/2011/10/06/#ubuntu-release.txt

cjwatsonhuh, you're right, I have a very very distinct memory of discussions about that in Seville though00:00
cjwatsonmaybe it was something related but subtly different00:00
cjwatsonoh, perhaps udev-lvm-mdadm-evms-gutsy00:01
cjwatsonheh, yes, https://blueprints.launchpad.net/ubuntu/+spec/udev-lvm-mdadm-evms-gutsy is definitely worth looking at in conjunction00:02
slangasek# In Ubuntu uploads should go to precise00:17
slangasekyes, they should all go to precise00:17
* slangasek stabs the language center of his brain harder00:18
infinityslangasek: Yeah, I don't think I'll ever get used to it.00:19
infinityMaybe we can get a perky == precise hack into launchpad, and upload to the correct suite. :)00:20
cjwatsonit took me three months to stop typing interpid.00:29
infinityI remember a lot of rejected "gusty" uploads.00:34
cjwatsonoh, yeah, that too00:35
slangasekheh00:35
slangasekdch -r, dudes :P00:35
cjwatsonI wasn't always in the habit of editing /usr/bin/dch locally before I got round to upgrading to the next release00:38
cjwatson(I am now)00:38
slangasekah :)00:38
cjwatsonskaet: is this a true candidate tomorrow - should we ensuring that base-files and the CD volume labels are final?01:30
cjwatsonor just a smoke test?01:30
cjwatson*should we be01:30
cjwatsonReleaseProcess doesn't indicate that we should be doing so until Monday01:31
cjwatsonso I guess I'll just go to bed, somebody else can deal with that if it's needed :)01:31
cjwatsondebian-installer and ubiquity uploaded, hopefully at least conceivably final01:31
stgrabercjwatson: good night!01:36
ScottKinfinity and Daviey: Thanks for looking into memcached.03:23
* infinity puzzles over both the weird version on that postfix upload and the really quick accept...03:43
infinityWho accepted that?03:43
* infinity wonders if lamont accepted his own upload...03:44
lamontinfinity: I did not03:45
lamontOTOH, I haven't exactly finished updating the debian chroot to build the upload for debian03:45
infinitylamont: It would seem that no one else is speaking up either. :P03:45
micahglamont isn't an AA AFAIK03:46
lamontand that's a perfectly valid "yeah, just import over me" version number03:46
lamontmicahg: I have a duck03:46
infinitymicahg: lamont is a duckie, he has full LP access.03:46
lamontOTOH, AA stuff scares me enough to just avoid it entirely03:46
micahglamont: I know, but I don't see you as the type to abuse it :)03:46
infinitylamont: While you're in a package maintaining mood, RT#48330? :)03:46
stgraberskaet: just so you know, I just found what looks like a python-gevent bug breaking weblive for Oneiric systems (possibly limited to these with IPv6 connectivity). Only Edubuntu ships with python-x2go/python-gevent by default but we'll likely want that working in the release (as it's advertised in the install slideshow).03:47
infinitymicahg: Yes, lamont's never abused access to anything in his life. ;)03:47
lamontinfinity: give it some relationship to 48181?  I'd be inclined to shrug if you went in and said 48181 depended on 4833003:48
lamontthat argument holds at least some water03:48
infinity48181?03:48
* infinity looks.03:48
lamontI have one other zomfg ticket ahead of 48181, and I'm planning to have a weekend this week03:49
infinityI'm not sure I can argue that. :P03:49
infinityBut it's a 2-line patch.03:49
lamontinfinity: oh.  orthogonal activities?03:49
infinitylamont: Yeah.  48181 is an OEM one-off project, not proper armhf in Soyuz.03:50
lamontok03:50
infinitylamont: 48330 is Soyuz.03:50
infinity(And needs doing between now and P, but I'd prefer to have all our ducks i na row well ahead of P, so I'm not panicking on opening day)03:50
lamontinfinity: I've got pre-O craziness that wins over it.03:50
ScottKinfinity: I accepted it.03:51
lamontOTOH, if you happened to have a source package that was based on -cat, that becomes much more of a slamdunk03:51
infinityScottK: Mmkay.  Just seemed a bit quick.03:51
infinitylamont: I can do that.03:51
lamontinfinity: it got built and tested in a ppa03:51
lamontpostfix that is03:51
ScottKIt was because I'd reviewed it before it was uploaded.03:51
infinitylamont: I realised the current -cat one was Colin's, not yours. :P03:51
lamontwith ScottK poking me about it starting a couple days ago03:52
* infinity wonders if he can still upload to archive.admin ...03:52
lamontpretty sure we removed that key03:52
infinityOh, no, it was an scp queue, wasn't it?03:52
lamontyeah03:52
infinityFoiled.03:52
infinitylamont: I'll toss a fixed package on chinstrap.03:52
lamontcool.  ref it in the ticket, and etc, etc03:53
lamontfortunately, dpkg on the buildds is run inside the chroot, so we don't need a hardy version03:54
lamontand with that, way past my bedtime03:54
infinitylamont: Yeah, I know, I fixed that misfeature. ;)03:54
infinitylamont: Just need this for soyuz.03:54
lamontyour homedir on osageorange is another option for where to drop it03:54
infinityWhat host is that?03:55
infinityNew amd64 porter, I'm guessing?03:55
lamontporter box, should have a lucid-cat chroot on it03:55
lamontit's the new ronne03:55
infinityYeah, I don't keep up.  Never use porter boxes.03:55
infinityI always have to look them up when I tell others to. :P03:55
lamontheh03:55
micahgthere are aliases for them now03:56
infinityOh?03:56
micahginfinity: porter-<arch>03:57
* infinity just tried amd64.canonical.com amd64-porter.canonical.com and amd64.porter and gives up hope that it's intuitive. :)03:57
lamontMachineOverview03:57
infinityOh, sure.03:57
infinitylamont: Looks like porter-armhf might need some DNS love (scheat)03:58
infinitySure, it has no armhf chroots yet, but whatever. :P03:58
lamontbah03:58
lamontthrow that at RT, it seems trivial to me03:58
lamontas in it'll just go through the vg queue and be done in a couple days03:58
* infinity nods.03:59
lamontlogging in would be work03:59
lamontand my day ended quite a while ago04:00
infinitySo did mine. :P04:00
lamontheh04:00
infinitylamont: Uploaded to osageorange, changes is signed (on the off chance that the archive accepts my key?), and threre's a debdiff sitting there too.04:05
stgraberskaet: actually just spent a bit of time debugging that python-gevent thing now. It's a weird bug but actually very far from being critical (socket.getaddrinfo hanging for > 30s when one of your DNS servers doesn't answer)04:07
ScottKSounds easy enough to fix though.04:08
stgraberpretty weird bug though. I have 3 DNS servers, two of them work fine, including the first one. getaddrinfo always returns within a second, except from python-x2go which uses python-gevent04:09
infinitylamont: And ticket updated to reflect that.04:09
stgrabertrying to reproduce with just socket or gevent.socket won't get me the bug. Doing it from x2go, gets me the bug every time I try it04:09
ScottKWhat does it use for DNS?04:09
stgraberScottK: http://paste.ubuntu.com/703175/04:10
ScottKCongratulations, BTW.04:10
stgraberweblive-appserv02.nx.stgraber.org, 6622, socket.AF_UNSPEC, socket.SOCK_STREAM are the parameters to socket.getaddrinfo() (added some debug in paramiko)04:11
stgraberthanks :)04:11
pittiGood morning04:12
pitticjwatson: langpacks> I'll just remove the broken ones for now; need to investigate why the heck they are built without a corresponding -base04:12
infinitypitti: Mornin'.04:12
pittiskaet: langpacks will be uploaded tomorrow; they weren't meant to be on the RC (but current images have Tuesday's langpacks, so are reasonably current for testing)04:13
infinitypitti: I'm waiting on a final apt upload from mvo for RCish images anyway.04:16
infinitypitti: Well, for ARM, that is.  You can spin others before, if you like. ;)04:16
pittiseems we still have the daily cron jobs even04:17
pittihttps://wiki.ubuntu.com/OneiricOcelot/ReleaseTaskSignup doesn't have someone responsible for RC2, but as we don't release it, I guess the only thing that we need doing is spinning images and posting them to the tracker for QA?04:17
infinityYeah, we're not releasing.  So, whatever.04:18
infinityAlso heard rumours that we won't start calling things RC until after the weekend.04:18
ScottKstgraber: For a test you might switch the failing call in dns.py to use python-dns or python-dnspython.  That would at least give you an idea if if the issue was in the code below that call.04:19
pittioh, so we could still accept fixes today?04:19
infinityYeah.04:19
ScottKI would.04:19
ScottKIn fact I did a few minutes ago.04:19
pittie. g. I have https://code.launchpad.net/~jbicha/ubuntu/oneiric/jockey/update-help-link/+merge/77782, which is a trivial and obvious fix for broken help button04:19
infinityWell, we can accept fixes until release day, but we pretty obviously don't want to unless they're critical. :P04:19
infinitypitti: Do it.04:19
pitti(due to the ubuntu-docs reorg)04:19
pittiwell, not exactly critical, but very low-risk (arch: all package, and all that)04:20
ScottKSounds like the kind of final polish we should have.04:20
infinitypitti: I don't think the team as a whole is committed to being in RC mode until the sprint, which starts Monday morning.04:20
pittiScottK: yeah, I agree04:20
pittibut RC on Monday sounds fine to me; we'd still want some urgent fixes in, if we can get them04:20
infinitypitti: So, I think it's sane to get base-files and such in over the weekend, turn off dailies Monday morning, and go from there.04:20
pittisounds fine04:21
pittiso a REAL release candidate for the first time? :-)04:21
* infinity crosses his fingers.04:21
pittiwe should still get the current dailies some testing, though, to spot some OMG installer problems04:22
infinityI've kind of come to the conclusion that I just have to live with any ARM bugs we find from here on.04:22
infinityTHough I'm really, really tempted to hack up oem-config to stop/start (ana)cron before/after the install.04:22
infinityThe regression potential for messing that up isn't worth it, though.04:22
ScottKpitti: If you have a free moment today, I think KDE 4.6.5 is sufficiently aged to move to natty-updates.04:23
pittiScottK: yep, will do04:23
ScottKThanks.04:23
pittiI'll have a look today why evolution-exchange is uninstallable04:23
pittislangasek, infinity, ogra_: do you know about all the linaro kernels on http://people.canonical.com/~ubuntu-archive/component-mismatches.txt ?04:24
pittithey are also shown as being uninstallable on http://people.canonical.com/~ubuntu-archive/testing/oneiric_probs.html (some of them)04:25
pittishould they be in main and are missing some seeding/metapackages, or demoted?04:25
infinitypitti: vexpress and omap4 are used by d-i.. That may need some seeding, if things aren't smart enough to sort that out.04:42
infinitypitti: linaro-mx51 can go to universe, as can st1-5, unless we have a support commitment there I'm not aware of (we certainly don't use them for images)04:43
infinitypitti: linaro-omap as well.04:43
infinitypitti: Might need Colin's input on vexpress.  I can chase down the rest.04:45
pittihm, indicator-datetime went to oneiric-proposed04:45
pitticould just as well have gone to final, I guess?04:45
infinityOh, I didn't even notice the pocket on that one...04:46
pittihttp://launchpadlibrarian.net/82049869/indicator-datetime_0.3.0-0ubuntu1_0.3.0-0ubuntu2.diff.gz looks safe enough to me, anyway, and it affects the live system04:48
pittiinfinity: I can remove the proposed package and reupload to oneiric?04:48
infinitypitti: yeah, please do, I didn't notice the suite when I accepted it.04:48
pittiroger04:48
micahgpitti: you'd have to bump the version04:48
pittimicahg: yeah, I won't retrofit the changelog04:49
infinitypitti: don't accept that u-boot to proposed either, I'm going to grill jcrigby about why he didn't want that in release.04:50
pittiinfinity: *nod*04:51
infinitypitti: Actually, better idea, maybe I'll reject it from -proposed, so I can talk to him about it without someone else accepting it. :P04:51
infinitypitti: Oh, I suppose u-boot-linaro-mx53loco can go to universe, we're building mx53 from universe anyway.04:53
infinity(Though it comes from main sources, so I could just as easily seed it)04:53
infinityI've always found the source-in-main-binary-in-universe thing kinda messed up. :/04:53
* infinity fixes some kernel seeds.04:56
pittiok, let's see what's left after your seed changes04:56
infinitypitti: Updated, if you want to manually trigger a mismatches check.05:00
pittiinfinity: I'll just wait for cron, before I break anything05:01
infinitypitti: Wuss. ;)05:01
pittiinfinity: so you seeded mx53 only? mx51, st1-5, and omap should still go to universe?05:01
infinitypitti: mx53 is in universe, and should stay there (the u-boot can go).05:02
infinitypitti: I fixed up seeds for omap, vexpress, and omap4 for main, and mx51 and st1-5 can go.05:02
pittiah, good05:02
pittistill wondering why their sources are in main05:02
infinityWho knows.05:03
stgraberScottK: http://paste.ubuntu.com/703195/05:03
pittidemoting, of course I just missed the publisher05:03
infinityI'm wondering why linaro-omap is in main when the images use -omap, but I need to talk to Colin about that, since he builds d-i for both.05:03
stgraberScottK: at least I'm pretty sure it's a gevent weirdness now :)05:03
ScottKYeah.05:04
infinitypitti: You can remove libreoffice-gcj too, it's NBS.05:18
pittiweird, why it isn't on http://people.canonical.com/~ubuntu-archive/nbs.html ..05:19
infinityProbably because it's still in the .dsc and NBS isn't smart.05:19
infinityIt's conditionally built.05:19
pittiaah05:19
infinityAnd not on any of our architectures.05:19
pittipresumably for backports05:19
infinityNo, for arches that use gcj instead of openjdk.05:19
infinityWe just don't ship any of those. :P05:19
pitticheers, doing05:20
* infinity finds http://people.canonical.com/~ubuntu-archive/testing/oneiric_outdate.txt helpful for stuff like that.05:20
micahgUbuntu freebsd coming any time soon? :D05:20
infinityWhen one package from a source is out-of-date, you know something's up. ;)05:20
nigelbmicahg: Tomorrow's headlines - "Ubuntu developer membership board member wonders when Ubuntu freebsd is coming out"05:22
micahgnigelb: context FTW :)05:23
infinitypitti: ibmasm-utils and msr-tools can be removed on armel and powerpc (should have been done in natty, no one noticed)05:23
nigelbmicahg: Heh. :)05:23
infinitypitti: All those pings combined, and two buildds catching up, and armel will be completely up-to-date again.  Yay.05:24
pitti*flush*05:25
infinityScottK: Aww, crap.  Weren't we meant to do something about that kdesdk/ppc build failure?05:27
infinityScottK: I reproduced it but didn't have the time to debug. :/05:27
ScottKYes.  You were going to fix it ...05:27
infinityI was going to fix it?05:28
infinityReally?05:28
ScottKYes.05:28
infinityLies and subterfuge.05:28
ScottKI'm sure you volunteered.05:28
micahginfinity: I'm in the same boat as you :)05:28
ScottKI know it's way too complicated for me.05:28
infinityUgh.05:28
infinityCan it please not be CMake?05:28
micahginfinity: a generated file doesn't seem to work on powerpc05:29
infinitymicahg: And by 'work' you mean 'exist'.05:29
micahgright05:29
infinityAnd yeah, I got that far before I got busy.05:30
* infinity updates his oneiric chroot to have another poke with a sharper stick.05:30
ScottKThe python-defaults upload that is about to appear only has minor changes from what we have now, but it lines us up with what's supposed to push the python2.7 transition into Debian Testing today, so I think it'd be good so have that for release.05:32
ScottKThat one.05:32
infinityI'll look at it when it gets diffy.05:33
ScottKThanks.05:34
ScottKKubuntu alternates all fit again.05:35
infinitypitti can fix that.05:35
ScottKSomehow they grew 10MB yesterday to I had to strip some lang packs off.05:35
pittiScottK: most likely https://launchpad.net/ubuntu/+source/kubuntu-docs/11.10ubuntu2 ?05:36
ScottKYes.  That would do it.05:36
ScottKBut notice what pocket that's in.05:36
ScottKIt wasn't supposed to be accepted yet.05:36
micahgxubuntu alternates are 10MB larger as well05:36
infinityDid we get a kernel image suddenly bloating or something?05:37
ScottKAnd kubuntu-doc is on both live and alternate, so it wouldn't have affected both.05:38
infinityScottK: It was only your alternates that grew?05:38
ScottKYes.05:38
pittiScottK: eww, missed that; straight to -updates?05:38
infinitySo, something d-i-ish, or something in your ship seed.05:38
infinityAnd something in common with xubuntu.05:39
infinityThis is a fun game.05:39
ScottKYep.05:39
pittiScottK: we also got new delta langpacks on Tuesday, which will shrink again tomorrow when we do a -base refresh05:39
micahgusually the langpacks do this when stuff moves between base and non-base05:39
ScottKFortunately the alternates have language packs to remove.05:39
ScottKMaybe that was it.05:39
pittiScottK: so if you add up the size of all language-pack-XX on the images, that's what will go away on Saturday's images05:39
ScottKEasy enough to put them back if we get more room.05:41
pittiScottK: so, about the kubuntu-docs blunder, sorry about that; should we reupload the previous version, and the current one to -proposed?05:42
ScottKThe biggest reason to wait was fear that the added translations would make it too big.05:42
ScottKSince we aren't over on the live CD, I think we can leave it.05:43
ScottKI was suprised Riddell uploaded it so soon if it was for updates.05:43
infinityScottK: Your CDs shouldn't be building against updates anyway.05:51
infinityScottK: Check your manifests, that package shouldn't be there.05:51
ScottKIt's there.05:52
infinityReally?05:52
ScottKYep.05:52
infinityThat's a bug in our code, then. :P05:52
infinityWell maybe a misfeature.05:52
infinitySince we build against updates for point releases.05:52
ScottKI don't think so.  I think we normally build against updates, it's just usually empty.05:52
infinityAnd I guess maybe we're expecting (incorrectly) that updates is empty on release. ;)05:52
ScottKWe used it last cycle to fix a dvd seed problem by uploading kubuntu-meta to -updates and then just respinning the dvd.05:53
ScottKThat way the CDs weren't out of date at release ...05:53
ScottKNice trick, eh?05:54
ScottKI think pitti thought of it.05:54
pittiI still remember that one05:54
pittiI'm not surprised that -updates lands on images, it's just strange to have it05:55
pittiin all but that one case we have used zero-day SRUs for fixing major upgrade bugs05:55
pittiwhich don't affect images05:55
cjwatsonYeah, we've used that trick a couple of times06:01
pittihey cjwatson  -- early for you :)06:02
infinityUp to and including making sure openssl-blacklist DIDN'T land on CDs because it was too effin' huge.06:02
infinityThat was entertaining.06:02
infinitycjwatson: Want to check the lightdm in the queue, since it relates to your pet bug?06:02
cjwatsonpitti: Thursdays are odd for me, toddler sign class06:03
cjwatson(and believe me I'm not happy to be awake)06:03
infinityBeer.06:04
infinitySome may argue it's too early to drink, but in your world, it's probably more late than early.06:05
cjwatsonlightdm> still doesn't look like an entirely proper fix to me (overrides PAM), but it looks OK06:08
cjwatsonand somebody else seems to have beaten me to it06:08
cjwatsonI hadn't tested the previous one yet ;-)06:08
ScottKI think it's officially late here.  Good night.06:09
infinityNight.06:09
slangasekpitti: I know nothing about current linaro kernel packages, sorry06:14
infinityslangasek: I sorted it.06:14
infinityIsh.06:14
infinitySomeone verify that I can spell "oneiric" correctly and accept jasper?06:19
pittione-eye-rick looks fine; accepted06:21
infinityThat sounds vaguely dirty.06:24
infinityRight, I remember the kdesdk failure.  structviewpreferences.h doesn't exist, and ISN'T REFERENCED FROM THE BUILD SYSTEM AT ALL.06:25
infinity(I'm not bitter)06:26
infinityFriggin CMake.06:26
micahginfinity: it's supposed to be generated by a .kcfg file IIRC06:26
infinityYeah, I have no clue how any of that works. :P06:27
micahgme neither :P06:27
=== doko_ is now known as doko
dokodo we already accept uploads for -proposed?06:54
infinitypitti: Oh, the other issue with those mismatches is linux-meta-linaro being crufty.  I need to talk to jcrigby about that, since not all the linaro sources are in sync. :/06:59
infinitycjwatson: And on the topic of ARM kernels, is there a reason for the linaro-omap d-i build alongside the -omap one?07:01
infinitycjwatson: (That you know of?)07:01
cjwatsoninfinity: I just do what I'm told.  But both of them are in d-i right now, so let's keep them both for oneiric ...07:02
infinityYeah, I wasn't planning to change it, was just curious if you had a rationale.07:02
cjwatsondoko: -proposed can always be uploaded to from the moment a series opens07:02
cjwatsondoko: whether anyone will process it ... :-)07:02
cjwatson  * Add linaro-omap netboot target to armel images, copied from versatile;07:03
cjwatson    this is useful for all OMAP2+ boards supported in this kernel.07:03
cjwatsonwas for linaro-omap - that was lool07:03
cjwatsonI don't really want to know, I just let y'all shuffle kernels around07:03
infinitycjwatson: Heh.07:05
jbichawill there be an actual milestone RC like the Betas or is RC just test builds for final?07:06
infinityjbicha: The latter.07:07
jbichainfinity: thanks, that's how I read the schedule but just wanted to verify07:08
cjwatsonslangasek: do we want to ditch stderr from 'modprobe -q vesafb' in your recent initramfs-tools change?  I've noticed that my live CD boots in kvm have started showing "FATAL: Error inserting vesafb (/lib/modules/3.0.0-12-generic/initrd/vesafb.ko): No such device" on the console, which seems untidy and may alarm people07:10
slangasekcjwatson: mmm yes - sorry for not catching that07:13
loolinfinity: we can chat about OMAP flavors if you like07:30
loolinfinity: There was also a linaro-vexpress build which got disabled due to some missing kernel configs a while ago (that actually just got fixed); both of the linaro-* builds are suitable for running with qemu-linaro or on real hardware07:31
loolthe linaro-omap one targets OMAP3 and OMAP407:31
loolI think we could do without the OMAP build entirely, but that's not really Linaro's decision to make07:31
infinitylool: We'll chat about flavours after release. :)07:32
infinitylool: Not inclined to do anything about it right now, we'll go with what we have.07:32
pittiso seems some linaro kernels are still missing something: http://people.canonical.com/~ubuntu-archive/component-mismatches.txt07:38
infinitypitti: meta issues.  Scroll up and check nick hilights.07:38
infinitypitti: I'll sort it with jcrigby tomorrow.07:39
pittiok, thanks07:39
pittilibgdata is FTBFS (probably link ordering), looking07:51
infinityslangasek: \o/07:53
pitti^ trivial FTBFS fix, review appeciated08:07
jbichapitti: I noticed the FTBFS because I was going to make libgdata-dev depend on its gir08:10
infinityjbicha: Would you still like to make that change?08:12
infinityjbicha: You can grab pitti's source from the queue and then I can reject it. ;)08:12
pittiI can reject the current upload08:12
pittiinfinity: all in bzr08:12
pittijbicha: ^08:12
infinitypitti: Crazy talk.  You kids and your fancy bizedares.08:12
pitti^ simple installability fix, review appreciated08:14
pittijbicha: libgdata upload rejected, and uncommitted the release tag in bzr to pretend it never happened :)08:16
* infinity decides to try to get some sleep tonight.08:17
infinityToodles, everyone.08:17
pittisleep well!08:17
pittijbicha: doing the dependency change now08:18
pitti... and reuploaded08:19
jbichapitti: thank you08:19
* ogra_ wonders why omap4 images suddenly try to install oem-config-kde08:21
ogra_(and fail badly)08:21
ogra_was there any seed change ? we never had that package installed08:22
ogra_hrm, i should probably learn to read before talking, ignore me08:27
ogra_pitti, can we hold back on arm images until after the arm meeting today, i have no info about the banshee breakage from NCommander yet and dont know iff we need a seed change (to rhythmbox) or not08:35
ogra_(which indeed in turn will require a meta upload)08:35
infinityogra_: We're not spinning RC until the end of the weekend.08:35
infinityogra_: It's just dailies as usual for now.08:35
ogra_oh ?08:35
ogra_why is that ?08:36
infinityJust seemed to be the general concensus around here.08:36
infinityAnd the release sprint starts Monday morning, so that seems like a sane time to turn off the cronjobs and roll up our sleeves.08:36
ogra_k, well, kate told me she wanted images during the day ... that was my last update08:37
pittiwell, we still get dailies08:37
infinityogra_: omap4 images installing oem-config-kde?  where?08:37
pittijibel: is the auto-tester for dailies running?08:37
ogra_infinity, in the kubuntu build that failed08:37
pittii. e. do we get notified if something really breaks?08:38
infinityogra_: Oh, well that sort of makes sense in kubuntu.08:38
ogra_infinity, i hadnt finished my first coffee ...08:38
infinityogra_: But yeah, the failure is just the usual ubiquity-out-of-sync issue.08:39
ogra_and evo crashes badly if i scroll down to the bottom of the log so i didnt really regard the subject line while trying to scroll as slow as possible to actually see the end of the log08:39
ogra_one day i need to switch to TB or file a bug for evo about that :P08:39
pittiugh, http://people.canonical.com/~ubuntu-archive/component-mismatches.txt just exploded08:44
pittidid we just get a new nova? (didn't see one), or was there some seed change?08:44
pittiDaviey: ^08:44
jibelpitti, yes it is running. is your intention to really break something today ?08:44
pittijibel: not just today!08:45
* pitti promotes cobbler-enlist08:46
Davieypitti: Hmm.. that will be my fault.08:50
* Daviey fix0rs08:52
pittiDaviey: cheers08:53
Davieypitti: When it refreshes, it should just be tgt and it's children, which fell out of main this cycle - but should be there.09:03
Davieybug 594372 is the old MIR, can you promote it when it's clear what needs nbumping?09:03
ubot4Launchpad bug 594372 in tgt (Ubuntu Maverick) (and 7 other projects) "MIR: tgt (affects: 1)" [Medium,Fix released] https://launchpad.net/bugs/59437209:03
pittiDaviey: can do09:04
Davieythanks.09:04
Davieyi thought c-m's used to generate every 15mins or so, seems to be hourly now :(09:05
pittiDaviey: has always been hourly, as it needs to wait for publisher09:06
nigelb4509:10
pittinigelb: off by three09:10
nigelbpitti: heh, ironically, I was indeed looking for /window 42 :)09:10
pitticjwatson, Daviey: could either of you please review my libgdata and evolution-exchange uploads?09:17
pittiDaviey: I just did the necessary promotions/demotions for nova10:12
pittic-m should look better in ~ 1.5 hours10:12
pittiScottK: any idea what to do with kdesdk's kdesvn dependency? should that get a very late MIR, or dependency dropped? (I remember that we had the same problem in ealier releases)10:35
cjwatsonpitti: accepted libgdata and evolution-exchange10:36
pitticjwatson: cheers10:36
dokopitti, ScottK: that should be gone. kdesdk did build now. somebody insisted to have to debug it on powerpc only11:55
tumbleweedbdrung: distro-info was picked up by lp, and I requested a sync. (someone please ack it)11:56
Davieypitti: thanks12:27
ScottKdoko: Thanks.12:50
Laneyphppgadmin distro-info look ok to me12:58
pittiLaney: accepted13:10
Laneycheers13:11
oravaHi, when 11.10 RC will be available?13:11
stgrabergood morning13:36
evhiya13:46
Daviey14:36 < stgraber> good morning <-- fail. it's the afternoon.13:47
hggdhDaviey: good morning ;-)13:48
skaethiya13:57
Laneyhey13:58
kenvandinehey skaet13:59
skaetpitti, have all the langpacks landed now?14:00
skaetogra_, wat;s the background on the glade-3 armel translations sitting in the new queue?14:02
* skaet scratching her head over them.14:02
* ogra_ has no clue, first time i hear about it 14:02
* skaet figures to see if pitti knows where they've come from then....14:03
cjwatsonthe translations are not the things that are new.14:03
cjwatsonI will review that14:03
skaetthanks cjwatson. :)14:03
ogra_package name changes ?14:03
ogra_8or is that source-new we are talking about)14:03
cjwatsonI will deal with it14:04
ogra_k14:04
cjwatsonnor is it armel-specific btw14:04
Laneybinary new; they added gtk2 variants14:04
ogra_aha14:04
dokowho did accept libx86 and xen? just want to know how it was accepted (web UI or command line tol)14:05
skaetDaviey, nova fix in the queue from Robie,  are you reviewing and accepting it for the candidates?14:06
cjwatsonpitti: your glade-3 3.8.0-0ubuntu2 upload said that glade-gnome is built by the glade source package now, but I don't see that.  Did you have a glade upload that you aborted when didrocks decided to reintroduce glade-gnome to glade-3?14:15
stgraberare we planning for a mass rebuild later today? otherwise I'd like to have a respin of Edubuntu to pick up the new ubiquity for testing.14:25
skaetstgraber, will go kick it off.14:26
stgraberthanks14:26
skaetits started now.14:29
pittiskaet: no, langpack export is starting tonight, will build them tomorrow morning14:34
pitticjwatson: didrocks needed the gtk2 variant back for quickly14:35
pitticjwatson: it's actually not called "glade-gnome" any more, just glade14:35
cjwatsonpitti: so the mentioned glade change never happened?14:35
cjwatsonpitti: didrocks' upload reintroduces a 'glade-gnome' binary package, that's why I'm asking14:36
cjwatsonI wanted to make sure that wouldn't collide with a change to the glade source package14:36
skaetpitti, was wanting to get the candidates created with the langpacks today, so jibel could test them out tomorrow,  any options?14:36
pittiskaet: the export takes about 24 hours..; but when we discussed that a week or two ago it was fine?14:37
didrockscjwatson: the paths are different, it's basically the same than libgladeui-common's one, with a different (glade3) path14:37
skaetpitti, I appear to have misunderstood.  I thought they'd be ready by today, not starting to export today.14:37
cjwatsonsorry, I seem to be being unclear, I don't care about any of this stuff :)14:38
cjwatsonpitti's previous upload implied that glade-gnome was being added as a binary to the glade source package14:38
cjwatsonI want to make sure that didn't happen so that this glade-3 upload in NEW won't collide14:38
cjwatsonI can read the rest of the rationale and such for myself14:38
pittiglade-gnome is not really meant to exist any more14:38
pittiin a GNOME 3 world14:38
cjwatson*sigh* is anyone actually going to answer my question? )14:39
didrockscjwatson: there is no overwrite, if that's the question, it's gnome-common for the gtk2 glade flavor and libgladeui-common for the gtk3 glade14:39
pittias all the widgets etc. are in GTK now14:39
cjwatson:)14:39
cjwatson  * debian/control: Drop glade and glade-gnome, they are built by the "glade"14:39
pitticjwatson: so, glade-gnome is not meant to be built by the glade source14:39
cjwatson    source package now.14:39
cjwatsondid this happen or did it not?14:39
cjwatsonthis should be yes or no14:39
pitti"yes" for the  glade binary, "no" for glade-gnome14:39
pittiand glade-gnome isn't meant to be built by glade14:40
cjwatsonOK14:40
pittiso everything should be fine14:40
cjwatsonthanks, that's all I wanted to know14:40
pittibut I don't know why didrocks introduced glade-gnome as well14:40
pittididrocks: ^ are these the extra gnomeish widgets on top of glade-gtk2?14:40
didrockspitti: right, it seems that some widgets in glade only show if we get this extra ones14:40
didrocks(in glade, like, in glade gtk2)14:41
pittididrocks: yes, those are from the old "extra" gnome libs, all of which are obsolete in 314:41
pitticjwatson: so, as long as there are no file collisions, it shoudl be fine; want me to check?14:41
didrocks(there is not normally, I ensured that using the old glade3/ path instead of glade/)14:42
cjwatsonpitti: it looks fine, but I'm sure a second pair of eyes wouldn't hurt.  The files are in cocoplum:/tmp/cjwatson/14:43
dokopitti, cjwatson: the kdesvn component mismatch isn't a real one. kdesdk depends on kdesdk-kio-plugins (>= 4:4.7.1-0ubuntu2) | kdesvn-kio-plugins. the former is in main14:50
pitticjwatson: install well alongside glade binaries, debs look ok to me, and both the old and the new glade work14:53
cjwatsonok, and it can go in universe, can't it?14:54
pittiyes, as quickly is universe, too14:54
cjwatsonok, accepted then, thanks14:56
pittithanks14:56
mvoif someone like cjwatson could review the apt upload, that would be great, it got some good review from mdeslaur and infinity already, but the more eyes the better14:57
pittiI'm afraid I'm mostly useless right now, my head is exploding (got a cold); I'll try to take a nap, back on TB meeting15:03
pittiplease don't hesitate to call my mobile if something bad happens15:03
skaetok pitti.   hope you feel better soon.15:06
evRT 48349 is for a signed wubi15:29
* skaet thanks whoever just reviewed glib2.0, which appears to have the fix for bug 80494615:35
ubot4Launchpad bug 804946 in glib2.0 (Ubuntu Oneiric) (and 2 other projects) "gnome-settings-daemon crashed with SIGSEGV in g_variant_unref() (affects: 227) (dups: 83) (heat: 1020)" [Critical,Fix released] https://launchpad.net/bugs/80494615:35
infinityThat was me.15:36
skaet:)15:40
* Laney wonders if 12.10 wouldn't have been a better choice for the LTS given that Debian will be frozen from June15:51
cjwatsonhttp://article.gmane.org/gmane.comp.time.tz/4133 erk16:04
micahgskaet: we're going to need a firefox upload to fix upgrades from natty to oneiric with the same firefox version, I assume we want this fixed on the live media as well?16:05
micahgskaet: problem we're fixing is missing search engines again16:06
skaetmicahg, ok,  what's the ETA?16:06
* skaet wondering if we need this in today's images, or if its going to need to go into Monday's final, or an SRU.16:07
micahgskaet: well, I can do this one of 2 ways, I can fix the current issue, but it'll come back to bite us again when we upgrade to 8, or I can try to fix it right so we hopefully aren't bitten by it again16:07
micahgthe first, I can upload a fix in a few minutes, the other will be several hours16:08
skaetmicahg,  please fix the current issue,  and upload that.   That will give us the backup, and get the builds started.   If you have a better fix,  we can decide tomorrow to get it ready and included for Monday's builds.16:09
micahgskaet: ok16:09
* skaet figures micahg will do a better proper long term fix without her asking for the next few hours... is it ready yet?;)16:10
skaetcjwatson, urk indeed.16:12
micahgskaet: so, Chris Coulson committed a fix to bzr, it should be a permanent fix16:13
micahgI'll upload it16:14
skaetmicahg, thanks.16:14
micahgskaet: do you want me to do a test build first or just upload? (only change was in the postinst)16:19
skaetmicahg,  test build first please,  just in case.    We have time,  waiting for WUBI upload.16:20
micahgskaet: ok, should be about a half hour then16:20
skaetmicahg, thanks. :016:21
skaet:)16:21
micahgskaet: so, apparently, the upgrade issue with Firefox was discussed with pitti yesterday and they decided to SRU, I'm not sure if the issue of people upgrading off of live media was brought up16:57
skaetmicahg, yeah, so it appears.16:58
jdstrandmicahg: can you briefly summarize the issue?17:00
jdstrand(for me-- sorry that I am not up on backscroll, etc)17:00
micahgjdstrand: upgraders from natty w/the same version will lose their search engines Bug #86931117:01
ubot4Launchpad bug 869311 in firefox (Ubuntu Oneiric) (and 1 other project) "searchplugins installation damaged after natty->oneiric upgrade (affects: 1) (heat: 6)" [High,In progress] https://launchpad.net/bugs/86931117:01
jdstrandso, I go from 0ubuntu0.11.04.1 to 0ubuntu1 and lose my search engine?17:01
micahgjdstrand: right17:02
jdstrandmicahg: 7.0.1+build1+nobinonly-0ubuntu2 will fix this?17:02
jdstrand(whether it is SRU or not)17:02
micahgjdstrand: yes17:02
jdstrandmicahg: what is on the iso right now?17:03
micahg7.0.1+build1+nobinonly-0ubuntu1 should be17:03
jdstrandmicahg: ok, so this should not affect new installs, correct?17:04
micahgjdstrand: right, only upgrades (which I thought the live media supports as well)17:04
jdstrandmicahg: so your concern is natty users using the CD to upgrade17:04
micahgbut I guess if people are upgrading off live media, they'll either be out of date on natty, or will just run upgrades on oneiric afterwards17:05
micahgso I guess it can go to SRU17:05
micahgjdstrand: yes17:05
jdstrandwell, we can't say the former is true, we can say that latter is17:05
jdstrandmicahg: can this simply be a 0-day SRU?17:05
micahgjdstrand: yep17:05
jdstrandIMHO, that is the best course of action because they will immediately get the updates most of the time. it seems that people upgrading off of oneiric install media would also be getting network upgrades as well17:08
micahgjdstrand: right and if they don't they probably didn't have the previous upgrades either (so won't experience the issue)17:08
jdstrandcool17:09
evabout to step out for dinner17:09
evstill waiting for a signed wubi from IS17:09
evwill check back when I get home tonight17:10
jdstrandskaet: I think that perhaps this should be a release note in the Technical Overview: "Ubuntu 11.04 users who are upgrading via Ubuntu 11.10 install media may lose access to Firefox search engines until performing a standard upgrade (LP: #869311)."17:10
jdstrand(or similar)17:10
skaetev, ok,  WUBI's on the critical path for building the images.17:10
infinityIs there a sane way to determine why I can see private bugs?17:11
infinityhttps://bugs.launchpad.net/ubuntu/+source/geoclue <-- I see 20+ private bugs there, and I'm curious if people who actually need to see them can.17:11
micahginfinity: go to a bug and click on edit bug mail, it should tell you why you can see it17:12
skaetjdstrand, ack.   will add it then.17:12
micahgskaet: do you want a release notes task on the bug?17:12
skaetmicahg, yes please.17:12
micahgskaet: and should I just leave the upload for chris next week then?17:12
evskaet: indeed, text me if I need to run back to the office17:12
evskaet: my mobile is in the directory17:13
Laneyinfinity: by being in a team which is subscribed to the bug (usually crash bug triagers)17:13
Laneydon't know if that is sane17:13
infinityLaney: Ahh, so basically, any ubuntu dev can see those.  Check.17:13
jdstrandmicahg: thanks for looking into this and bringing it up :)17:13
infinityLaney: It may or may not be sane, but in this case, I'd like people to actually be trying to fix that bug. :P17:13
infinityLaney: 20+ dupes of the same bug sounds less than ideal.17:13
jdstrandmicahg: is the ubuntu2 upload something that chris can handle next week?17:13
micahginfinity: bug control is allowed to see retraced bugs, and ubuntu-dev is a member17:14
micahgjdstrand: yes17:14
micahgjdstrand: as long as the 7 day SRU period is waved17:14
skaetev,  thanks will do.17:14
jdstrandmicahg: cool. feel free to commit any work you've done and just ask him to review/upload17:14
jdstrandmicahg: yeah-- that'll need to be coordinated with pitti (which is convenient since he is on both the SRU and release teams :)17:15
skaetstgraber, edubuntu 20111006.1 is available17:31
skaetcrontab has been disabled17:34
stgraberskaet: rsyncing17:35
skaetheya,  who let the ubuntu-meta package through,  and what was it fixing?17:51
cjwatsonyou can answer the latter question using https://launchpad.net/ubuntu/+source/ubuntu-meta/+changelog17:52
cjwatsonI wasn't the one who accepted it but I would have done if I'd seen it17:53
skaetthanks cjwatson17:53
cjwatsonthe seed commit message is "remove banshee from armel and replace it with rhythmbox, banshee is unusable on arm"17:53
skaetyup,  am looking at it now.17:54
pittimicahg, skaet: as chris is on holiday, and the firefox issue is upgrade-only, a 0-day SRU should do, I think17:57
pittichris has a fix, but needs testing, etc.17:57
ogra_skaet, banshee is unfixable in time, the meta upload switches armel back to rhythmbox18:17
ogra_sorry, i should have announced it here, but was in a hurry to get catfood before the shop closes18:18
skaetogra_,  ack.  infinity, ^^18:18
* skaet stepping out to lunch, biab18:19
evskaet: Got your message. We've just sat down to eat. I'll check and move the wubi binary into the right place once we're done.18:19
ogasawarapitti: I uploaded a new linux-meta to resolve the missing lbm-headers and -extra meta packages, could you accept it in the queue?18:19
skaetev:  thanks!18:19
pittiogasawara: splendid, thanks!18:19
stgraberskaet: I'll be uploading a new edubuntu-meta shortly, just a refresh to follow the changes to ubuntu's and apparently one of our meta wasn't up to date on ARM (which we don't ship anyway)18:21
stgraberskaet: I've been discussing a NetworkManager/libnl bug in private with cyphermox. It prevents anyone on an ipv6 only network to connect to the internet when they use a static configuration.18:39
stgraberit's a pretty rare setup, thought the annoying part is that if we push the fix as an SRU, they won't be able to install it unless they manually fix the route from a shell (as they won't get connectivity until the fix is downloaded)18:40
stgraberis that something you'd consider for release or should we instead document and get that as SRU (hoping it's indeed a very very rare setup)?18:40
Davieystgraber: Is it a regression from Natty?18:42
stgrabercyphermox: do you know? ^18:43
stgraberDaviey: I would think it's but I don't have a lucid system around me here to easily check18:43
cyphermoxDaviey: I'd venture a "yes", but tbh I didn't spend much time playing with ipv6 on natty18:43
cyphermoxotoh, this part of the NM code didn't really changed that I know of, so perhaps it was the same in natty18:44
DavieyIt's a setup i want to create at home, but i'd expect some tweaking.  I imagine others in the same situation would expect the same, am i wrong?18:44
cyphermoxthere's two issues: one with libnl not playing nice, and one with missing bits in NM18:44
cyphermoxDaviey: what do you mean by tweaking?18:45
stgraberDaviey: well, when filling the IPv6 manual configuration in NM, I'd kind of expect it to actually set that configuration :) and not everything but the default gateway18:45
Davieycyphermox: potential to add my own patches.18:45
cyphermoxah, no, don't think you'd need to add that much18:45
cyphermoxeven if you just set one static ipv6 with a gateway, the default gateway for the interface is never set18:45
cyphermoxpartly due to libnl, partly because there are small bugs in NM for that; plus then it wouldn't be removed, for the same reason18:46
cyphermoxand I fail at copy paste.18:47
cyphermoxstgraber: Daviey: the changes in NM are relatively simple and self-explanatory: http://paste.ubuntu.com/703472/18:47
stgrabercyphermox: wow, that's like the shortest NM patch I've seen in month!18:48
cyphermoxthe change in libnl3 would warrant a quick review, but basically "reverts" to libnl1 behavior: http://paste.ubuntu.com/703546/18:49
cyphermoxstgraber: isn't it two patches?18:49
stgrabercyphermox: right ;)18:49
ScottKstgraber: Accepted edubuntu-meta18:49
infinitycyphermox: Those both look fine to me.18:50
infinityskaet: You willing to hold off your respins for a couple hours for this NM fix?  Your call.18:50
infinityskaet: Actually, we're still updating metas and stuff...18:50
infinitycyphermox: Just do it. :P18:50
cyphermoxinfinity: zug zug18:50
infinitycyphermox: Your Blizzard fanboy is showing.18:51
skaetinfinity,  yeah, and waiting for ev to upload WUBI.18:51
stgrabercyphermox: I plan on running a full ipv6 test on alternate + desktop tomorrow, just to be sure. So having that in now would be good.18:51
skaetWUBI upload is my trigger to kick off the builds.     If anyone has a good reason for waiting for something else,  please post now.18:51
cyphermoxyup, it's a matter of minutes, the packages are pretty much ready and I've been running with them since yesterday18:52
cyphermoxstgraber: I'm going to need sponsoring for the libnl3 changes.19:05
infinitycyphermox: I can sponsor.19:13
infinitycyphermox: Throw me a debdiff somewhere or something.19:14
cyphermoxinfinity: merge proposal good enough? https://code.launchpad.net/~mathieu-tl/ubuntu/oneiric/libnl3/lp856209/+merge/7848519:14
infinityIck.19:14
infinityYes.19:14
infinity(debdiff is so much faster than me checking out a branch I don't normally work with)19:15
infinityI can, however, diff from your MP and live with that. ;)19:15
infinitycyphermox: Is NM on its way to the queue?19:19
infinitycyphermox: libnl3 uploaded.19:20
cyphermoxyes, uploading now19:22
cyphermoxdoen19:22
cyphermoxheh, I could have sent you a debdiff just the same, since I did make one19:23
infinityNo matter, LP diffs for me.19:23
infinityJust easier to apt-get source when I have a local mirror than to checkout a branch I never use.19:23
infinityEspeciall since I have to apt-get source anyway for paranoia.19:23
infinity(I always diff before I upload to make sure there's no cruft in the VCS I'm using)19:23
cyphermoxright. I was paranoiing, hence the slow response19:24
cyphermoxretested the different eth0 wlan0 with ipv6 or without, and mbm and vpns for good measure19:24
infinityI'll accept as soon as I verify these are the same two diffs I reviewed before. :)19:27
* infinity waits for the queueu to get diffy with it.19:28
cyphermoxinfinity: it's not quite the same19:28
cyphermoxinfinity: for NM I added a small thing, just dropping some messages I had forgotten from warn to debug19:29
cyphermoxthat way I don't end up spamming everyone's syslog with 10 extra lines per connection19:30
infinityThat sounds pleasant.19:30
infinityI'll re-review for the hell of it.  It was small. :)19:30
cyphermoxsure19:31
slangasekcjwatson: did the vesafb error suppresion fix go ahead already?19:33
ScottKpitti: Thanks for taking care of moving kde 4.6.5 to -updates.19:54
infinityslangasek: Changelog says no.20:05
infinityslangasek: We're still waiting on wubi, I believe, so go go go? :)20:08
stgraberScottK: thanks (for edubuntu-meta)20:13
ScottKNo problem.20:19
slangasekinfinity: ok, initramfs-tools uploaded; I have not tested it20:21
infinityslangasek: You rebel.20:23
slangasekI'm not rebelling, just informing :)20:23
* skaet shifting location, biab20:24
bdrungtumbleweed: where? i synced it.20:45
bdmurrayI'm gonna rename p-series to Precise okay?21:01
bdmurrayIn launchpad that its21:02
slangasekbdmurray: thanks :)21:03
stgraberare there any script currently looking for p-series that'll need updating?21:03
bdmurrayWell, I was just writing one and didn't want it needing updating ;-)21:03
bdmurrayusing the version is more reliable21:04
skaetbdmurray, thanks :)21:08
bdmurrayhrm, actually it results in an error with out an e-mail address for changes to go to21:09
slangasekah, so we need precise-changes to get set up21:14
bdmurrayor to use the api21:14
bdmurrayI don't have permission to change the displayname though21:15
* infinity thinks we're almost ready for a base-files upload.21:21
DavieyIsn't that usually done on release week?21:22
infinityOr, apparently we're not doing that until -321:22
infinityYeah, getting ahead of the new and improved schedule, apparently. ;)21:22
skaet:P21:23
Davieyinfinity: release later, release okayish.21:23
* Daviey looks at cloud-init21:23
slangasekcjwatson: any traction on bug #745960?21:24
ubot4Launchpad bug 745960 in grub2 (Ubuntu Oneiric) (and 3 other projects) "Cannot boot grub after installing to LVM (affects: 19) (heat: 108)" [High,Incomplete] https://launchpad.net/bugs/74596021:24
Davieyslangasek: Did you see that udev without dbus installed is apparently causing non-deterministic boot fails?21:25
infinitycjwatson: Shouldn't syslinux-themes-* be "Arch: amd64 i386" in light the whole dependency on memtest86+?21:25
slangasekDaviey: um, no21:25
skaetDaviey, is fix for bug 850880 going to land in time for release?21:26
ubot4Launchpad bug 850880 in cobbler (Ubuntu Oneiric) (and 1 other project) "cobbler-ubuntu-import does not pull from -updates (affects: 1) (heat: 6)" [High,In progress] https://launchpad.net/bugs/85088021:26
Davieyskaet: yep21:26
slangasekDaviey: do you have a bug number for this?21:26
slangasekudev itself doesn't use dbus21:27
Davieyslangasek: I'm not sure, hggdh mentioned that jibel was still trying to work out enough information to raise a bug.  I suggested he talk with jhunt tomorrow21:28
slangasekDaviey: ok, well I'm pretty skeptical of this bug description to be honest21:28
slangasekwe have three other known udev issues related to initramfs races21:28
Davieyslangasek: Apparently installing dbus was enough to get reliable booting.. Perhaps it's slowing down the boot.21:28
Daviey*shrug*21:29
slangasekI think it's more likely that they're seeing one of these21:29
DavieyThat is all i know.21:29
slangasekand that dbus is a red herring21:29
slangasekev: how was dinner? :)21:29
Davieysmoser: cloud-init, why did you bump the timeout by 1?21:30
Davieysmoser: So this catches the failure, and re-tries X times.. doesn't just catch and error out, right?21:31
slangasekDaviey: a udev bug report tomorrow is almost certainly too late for us to get any kind of fix in for release.  But then, the same is probably true of a bug report today, so.21:32
Davieyslangasek: I agree that it's probable to be the same issue.. Does that mean the already declared bug is unlikely to be resolved for release?21:34
slangasekDaviey: yes, all of these udev bugs are going to be zero-day SRU material21:35
Davieygeez.21:35
DavieyI would have thought that it was bit of a release blocker.21:35
slangasekthat would imply an unhealthy amount of rushing21:35
DavieySome hardware having 100% boot failure.. Doesn't help them it being in -updates.21:35
slangasekwhat hardware has 100% boot failure?21:35
evslangasek: We're just trying to flag the waitress for the bill21:36
slangasekthat's absolutely not the message communicated in these bugs21:36
Davieyslangasek: Much of the Canonical IS hardware AIUI :)21:36
slangasekthen perhaps you should clarify what you mean by "the already declared bug"21:36
slangasekbecause none of the things we're tracking bear the slightest resemblance to that21:36
slangasek(not that Canonical IS is going to run O on their hardware, but still)21:37
Davieyslangasek: bug 818177 was reported by CorpServices hardware.  bug 862823, was by IS.  Are you certain they don't have the same root cause?21:37
ubot4Launchpad bug 818177 in udev (Ubuntu Oneiric) (and 3 other projects) "boot failures because 'udevadm exit' does not kill udevd worker threads (affects: 8) (heat: 62)" [High,Triaged] https://launchpad.net/bugs/81817721:37
ubot4Launchpad bug 862823 in udev (Ubuntu) "udev causes a kernel panic on oneiric network install (affects: 1) (heat: 39)" [High,Confirmed] https://launchpad.net/bugs/86282321:37
DavieyThe failure jibel is seeing is in kvm..  However, i don't have enough data about that to comment.21:39
slangasekDaviey: 818177 as it's currently being worked is nothing at all like a 100% boot failure.  If that was the original symptom, I'm afraid that's been drowned out by Adam's and Serge's debugging of unrelated configurations21:39
Davieythe 'hardware' is kvm, i mean21:39
slangasek862823 *could* be the same as bug #818177 but there's really not much evidence yet to support this21:40
ubot4Launchpad bug 818177 in udev (Ubuntu Oneiric) (and 3 other projects) "boot failures because 'udevadm exit' does not kill udevd worker threads (affects: 8) (heat: 62)" [High,Triaged] https://launchpad.net/bugs/81817721:40
Davieyslangasek: ah, comment 1 is 1:10 success21:41
slangaseki.e., 862823 has insufficient information to actually implement a fix21:41
DavieyGah, Trellis said he was going to update the bug earlier21:41
Daviey09:30 < Daviey> TREllis: hey, can you comment if you were using LVM to produce bug 818177,21:43
ubot4Launchpad bug 818177 in udev (Ubuntu Oneiric) (and 3 other projects) "boot failures because 'udevadm exit' does not kill udevd worker threads (affects: 8) (heat: 62)" [High,Triaged] https://launchpad.net/bugs/81817721:43
Daviey09:37 < TREllis> Daviey: howdy, originally yes but it's visible without LVM according to the support guys in montreal who were installing oneiric yesterday on the same systems21:43
slangasekright - the LVM issue has been triaged off to a different bug21:43
slangasek(that's the one that adam_g is seeing, principally)21:44
slangasek818177 is now about udev reaping its children, which is a race condition that should happen *rarely*21:44
slangasekif there is hardware that's failing 100%, then we definitely need to escalate21:45
evOn my way to a computer now. Will sort wubi straight away21:45
slangasekev: whoo :)21:45
Davieyslangasek: I'll see if i can grab some more details tomorrow morning.21:47
* ev underground21:48
Davieyslangasek: Ah, Trellis did say that on some hardware they were blocked from testing it because of a binary firmware rename which hasn't been handled.22:00
Davieyhttp://pb.daviey.com/GPWt/22:00
* infinity loves how initramfs-tools uploads make ~1200 packages uninstallable.22:00
slangasekinfinity: buy a bigger hamster22:00
infinityslangasek: amd64 too!22:00
Daviey(which smb and apw where notifed of today, don't know that there is a bug.)22:00
slangasekamd64 is a bigger hamster!22:00
infinityhttp://people.canonical.com/~ubuntu-archive/testing/oneiric_probs.html <-- See?!22:00
infinityOur hamsters are just fine!22:01
slangasekDaviey: right, I saw that error in the original bug data, though I don't understand how it relates to the hang-on-boot symptom22:01
* infinity goes to pet some dev boards.22:01
Davieyinfinity: lets just ship i386, only breaks 5 packages22:01
infinityDaviey: Seems reasonable.22:01
slangasekDaviey: is that hang completely reproducible?22:02
hggdhslangasek: I think this maybe just a race condition; it happens frequently on our Jenkins rig for i386 minimal-virtual server install, and infrequently elsewhere22:03
Davieyslangasek: I only learned of it at 8:30 UTC today, and if you have the scrollback, you know as much as i do.22:04
Davieyinfinity: Is that initramfs-tools induced issue transient?22:06
infinityDaviey: Of course.22:06
DavieyA happy ending.22:07
infinityDaviey: Just a great example of the "archive skew" issue that we keep whining about. :)22:07
slangasekhggdh: what happens, exactly?22:07
slangasekhggdh: I have at least three different udev bugs in the air at the moment, I need a precise description22:07
slangasek(a precise description for oneiric, of course ;P)22:08
hggdhslangasek: as far as I can determine: system boots, everything seems OK; / remains RO, and udev gets completely lost22:09
hggdhafter some minutes you get a login prompt, but / is still RO22:09
Davieyhttp://pb.daviey.com/ohJw/22:09
hggdhreboots may, or may not, reproduce22:09
slangasekhggdh: right.  Bug #818177 to a T then22:10
ubot4Launchpad bug 818177 in udev (Ubuntu Oneiric) (and 3 other projects) "boot failures because 'udevadm exit' does not kill udevd worker threads (affects: 8) (heat: 62)" [High,Triaged] https://launchpad.net/bugs/81817722:10
hggdhyes, really sounds like it22:10
infinitypitti: All ARM-related component mismatches should be taken care of now.22:10
hggdhinteresting is that we pretty much *only* see it on a i386 install22:10
slangasekand dbus is a red herring for that22:10
hggdhI also think so, I was able to reproduce & reboot correctly without it22:11
infinitypitti: Not sure what the story is on then linux-* stuff that wants to fall into universe.  Not sure if that's a failure to seed, or incorrect overrides when NEWing.22:11
infinitypitti: (For x86, that is, I got the ARM linux-* stuff happy, as I said)22:11
slangasekDaviey: ^^ ok, hggdh and I are aligned now :)22:13
Davieysuper22:13
evI see no wubi signed binary. The ticket hasnt been updated22:54
evAm I missing something?22:54
skaetev,  there's was a direct link pasted to #is window.22:54
skaetjust a sec, and I'll grab it again.22:54
skaetev, pasted in pm.22:55
evRight. Sorted22:56
evWubi is ready for the CDs22:56
skaet:)23:01
hggdhslangasek: if it will help any, we are now saving the boot log (actually, the console log) on Jenkins, so next time it fails we will have it23:04
slangasekhggdh: I think that particular bug is well-understood now, and the console log doesn't give too much relevant debugging detail by default; I might have some test packages later that would give more interesting output though23:07
skaetev, where should I be looking for Wubi to land before triggering builds?23:24
slangasekskaet: it's published directly via people.canonical.com and pulled from there onto antimony by the build scripts; so if ev says "ready", you should be able to trigger anytime23:29
skaetslangasek,  thanks!!23:30
slangasekskaet: hold23:30
skaetholding23:30
slangasekhttp://people.canonical.com/~evand/wubi/oneiric/ doesn't show anything updated after 17:40pm23:30
evNo, thats correct23:30
skaetslangasek, wubi-r241-signed.exe is there23:30
evIt's the stable symlink23:30
slangasekok23:31
evWhich points to 241-signed23:31
skaet17:41 is when it was created by IS23:31
slangasekit's just backdated?23:31
slangasekah, ok23:31
slangasekskaet: good to go then :)23:31
skaetslangasek, ev,  thanks \o/23:31
evSure thing23:31
skaetWUBI, CDs, DVDs building...23:35
skaetDaviey,  any last updates I should be checking for being built, before kicking off server?23:37
smoserDaviey, I did bump the timeout.  previously it was not catching that error and thus exiting without retrying.  i bumped the timeout to increase the chance of getting a response before giving up.23:46
smoserthe fact is, that on nova, the MD service is painfully slow, and 2 seconds might not return . so all we're doing is killing it by repeatedly asking it for something.23:47
smoseri dont want to disable the timeout *and* retry, because then ew'd potentially do X retries with OS default timeout (which is quite long).23:48
infinityskaet: I see a cloud-init upload still being debated for server.23:56
infinitysmoser: Accepted.  Even if it's the wrong solution, I fail to see how it's much worse.23:57
skaetinfinity, ok.  will wait for it to build, and then trigger the alternates23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!