/srv/irclogs.ubuntu.com/2012/07/02/#ubuntu-release.txt

ogra_hmm, whats that update-apt-xapian-index issue in the image builds ?09:02
Laneybug #101958109:03
ubot2Launchpad bug 1019581 in software-center "update-apt-xapian-index crashed with ImportError in /usr/share/apt-xapian-index/plugins/software-center.py: cannot import name index_name" [Critical,Confirmed] https://launchpad.net/bugs/101958109:03
ogra_ah09:04
jibelogra_, I just pinged mvo on #ubuntu-desktop09:04
ogra_we really should have a variable to skip it09:04
ogra_so you can temporary build images without updated index09:04
cjwatsonjibel: I just nagged on #ca-internal too09:11
cjwatsonogra_: I considered that but it seems entirely possible that this breaks some upgrades too, so I didn't want to work around it and help to take it off the radar09:11
cjwatsonCan't be that hard to just fix09:11
ogra_indeed ...09:12
ogra_hmm, seems i forgot to disable kubuntu preinstalled builds09:13
ogra_did someone just disable them in bzr ? i get a merge conflict09:18
ogra_(looks like /srv/cdimage.ubuntu.com/etc/crontab was hacked directly or some such09:19
ogra_)09:19
ogra_... hmm, and wasnt installed with the crontab command at all09:20
cjwatsonI'm pretty sure Daviey did that a few days back09:20
ogra_hmpf09:20
cjwatsonmerge conflict> you mean when trying to pull into /srv/cdimage.ubuntu.com?09:21
ogra_right09:21
cjwatsonAre you on top of it or do you need help disentangling it?09:21
ogra_i removed the kubuntu preinstalled line while the tree has it manually commented and seemingly uncommitted09:21
ogra_well, just editing it in the tree and a bzr resolved should do, no ?09:22
cjwatsonFor the time being, yes09:22
ogra_k09:22
cjwatsonI usually check 'diff -u etc/crontab <(crontab -l)' rather than just blindly overwriting the live copy09:22
cjwatsonBecause it's very common to only comment out the live copy during milestone prep09:23
ogra_yep09:23
ogra_hmm, thats quite a big diff09:31
cjwatsonThat's just "uncomment lots"09:35
cjwatsonLet me resolve some of it09:35
ogra_yes09:35
ogra_well, i'm just pulling the original crontab into the tree here09:36
cjwatsonTry that09:36
cjwatsonetc/crontab should never have been edited locally in the first plac09:36
cjwatsone09:36
ogra_right, i know09:37
cjwatsonEither commit to bzr, or do it just in 'crontab -e' for temporary stuff, not a weird halfway house09:37
cjwatsoncommitter: CD Image <cdimage@nusakan>09:37
ogra_well, it shouldnt have gotten into that condition in the first place09:37
cjwatson  fix etc/crontab conflict (please dont edit directly on nusakan, or at least commit it to the tree)09:37
cjwatsonThe irony hurts.  Please edit on your local system not on nusakan09:38
ogra_yes, that was me09:38
ogra_how can i, i dont get the conflict over here09:38
cjwatsonGood grief, scp exists09:38
cjwatsonCan I resolve this?09:38
ogra_yes, i'll keep my fingers off it09:38
cjwatsonI realise this isn't your fault but I want to carefully get this back to a sane state ...09:39
ogra_so how would you do it (for the next time) ? scp the whole tree from /srv/cdimage to your local machine and discard your existing working tree ?09:40
cjwatsonHeck no09:40
cjwatson1443 should never have been committed; that should have been reverted on nusakan instea09:40
ogra_then i dont get it09:40
cjwatsond09:40
cjwatsonIf it's already edited locally on nusakan, then you can edit there for the purpose of undoing things or resolving the conflict, but you must never commit on nusakan09:41
cjwatsonYou can copy the file back locally to commit09:41
* ogra_ is irritated ... 09:42
ogra_so there was a change on nusakan that wasnt committed ... usually i get an uncommitted changes error here, and bzr would refuse to go on with the merge ... why didnt that happen here09:43
cjwatsonBecause it was only not committed in the working tree you were pulling into09:44
cjwatsonNot the tree you were running merge in09:44
ogra_it merged and created the conflict .. that shouldnt be possible09:44
ogra_oh, stacked trees09:44
ogra_*lightbulb*09:44
cjwatsonIt's all resolved now.09:44
ogra_thx09:45
* ogra_ wonders why ac100 initrds are suddenly built with lzma09:55
=== yofel is now known as Guest57033
rbasakWhat's the quantal publishing interval now? 20 minutes?11:17
cjwatson3011:18
cjwatsonIt starts at :03 and :3311:19
rbasakThanks11:20
cjwatson(FWIW, not that this is well-known or anything, but I believe anyone in Canonical can check out lp:lp-production-crontabs now and the times are there)11:25
cjwatsoncocoplum-lp_publish in particular11:26
rbasakIt seems I can - thanks.11:35
xnoxlast daily image is from 29th, long weekend for the CD-building? (this is daily-live/quantal/amd64)11:43
cjwatsonxnox: bug 101958111:44
ubot2Launchpad bug 1019581 in software-center "update-apt-xapian-index crashed with ImportError in /usr/share/apt-xapian-index/plugins/software-center.py: cannot import name index_name" [Critical,Fix released] https://launchpad.net/bugs/101958111:44
cjwatsonbroke image builds all weekend11:44
cjwatsonI whined about it on Saturday morning but nobody relevant was aruond11:45
cjwatson*around11:45
Laneyand you can see why they failed if you look at the livefs build logs, for example http://people.canonical.com/~ubuntu-archive/livefs-build-logs/quantal/ubuntu/20120702/livecd-20120702-amd64.out11:46
xnoxcjwatson: Laney ok thanks11:48
mvocjwatson: should be fixed now11:52
mvosorry for the breakage11:52
cjwatsonta11:53
cjwatsonOops, didn't catch that in time ...12:58
cjwatsonmute queue new quantal-release12:58
=== Guest57033 is now known as yofel
mterryHello!  Would someone mind pushing a few packags from quantal-proposed to quantal for me?   update-manager, ubuntu-release-upgrader, and update-notifier source packages14:15
cjwatsonunmute queue new quantal-release14:15
cjwatsonmterry: done14:16
mterrycjwatson, thanks!14:17
mterryIs there any reason aisleriot is in main still?  It's not seeded anymore14:55
seb128mterry, it's not? it was still on the CD for precise I though14:56
seb128mterry, did we drop it since?14:56
mterryseb128, I just ran seeded-in-ubuntu, but I thought it had been dropped in precise, so I might be wrong here14:56
mterryseb128, yup, still recommended by ubuntu-desktop14:57
seb128mterry, cool14:57
mterryseb128, seeded-in-ubuntu's got some 'splaining to do14:57
LaneyWe should drop it though.14:59
LaneyNobody's going to work to get guile-2.0 into main14:59
Laneyseb128: ^^^14:59
Laney(plus guile-2.0 FTBFS on arm)14:59
tumbleweedhrm, it's in the manifest15:00
* tumbleweed looks at why seeded-in-ubuntu got that wrong15:00
Laneytumbleweed: it's not wrong15:01
Laneyhttps://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/ubuntu.quantal/view/head:/desktop#L11915:01
Laneyoh, false /negative/15:01
Laneybecause it depwaits?15:01
seb128Laney, or we should got back to the old version15:01
tumbleweedah, one of those15:01
tumbleweedwe should display a warning for that, as it's a known issue15:02
seb128Laney, if it depwaits we can just delete the source and reupload the old version ;-)15:02
seb128without having to tweak15:02
Laneyreally?15:02
Laneythe source would be published, no?15:02
seb128Laney, yes, pitti did that one beofre15:02
seb128once15:02
cjwatsonErr15:02
cjwatsonIf you can that's a Soyuz bug and I find it quite doubtful15:02
seb128Laney, soyuz doesn't check for that15:02
cjwatsonI would really very much prefer that you did not do that15:03
LaneyI remember going backwards but I can't remember why it was ok15:03
micahgthe source being published isn't a problem, it's the binaries that are an issue (you just can't use the same version again)15:03
Laneythere are no binaries.15:03
seb128right15:03
seb128cjwatson, hum k, it was handy though :p15:03
cjwatsonPlease just be explicit and bump the version forward if you're going to revert15:03
Laneymaybe it hadn't been published yet or something15:03
micahgthat's why totem is precise didn't have a crazy version number15:03
cjwatsonexplicit is better than implicit15:03
micahg*in15:03
seb128micahg, yes15:03
Laneyah, it was even cjwatson wot done it last time15:04
micahgcjwatson: why should it matter if a source was published?  that's just used for uploading new sources, as long as there were no binaries, there's no apt/dpkg issue15:04
cjwatsonhaha, ref?15:04
Laneyhttps://launchpad.net/ubuntu/+source/totem/+publishinghistory15:04
seb128cjwatson, https://launchpad.net/ubuntu/+source/totem/+publishinghistory15:04
seb1282012-01-10 01:10:17 CET Deleted Precise release main gnome 3.3.4-0ubuntu1~precise115:04
seb1282012-01-13 12:37:39 CET Superseded Precise release main video 3.0.1-0ubuntu1315:04
seb128cjwatson, 3.3.4 was uploaded by error and never built15:05
cjwatsonmicahg: I'm aware of that, there are all sorts of things inside Soyuz and in API scripts that make stronger assumptions about ordering that are reasonable as long as people aren't playing silly buggers15:05
seb128pitti deleted the source and we reuploaded 3.0.1 which worked15:05
Laneywasn't pitti15:05
seb128oh, I though it was15:05
Laneyexpand "deleted" and you can see15:05
seb128sorry15:05
cjwatsonHah, right, I wouldn't do that again15:05
seb128heh15:06
cjwatsonBut I guess that means it works at least sometimes15:06
micahgcjwatson: I guess that's the "trouble" of knowing the code :)15:06
cjwatsonIndeed15:06
seb128Laney, well anyway I guess we are good to do a new.is.really.old upload15:06
* Laney would still prefer to replace it with sgt-puzzles or nethack :P15:06
cjwatsonLaney++15:06
cjwatsonI guess that the above hack mostly worked because things tend to do archive.getPublishedSources()[0]15:07
cjwatsonSo it ends up being most recent by upload order15:08
cjwatsonAll this stuff is in code I'm not convinced anyone gets right though, which is a reason I'm newly wary of it15:08
cjwatsonThe other day I discovered three different implementations of roughly the same ancestry detection logic, none of which I entirely agreed with15:08
cjwatsoninfinity: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1019514 passed my test, FWIW19:03
ubot2Ubuntu bug 1019514 in livecd-rootfs "Need to be able to generate images with -proposed in sources.list" [High,Fix committed]19:03
* infinity checks the log.19:12
infinity0 upgraded, 0 newly installed, 0 to remove and 18 not upgraded.19:13
infinity^-- This would probably take some live-build hacking, but an upgrade post-debootstrap would be a good idea.19:14
infinitycjwatson: Maybe not critical for proposed testing, but would seem the right thing to do for actual point-releases, so -security and -updates packages are installed on the image.19:14
infinitycjwatson: Oh, never mind, that happens later in the log.  I guess someone thought of this already. :P19:15
infinitycjwatson: Looks good, then.19:16
infinitycjwatson: Fast-tracking it through.  Thanks for the test output.19:17
cjwatsonGreat, thanks.  And as you say.19:19
=== robbiew is now known as robbiew-afk
=== bjf is now known as bjf[blood]
=== robbiew-afk is now known as robbiew
=== bjf[blood] is now known as bjf

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