/srv/irclogs.ubuntu.com/2010/08/27/#ubuntu-release.txt

slangasekScottK: bit of NBS processing done; all these kernels makes the recommended commandline too long to cut'n'paste at one go, so I'll do another run a bit later, but that should help make it more readable00:28
=== jjohansen is now known as jj-afk
ScottKslangasek: Thanks.04:42
ScottKWahoo!  KDE 4.5 built on armel for the first time ....04:52
* persia cheers upstream.04:55
GrueMasterDoes anyone know why ubiquity-frontend-gtk-2.3.8 is not building for armel?  It is blocking image builds.06:45
* persia looks, and suggests #ubuntu-devel as a better forum for that class of question in general06:47
persiaOh, it built.  Just waiting to be published (https://launchpad.net/ubuntu/+source/ubiquity/2.3.8/+build/1935852)06:47
persiaShould be out in a bit.06:47
GrueMasterok.  Not sure how the process works.  Since all of the packages come from the same source, I thought they would go at the same time.06:48
persiaSo, the source gets processed (NEW/Unaccepted/Accepted), and then gets added to the build queues.  The buildds pull from the build queues whenever they have time (some architectures are faster than others).  When a build finishes, it gets processed (NEW/Unaccepted/Accepted), and then gets published, after which it gets mirrored, after which you can grab it.06:50
persiaSince the buildd queues are all different lengths, and the buildds different speeds, there are often differences between the publication time for different architectures.  This can lead to issues on amd64, armel, and powerpc when there are package relationships between arch:all and arch:any binary packages.  But the assumption is that most folks run i386, where it just works.06:52
GrueMasterOk.  All run by cron jobs I would assume.06:52
persiaNo.06:53
persiapublication is on cron.  If a package gets caught in NEW or Unaccepted, it's a manual action to get it out (either source or binary).  builds are queued as soon as the sources are processed (I believe this used to be cron, but got changed to avoid the 3-hour delay between upload and availability)06:54
GrueMasterHmm.  Well, too much to consume before bed.  I'll manually pull it and install.  Want to see if I can make forward progress before bed.06:54
persiaOK.  I'd expect it to be on ports in ~15 minutes.06:55
evKDE ubiquity is busted on today's daily-live.  Seems to be a privileges thing; looking into it.08:43
KE1HAev:  saw that on a couple other daily's as well. was told it could be the Artwork uploads doing it.08:51
evKE1HA: older KDE ones?08:52
KE1HAnot older ones no, from today.08:52
KE1HAtoday being 26th :-)08:52
evheh, indeed08:52
evwhich ones, specifically?08:52
KE1HAXub and UB alts08:53
KE1HAamd6408:53
evalts?  Alternates?08:53
KE1HAYes08:53
evubiquity is not on the alternate CDs08:54
KE1HAI know.08:54
KE1HAwas the same issue though.08:54
evhow so?08:54
KE1HAHmm good question, I tryng to remember who told be this as said same thing happening on Ubiq iso too.08:55
KE1HAI stopped testing on the 3rd failed ISO08:55
KE1HAev I can't remember who it was, ... that's gonna bug me, it was a developer though, I know that.08:57
evwhat was the exact error you were seeing?08:58
evand was this during, or post-install?08:58
KE1HAI had to try and switch mirrors, and the apt portion failed.09:00
KE1HAIt was during install, never made it to the end.09:00
evKE1HA: not sure who told you it was the same bug, but it definitely was not.09:01
evthe bug I'm describing prevents ubiquity from even starting.  It never makes it to apt-setup.09:02
KE1HAHe didn't say it was Bug per say, but he said it was due to the updates with Artwork.09:02
KE1HAIf yours ins't starting at all, probably unrelated I suppose.09:04
evindeed09:15
cjwatsonScottK: on its way.  I was out yesterday.10:05
cjwatsonoh, needs some work cocoplum-side to make it useful10:05
cjwatsonpersia: s/Unaccepted/Unapproved/g in your explanation above, FWIW10:10
cjwatsonctrl-c'ing the bot to avoid flooding the channel until such time as language packs are out of the queue10:11
persiacjwatson, Right.  Thanks for the correction.10:12
cjwatsoncan people please STOP NBSing old kernels before d-i has been updated to use the new ones?!11:53
cjwatsonI'm getting kind of fed up of spending time debugging problems that turn out to be due to this.11:54
cjwatson(bug 624915)11:55
ubot4Launchpad bug 624915 in linux (Ubuntu Maverick) (and 3 other projects) "maverick kvm guests not seeing virtio disks (affects: 1) (heat: 6)" [High,Invalid] https://launchpad.net/bugs/62491511:55
persiaIs there a way to update the NBS script to detect that d-i still needs the kernels?11:55
cjwatsonpretty hard11:55
cjwatsonmaybe the people who like to blindly apply its output could do that11:56
persiaheh.  Right.  Doesn't sound worth it to look into the hard bits.11:56
cjwatsonI'm sure it's possible since there's a udeb manifest in the archive11:56
cjwatsonunder dists/maverick/main/installer-*/11:57
ogracan someone let jasper through please (it fixes a hard hang of the omap4 images)12:20
cjwatsonHas somebody been removing old CD build logs from antimony?13:03
cjwatsonPlease don't ever do that in future.  Whoever you are, you've made it impossible for me to investigate the exact set of circumstances leading up to bug 597734.13:04
ubot4Launchpad bug 597734 in debian-installer (Ubuntu) "kernel version mismatch between debian-installer and CD-ROM (affects: 1) (heat: 54)" [Undecided,New] https://launchpad.net/bugs/59773413:04
ScottKcjwatson: Thanks for the bot.13:48
=== bjf[afk] is now known as bjf
ScottKogra: All the armel build failures for KDE are (finally) fixed.  Once there is room in the queue, it would be good to try and spin an armel image (understanding it's not the priority)16:00
ograScottK, i thought that already happened16:00
ScottKogra: Maybe it did.  I didn't look.16:00
* ogra saw someone paste a url somewhere 16:01
ograhttp://cdimage.ubuntu.com/kubuntu-mobile/ports/daily-preinstalled/current/16:01
ogra(will still be broken until someone approves my jasper-initramfs upload)16:01
* ScottK pushes the big red button.16:07
ScottKogra: Accepted.16:07
ograsweet, thanks16:07
GrueMasteromap only?  No omap4?16:09
GrueMasteror is it still building?16:10
ograGrueMaster, if omap userspace works for kde and we know that omap4 kernel/bootloader work in ubuntu we currently save buildd time, i'll enable omap4 builds after beta for kubuntu16:11
ogranobody out there can test omap4 atm16:11
GrueMasterok16:11
GrueMasterwell, me (assuming we get our images working again).16:11
ScottKogra: We don't have an armel image for Kubuntu desktop yet.16:12
ScottKhttp://cdimage.ubuntu.com/kubuntu/ports/daily-live/current/16:13
ograi think NCommander enabled something in the crontab that just wasnt built yet16:13
* lamont has been shuffling buildds amd64->i386 and back to flush the langpack queue faster16:16
ScottKogra: Cool.  I thought he was just working on the kubuntu-mobile stuff, but we'll see.16:23
jdstrandhey, so avahi is sitting in binary new since it is a merge from Debian. it does not reference a bug-- has someone from ubuntu-release ack'd it?17:48
jdstranderr, a merge and has a new binary17:49
seb128it was uploaded  before the freeze not sure it needs a ack from binaries waiting there?17:50
seb128ie it got blocked in binnew as any packaged having new binaries17:50
jdstrandwell, the version is 0.6.27-2ubuntu1 and we currently have 0.6.25-1ubuntu617:51
jdstrandso we seem to be in a gray area, and I thought I'd ask17:51
ScottKGiven how long it's sat, having it sit until after beta may not be a bad idea.  Technically it doens't need a freeze exception though.17:52
jdstrandScottK: because of the timing of the upload?17:52
jdstrandScottK: ie, it technically doesn't need one because of the timing of the upload?17:53
seb128jdstrand, well we can't refuse the binaries for maverick17:57
seb128if we don't want the new version we will need to downgrade the source17:57
jdstrandseb128: I wasn't suggest refuse the binaries. I was curious about the beta freeze17:58
jdstrandseb128: and perhaps waiting to accept until after, like ScottK said17:58
seb128seems there is a soname change so we might as well wait17:58
seb128not my call17:59
seb128on one side we might want to test the new version in beta17:59
jdstrandright, mine either, hence the question here :)17:59
ScottKjdstrand: Yes.  Because of the timing of the upload.18:01
* jdstrand nods18:02
jdstrandScottK: can you look at https://wiki.ubuntu.com/ArchiveAdministration#Archive%20Administration%20and%20Freezes and tell me if it is accurate. I looked at https://wiki.ubuntu.com/FreezeExceptionProcess and it wasn't clear18:22
jdstrandScottK: specifically for the universe/multiverse bits18:22
ScottKjdstrand: I'm about to head out for a while.  I'll try and have a look later.18:27
jdstrandScottK: thanks18:27
evI'd greatly appreciate it if someone could review and accept the freeze exception for the ubiquity upload I just did.  Bug 62547219:20
evWithout it, KDE users wont be able to install from the desktop CD.19:20
ubot4Launchpad bug 625472 in ubiquity (Ubuntu) "Beta freeze exception for 2.3.9 (affects: 1) (heat: 8)" [Undecided,Fix committed] https://launchpad.net/bugs/62547219:20
ScottKev: Looks good.20:12
ScottKDownside risk is nil in any case.20:13
ScottKJust going to double check with sistpoty since he commented in the bug.20:14
sistpotyScottK: actually, I always forget about the exact uid handling, so I wrote a test program... however that actually fails at the setegid(1000)... still not too sure why. so seteuid(0) and setegid(0) seems to do the right thing20:16
ScottKsistpoty: Are you OK if I accept it then?20:16
sistpotyScottK: sure, just go ahead20:16
ScottKsistpoty: Thanks.  Would you please mark the bug approved.20:16
sistpoty(and sorry, for not getting my test program right in the first place)20:16
ScottKI think it delayed things by a full four minutes, so the consequences are pretty severe....  ;-)20:18
sistpotyheh :)20:18
ScottKev: It's in.20:22
* ScottK isn't reviewing ^^^20:41
* sistpoty tries to be invisible20:43
ScottKjdstrand: I agree it doesn't look quite right (incomplete update when motu-release and ubuntu-release were combined).20:48
ScottKsistpoty: Would you please read through https://wiki.ubuntu.com/FreezeExceptionProcess and see what you think of the Universe/Multiverse specific things we need to keep?20:57
slangasekwrt avahi which came up for discussion earlier, the only revdeps of libavahi-core6 in main are from the same source package20:57
sistpotyScottK: sure, will do20:57
ScottKThanks.20:57
slangasekso I think it'd be fine to take this now rather than waiting to post-beta20:57
ScottKslangasek: If you think so, then I'd say go ahead.20:57
GrueMasterScottK: The maverick-preinstalled-desktop-armel+omap.img is missing the vfat partition.  This is a bad image.21:01
ScottKOK.  How do we fix that?21:01
* ScottK looks around for ogra.21:01
GrueMasterI'm going to try to hack it together with our netbook image to see if it works.  Beyond that, it's an ogra thing.21:01
ScottKThanks.21:02
GrueMasterI should be able to dd the netbook image on, then overwrite the rootfs with the kubuntu one.21:03
sistpotyok, got a few points that I'll try to reword. However I'm unsure about: "FeatureFreeze for bugfix-only updates"21:07
sistpotythe section seems to imply that bugfix only updates are only suitable for universe/multiverse, but I think practice differs... make that section general for all packages?21:08
ScottKsistpoty: The difference is that in Universe/Multiverse we had a historical practice of requiring a bug to be filed to document it.21:13
ScottKI think we can drop that now.21:13
sistpoty*nod*21:18
ScottKI think there ought to be some discussion about seeded versus uneseeded packages in freezes, but I don't think we need any Universe/Multiverse specfic stuff anymore.21:22
sistpoty*nod*21:23
ScottKslangasek: I'm about to head out for a while.  The new ubiquity built and should be in the archive in ~20 minutes.  Would you please kick off Kubuntu live i386/amd64 rebuilds once it is so we can get the installer changes smoke tested?21:24
slangasekScottK: ack21:25
ScottKThanks.21:25
sistpotyhmpf, just updated the FFe page in the wiki, and don't find the knob to revert it back to the old version (so that the changes can be discussed on the mailing list, and my bad grammar and spelling can be sorted out)21:38
skaet sistpoty, can you bounce me the link to FFe page,  haven't encountered that one yet.21:59
sistpotyskaet: https://wiki.ubuntu.com/FreezeExceptionProcess21:59
sistpoty(sorry, should have added that to the mail)22:00
skaetsistpoty,  thanks!22:00
=== bjf is now known as bjf[afk]
slangasekScottK: kubuntu images rolled22:52
ScottKslangasek: Cool.  Thanks.  Just got back.22:52
GrueMasterScottK: Copying the kubuntu-preinstalled-desktop image over the top of the UNR armel image appears to be working so far.  System is very slow, but I am now in oem-config, which is a good sign.23:02
ScottKGrueMaster: Cool.  So we just need to get the vfat problem solved and we should be good, right?23:03
GrueMasterErr, no.  oem-config just crashed.  sigh.  I'll file a bug and get back to you.23:04
GrueMasterBut the vfat issue will need to be fixed for sure.23:05
ScottKGrueMaster: Thanks.23:10
* ScottK hopes for ogra to appear with a fix.23:10
GrueMasterhe's afk for the day.23:11
ScottKSurely if we repeat his nick enough he'll reappear.23:11
GrueMasterIt's 12am his time.  Doubtful.23:13
ScottKRight, then there's also the risk he might not be sober enough to give good advice even if he did appear.23:13
GrueMasterheh.23:14
ScottKslangasek: Would you please demote kubuntu-mobile to Universe.  It shouldn't be in Main and (as one might expect) isn't installable just with Main.23:24
GrueMasterScottK: http://paste.ubuntu.com/484686/ is the failure, but there is a new version specific to qt/kde.  Will pull that and try again before filing bug.23:26
cjwatsonScottK: it seems to be seeded for main though23:26
ScottKcjwatson: A while ago I mailed you about trying to figure out how to build two metapackages out of the same source one for Main and on with Universe.  We never got a chance to discuss it.  No doubt we missed something in trying to set it up.23:28
cjwatsonhmm23:29
cjwatsondon't suppose that mobile could live in a different seed collection, rather than kubuntu.maverick?23:30
cjwatsonthat's what drives it23:30
cjwatsoncould somebody review debian-installer in the queue?  it's needed to get armel to build23:31
ScottKAlso didn't figure out how to have a metapackage names kubuntu-mobile that wasn't built off of kubuntu-meta23:31
cjwatson'Task-Metapackage: kubuntu-mobile' at the top of the relevant seed23:32
ScottKRight.  Some things are too obvious.23:33
ScottKOK.  I'll work on that.23:33
ScottKcjwatson: I'll take care of accepting D-I.23:39
cjwatsonthanks23:39
ScottKDone.  That's probably the one time ever D-I will have a trivial enough diff for me to be confident reviewing it.23:40
ScottKGrueMaster: That smells like somethe the latest updates should fix.23:41
ScottKcjwatson: No doubt you know, but it FTBFS on armel.23:56
persiaWouldn't moving kubuntu-mobile to a new seed require landing a patch to cron.germinate in LP?23:56
persiahttp://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/annotate/head:/cronscripts/publishing/cron.germinate23:56

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