infinityAlternates re-spun, if someone who knows how the ISO tracker works wants to post them. :P00:04
stgraberinfinity: all of them or just ubuntu?00:06
infinitystgraber: The whole shebang.00:06
infinitystgraber: live/desktop/preinstall/whatever images are still grinding away, but alternates should all be ready.00:07
stgraberok, posting them on the tracker00:07
slangasekare none of the live images done yet?00:09
stgraberinfinity: I'm guessing that includes server too. What about the omap and omap4 build for server, was that part of it too?00:12
stgrabernevermind, I see them on cdimage00:12
mdeslaurbug 855171 may be worth mentioning in here00:13
ubot4Launchpad bug 855171 in nss (Ubuntu) (and 1 other project) "libnss3.so went missing after upgrade (affects: 2) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/85517100:13
stgraberinfinity: ok, I think I got them all, only left disabled on the tracker are the upgrades (not sure why so didn't re-activate), desktop builds and dvd builds00:14
slangasekmdeslaur: can you attach an apt term.log, which is generally more usable than a dpkg.log?00:16
slangasekthe file's missing here too, how incredibly rude.00:18
slangasekconvenient that I hadn't rebooted yet, I guess00:18
mdeslaurslangasek: attached00:19
slangasekmdeslaur: do you know when you last had it00:19
mdeslaurI had it when I booted the laptop just before doing the dist-upgrade00:19
mdeslaurso, whatever you see that's dated the 20th is when it happened00:19
slangasekI am going to be annoyed if this turns out to be a knock-on effect of running update-ca-certificates00:23
slangasekwhich is looking likely00:23
doko_slangasek, is there something wrong with java-ca-certificates update?00:33
slangasekdoko_: yes, the do_cleanup() function is nuking the system libnss300:33
slangasekdoko_: can you have a look at it?00:33
doko_slangasek, ok, first thing tomorrow morning. not now, just too tired00:34
slangasektomorrow morning is too late00:34
slangasekif you're not free to do it now, that's fine; but this is eating users' systems in realtime00:34
slangasekno nss3 == no network-manager00:34
infinitystgraber: Thanks.00:35
* infinity goes to make some food.00:36
doko_slangasek, there was a suggestion to drop the libdir setting in nss.cfg. openjdk does have the multiarch path on the default libpath.00:42
slangasekdoko_: should we take this to #ubuntu-devel?  RAOF is also looking at it there, probably better to not have too many people working on it in parallel00:43
infinityFailed to fetch http://ftpmaster.internal/ubuntu/pool/main/c/ca-certificates/ca-certificates_20110502+nmu1ubuntu2_all.deb  403  Forbidden00:49
* infinity blinks.00:49
infinityslangasek: Did I miss a memo?00:51
slangasekinfinity: yes00:51
slangaseklook up00:51
infinitySo, all these images are useless? :P00:51
slangasekyou can use them as virtual coasters00:53
infinityI need a virtual microwave to make them crackly.00:54
stgraberinfinity: btw, you should now have admin rights on the tracker00:56
infinitystgraber: Shiny, I suppose that means I'd need to learn how to make it go, then.01:00
infinityAnyhow, with ca-certificates in standard, that invalidates every image except for core.  Woo.01:00
* infinity kills the builds that were in progress still...01:00
charlie-tcaooops ;(01:02
* GrueMaster weeps for humanity01:03
slangasekinfinity: ca-certificates-java uploaded01:06
slangasekinfinity: please to reviewing01:06
slangasekor if you prefer, I'll accept it myself (but then I should probably test it first)01:07
infinityslangasek: I'll review when it lands..01:10
slangasekca-certificates-java doesn't affect all the images01:11
slangasekbut I think ca-certificates should gain a Breaks: on the old version of ca-certificates-java to enforce the upgrade in tandem01:11
slangasekactually, Conflicts:01:12
infinityWhich then affects all images.01:12
slangasekinfinity: you're holding the baton; what do you think?01:13
infinityI think I have a date tonight, but the baton is relocatable. ;)01:13
infinityI do think we should respin for it, though.01:14
slangasekfor -java, yes01:14
doko_hmm, ca-certificates-java should only be on DVD images01:16
slangasek-java tested locally, confirmed that I still have libnss3.so01:16
infinityslangasek: I may be coming into this discussion late, but how is it ever a good idea (even with this lovely guard in place) for a random package to delete libraries?01:16
doko_infinity, because it did create the link01:17
infinity(The code looks to do what it wants to, though)01:17
infinitydoko_: Ahh, it's a symlink (or, it is when we want it dead)?01:17
infinityA -L guard might have made that more obvious too.01:17
doko_infinity, it's a hard coded value in nss.cfg, but we need it to run the update01:18
slangasekdoko_: it's on {kubuntu,ubuntu,edubuntu} DVDs and ubuntu-server, but the question is if we want to update ca-certificates as well for all the users who might have -java installed locally and be affected01:18
* infinity nods.01:18
slangasekinfinity: right, it's meant to only be cleaning up symlinks created in this same script01:18
slangasekbut it, ah, missed01:18
infinityslangasek: Check.01:18
doko_slangasek, if it's safer this way, fine01:19
slangasekthe damn thing is, I *saw* the ca-certificates-java error backtrace when I was preparing the ca-certificates update, and assumed it was an innocuous pre-existing problem... I should have followed up on that error earlier :/01:19
infinityslangasek: I'm just going to go on record as saying that's one hell of an ugly and opaque shell script for something that appears to accidentally nuke files, but it looks like it should do what it says on the tin, so accepted.01:21
infinity(Well, until the next time something weird happens)01:21
slangasekinfinity: thanks.  so, you still hold the baton, what would you like to do?  I can prep a ca-certificates upload with the Conflicts quickly enough...01:21
infinityslangasek: Well, the conflict is sane anyway, I think.01:21
slangasekand if you need to pass the baton off to me, I can take it01:21
infinityslangasek: Personally, I think that warrants a rebuild.01:21
* slangasek nods01:21
slangasekdone then01:22
slangaseksince the breakage was introduced in a narrow range of versions in oneiric, I'll probably make it an == conflict to not complicate natty->oneiric upgrades01:24
infinityslangasek: I already killed the arm builds, which take longer than everything else combined, so it's not like this makes things worse.01:26
slangasekca-certificates uploaded01:30
infinityslangasek: There was only one broken -java version?01:30
slangasekinfinity: in Ubuntu, yes01:30
slangasekpublisher running01:52
slangasek(or jogging in place)01:52
micahg^^ that can wait until after beta 2, it's an FTBFS fix, but part of the ubuntustudio packageset02:24
micahgany objections from the release team for me to use the buildds for mozilla updates (all short ATM, will ask again before the long Firefox 7 ones)03:13
infinitymicahg: Any chance you can do them serially?03:20
infinityI don't really feel like putting buildds on manual, not when I'm not sure how long I'll be up.03:21
micahginfinity: the buildd manager will max out at 60% for the PPA03:21
micahgso that's 1 for the 2 arch ones, 3 for i38603:21
infinityWhen did this happen?03:21
micahg*2 per arch03:21
infinityCause I've seen two ppa builds on the powerpc buildds before.03:21
micahginfinity: a year or so ago?03:21
micahginfinity: I'll only be using one PPA03:22
micahgit's per PPA03:22
infinityIf you're sure you'll only eat one ppc buildd, go nuts. :P03:22
infinityI wasn't aware of this new shiny.03:22
micahgyeah, I'm sure :)03:22
infinityOf course, the kernel ppa will come bite me anyway.03:22
micahgI can't speak for the kernel team, anyways, my builds should only be 1.5 hrs at most on PPC03:22
micahginfinity: and since I don't need them until next week, I won't be upset if someone kills it03:23
pittiah, seems the netsplit has been fixed, according to global notice07:58
pittijibel: so seems we can continue talking here07:58
pittijibel, ev, cjwatson: I debugged bug 854717 and suggested a workaround08:23
ubot4Launchpad bug 854717 in ubiquity (Ubuntu Oneiric) (and 1 other project) "Broken panel icons and dialog style during ubiquity-dm and OEM install/final user configuration (affects: 2) (heat: 12)" [Critical,Confirmed] https://launchpad.net/bugs/85471708:23
evpitti: thanks! I'll make that change momentarily.  Reviewing your other patch now, though I don't think it's quite right. If you call stop_debconf while a page is running, you'll rip debconf from under its feet.08:25
evI'll have a think about it08:25
pittiev: right, I wasn't sure whether it's correct to call stop afterwards; but as it was stopped before, it seemed safer to stop it again08:26
pittiunless it's safe to have it there all the tiem?08:26
pittiev: I'm reading i-power source right now08:26
pittiev: but it seems that i-power is pretty tightly woven to g-s-d's power plugin; unfortunately it doesn't use upower directly08:27
evand actually, I'll just disable that code path for now, as we're not actually using ubiquity/online just yet08:27
pittiso, it's still unclear why the earlier g-s-d fails to set the theme08:27
pittiif I disable ubiquity-dm's g-s-d launching, I just have one, but it doesn't set the theme either, so it's not just a race between two gsd's08:28
seb128pitti, is there anything in .xsession-errors? the usual reason is "there is a xsettings manager already running"08:28
pittiseb128: partially; but see the bug trail08:28
seb128pitti, which is what we had in natty where the gdm g-s-d was not exiting before the session one starts for some users08:28
pittiseb128: /var/log/installer/dm doesn't have any messages about the g-s-d spawned by i-power08:28
pittipresumably becuase it's dbus activated, and thus its stdout/err isn't connected anywhere08:29
pittiwhich is a pity, as as it's a pain to see what's wrong with it08:29
seb128well, feel free to ping jjardon about indicator-power questions08:29
seb128he wrote it and he knows his stuff ;-)08:29
pittioh, yes08:29
seb128he's on #ubuntu-desktop08:30
pittiat the end of the day it seems to be a g-s-d problem, though08:30
pittithe one spawned by i-power should be able to set the theme as well08:30
pittiseb128: ^ or should it? does it need to be spawned by the session, or depend on environment variables?08:30
pitti.. like the session dbus, perhaps?08:31
pittiah, no, it's spawned _by_ the session dbus, so that's definitively there08:31
seb128pitti, I see no reason it should fail to set the theme08:31
seb128it's basically just reading the gsettings value and applying the xsettings08:31
pittiseb128: right; but it does08:32
pittiso I think that's the root of the bug08:32
seb128can you change g-s-d by a wrapper which call g-s-d 2>&1>/tmp/log or something?08:33
seb128to get the g-s-d output08:33
seb128bonus if you call it with --debug08:33
pittiseb128: nice idea08:33
seb128you might want to include the pid number of something in the log name if you have 2 g-s-d running08:34
pittiI just patch away ubiquity's g-s-d spawning08:34
* pitti has become pretty used to break=casper-bottom, hacking up the root fs, and then booting :)08:34
=== doko_ is now known as doko
pittiev: I love the "value set" window title of ubiquity :)08:41
evpitti: yeah, my most recent commit fixes that :)08:41
evyay copy and paste08:41
=== chrisccoulson_ is now known as chrisccoulson
pittiev, seb128: ah, see https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/854717/comments/1208:51
ubot4Launchpad bug 854717 in ubiquity (Ubuntu Oneiric) (and 3 other projects) "Broken panel icons and dialog style during ubiquity-dm and OEM install/final user configuration (affects: 2) (heat: 12)" [Critical,Confirmed]08:51
pittiseb128: so, it seems that g-s-d stays running, but doesn't do anything when it can't register?08:51
seb128seems like a bug, I would expect it to just exit08:52
pittiseb128: but even if we fix that, indicator-power would just fail08:56
seb128pitti, do we need indicator-power in the install mode?08:56
pittiso a longer-term fix would be either to make i-power use upower directly (currently discussing with jjardon)08:56
pittior to start g-s-d earlier than the panel in ubiquity-dm08:56
seb128I would go the g-s-d way08:57
pittiseb128: not crucial I think08:57
pittiseb128: but reading the g-s-d code it doesn't seem crucial that it registers; it should just go on08:57
seb128it doesn't make sense to make efforts to write unity desktop code without GNOME08:57
seb128i.e g-s-d is a basis desktop components nowadays we shouldn't try to fight to not have to use it, it's a waste of efforts08:58
pittiev: long story short, I think we can just disable libupower.so in panel.c for b2; does that sound ok to you?08:58
evpitti: works for me, will do now08:58
pittiseb128: I was mainly curious, as I don't think the g-s-d plugin provides anything that upower doesn't08:58
pittiseb128: and ubiquity-dm is a very case where we want the indicator without unity08:58
seb128right, just convenient apis it seems08:59
pittiseb128: I suspect that jjardon might have missed the existence of libupower-glib, though08:59
seb128pitti, well, without unity yes, but maybe g-s-d can be running08:59
pittiright, it should be running08:59
pitticf. the other solution I suggested08:59
pittistart g-s-d, then the panel08:59
seb128that would be my preferred solution09:00
seb128pitti, libupower-glib, maybe he missed it, but why is g-s-d duplicating that logic rather than using libupower-glib as well?09:00
evright, uploading a new ubiquity now09:00
seb128pitti, it's the same person who wrote upower, gpm and the gsd power code, there is probably a reason why it's done the current way ;-)09:01
pittiseb128: g-s-d does use libupower-glib09:01
seb128pitti, but anyway, not a topic for now and there, better to take that offline with jjardon09:01
seb128pitti, well jjardon said the g-s-d code to copy would be non trivial so I assume it's not only a few calls to libupower-glib09:01
pittiseb128: yeah, as I said this wasn't meant to be a blame or a bug, I was just curious why it's using g-s-d, as I didn't see a real reason to09:02
seb128pitti, should be let some of small applications in if we are going to respin?09:02
seb128things like eog, etc09:02
seb128or better to after beta2?09:02
pittiI let oneconf in, as this was small and focused09:03
pittibut now we have about zero margin for errors :/09:03
pittiseb128: if you have something in the queue which fixes a major bug and has a safe fix, that's fine09:03
seb128checking the queue09:03
seb128pitti, couchdb-glib would be nice09:04
seb128it fixes contacts syncing I think09:05
pittihm, no bug for this?09:05
pittiseb128: we won't respin alternates, BTW09:05
seb128is couchdb-glib on the CD?09:06
seb128no bug> hum, right, I just saw that rodrigo fixed it and chrisccoulson tested the fix yesterday09:06
pittiseb128: ah, seems not; so shoudl be fine09:06
* pitti accepts09:06
seb128pitti, everything else doesn't seem worth taking the risk09:07
seb128so better to delay the others to after beta209:07
pitti*nod* thanks for checking09:07
pittiev: seems the window title fix is not in that upload?09:07
pittiev: if that's intended it's fine, the upload looks good; just wondering whether there was something wrong with a commit09:10
cjwatsonslangasek: ack, when my brain is working well enough to understand openssl code, I'll take a look09:13
* pitti accepts ubiqity, to give it a chance to build before the next publisher09:14
evpitti: the window title fix is not setting self.custom_title to the return value of self.db.set09:20
pittiaah ;)09:21
=== s1aden is now known as sladen
ogra_pitti, when did you start the armel builds (my log has a time skew and i need to know when i need to look after downloading them)10:49
pittihey ogra_10:50
pittiogra_: at 07:23 UTC, i. e. 09:23 CEST10:50
ogra_thanks !10:50
pittiogra_: the first two builds are done, the second two are building10:50
ogra_so its anothe 3-4h10:50
ogra_its ~3h per arch10:50
pittiafter that I'll build server, then kubuntu10:50
pittiogra_: no, 1.5/2 h10:50
ogra_then someone did something to the buildd :)10:51
pittiogra_: well, the second pair could very well take longer :)10:51
ogra_it used to be 3h/flavour for two arches10:51
ogra_so i assumed twice the time for 4 arches :)10:51
ogra_indeed i'm happy if its faster ;)10:52
pittiogra_: yeah; what do we care if the builders sweat more now :)10:52
cjwatsonoh, whoops, I just accepted isdnutils and then realised it's in the ubuntustudio package set10:53
ogra_well, i would love to have builders in the cluster that we can just randomly assign in situations like milestones :)10:53
cjwatsonhopefully we can disregard that for image preparation purposes; it was a build fix10:53
pitticjwatson: also, we don't currently plan to rebuild it10:53
pittibut if ISDN stops working, nobody really should notice10:54
ScottKpitti: I'd like to get kdepim-runtime in even if we can't get it on some/all Kubuntu images since it fixes a data loss bug.  I'd appreciate if you would review/accept.11:09
pittiScottK: looks fine, accepted11:13
ScottKpitti: Thanks.11:13
pittiScottK: no worries, I can shuffle the build queue to build kubuntu a bit later, so that this has some time to publish11:13
pittiScottK: noted so on the pad11:14
pittiat last! ubiquity 2.7.3411:21
* pitti starts the build queue of doom11:21
pittijibel: so what was the thing with the "total failure" you mentinoed this morning with the alternate CD? the tracker seems have successes?11:41
pittimvo, jibel: FYI, I just re-enabled the upgrade tests; should work better now with cups11:43
pittiogra_: desktop builds on the buildds just finished, BTW; sycamore took 4:15 hours in total, annonaceae took 3:4011:49
jibelpitti, I re-ran all the tests both manually and automatically and it passed. I don't know what happened during the night, maybe an infrastructure or network  problem.11:56
jibelI'll retry upgrades.11:56
ogra_pitti, wow, thats a lot less than i expected (still way to long though, we will add more builds next release)11:56
* ogra_ waits for them to publish11:57
pittiogra_: they could be built on different builders perhaps?11:57
ogra_we have two builders and four subarches11:57
pittiogra_: will still take a bit, cron.daily-preinstalled is running11:57
ogra_we already share them between two machines, but i fezar we noeed more next release11:58
* ogra_ really doesnt want to hit 6h build times for one flavour 11:59
cjwatsonideally we need something that doesn't involve code on antimony having to explicitly select a builder12:10
cjwatsonI'd rather have something that dispatches to an idle builder if available and sends us a completion indication when it's done (which we would probably just block on)12:10
cjwatsonin some ways it would be easier if livefses were actual LP build jobs12:10
cjwatsonthat would be a big enough chunk of work to require escalation through LP stakeholders though12:11
pittiogra_: http://cdimage.ubuntu.com/daily-preinstalled/20110921/12:17
* ogra_ syncs12:17
pittiogra_: will we release mx5?12:17
pittiif so, we need a new product in the tracker, we only have imx51 (unless that's the same)12:18
ogra_pitti, well, that rebuild was only for mx5 :)12:18
ogra_i'll ask janimo, he owns mx512:18
ogra_i know we want to release it ...12:19
pittibuilding server and kubuntu preinstalled now12:19
pittihttp://cdimage.ubuntu.com/daily-live/20110921.1/ published for testing12:20
pittijibel: can we rename "Ubuntu Desktop armel+imx51" to "Ubuntu Desktop armel+mx5"?12:21
ogra_and there is janimo :)12:22
pittihello janimo, how are you?12:22
janimopitti, hi, should have the same type of testing as the omap flavours so wherever it fits in the iso tracker namespace12:22
pittijanimo: is imx51 == mx5?12:22
janimopitti, mx5 is a more generic name for a kernel (and eventually image)12:23
janimothat works with mx53 and the older mx51 too12:23
janimobut for now we only test on mx5312:23
pittiso I'll just add it as armel+imx51, and ask jibel to rename it in the DB12:23
janimopitti, what we test on now is imx5312:23
ogra_well, the arch name is mx512:24
janimoimx51 is an older subarch12:24
ogra_we usually use the subarch names12:24
pittijibel: right, but we only have an "armel+imx51" product; as I said, we ought to rename it in the db to match the image names12:24
ogra_yeah, that should be fine12:24
pittijanimo: thanks12:24
janimopitti, thanks for adding it :)12:24
ogra_janimo, you will need a tracker account btw (since you will liekly want to note down test results)12:24
janimoogra_, I knew there was a trap somewhere when you asked whether I want it to be on the tracker :)12:25
ogra_yeah, it was a diplomatic trick ;)12:25
ogra_but seriously, the person owning a subarch should indeed have a tracker account to note down test results :)12:26
janimoI did not intend to own it, just for it to be on the tracker. But yes, I'll get an account12:27
ogra_you should tell david :)12:27
ogra_i think he assume you own it12:27
janimowell my panda is fried, I guess I was bound to get closer to my MX5312:29
jibelpitti, I'd rather add a new product, it is a preinstalled image and test case is different from the former imx5112:29
pittijibel: ah, ok; do we already have defined test cases, or do we just copy the ones from ac100/omap?12:30
jibelogra_, is the testcase for mx5 http://testcases.qa.ubuntu.com/Install/ARM/PreinstalledImage like omap/ac100 ?12:32
ogra_its the same desktoip testcase for all desktop images12:33
ogra_(we dont build mx5 server or other images)12:33
pittijibel, janimo, ogra_: ok, I delete the imx51 image from the tracker then, don't get scared12:33
* ogra_ wont :)12:33
ScottKActually, AIUI our mx5 is mx53 only now, so calling it mx51 would be a mistake.12:40
jibeladded product ubuntu desktop mx5  and posted build 2011092112:42
pittijibel: cheers12:42
pittiinfinity, cjwatson, skaet: FYI, I just updated publish-image-set.py for the armel architecture list du jour, so please bzr update before you run this12:43
ScottKpitti: Would you please sync thaweb 3.0.12-1 from Debian non-free.  There's an upload in queue that doesn't have origin set correctly and so I'd rather get it done as a proper sync.12:43
pittiScottK: ack12:43
pittiScottK: did you already reject it?12:43
ScottKpitti: I did.12:44
* pitti can't see it12:44
pittiScottK: who requested it?12:44
ScottKJust a sec12:44
cjwatsonpitti: ta12:44
ScottK"أحمد المحمودي (Ahmed El-Mahmoudy)" <aelmahmoudy@sabily.org>12:45
cjwatsonstgraber: is POSTing to /qatracker/admin/addbuild (including hardcoding/scraping of milestone and testcase numbers) still the best way for a client script to post new builds to iso.qa?12:46
pittiScottK: done12:46
lamontcjwatson: mvo skaet: the current workaround for the archive slew is as follows:12:51
lamontwhen ftpmaster triggers syncproxy, the mirroring script now waits 25 minutes after it finishes syncing before removing the lockfile, blocking any subsequent trigger for 25 minutes beyond the ~ 20 minutes it takes for the script to run.12:52
lamontthis sucks, but it at least means that the triggered mirrors get a chance to get a consistent copy in their rsync12:53
lamontand gives us a little time to test and deploy something that will eliminate the slew entirely (COW is my friend)12:53
cjwatsoncould be worse, as workarounds go.  thanks12:55
lamontthat was kind of the thinking12:56
lamontbut it does mean that if you're doing rapid & manual publisher runs, you can get out your marker and scratch out "rapid"12:56
lamontsadly, this is all futurespeak, since the current run started before the change to the script12:58
cjwatsonYou say that as if the publisher is likely to finish inside 25 minutes anyway12:58
cjwatsonI suspect what went wrong here was manual mirror triggers to force out ca-certificates munging12:59
cjwatsonlamont: and I guess http://archive.ubuntu.com/ubuntu/pool/universe/d/diffutils/diff_2.8.1-18_all.deb being AWOL is another instance of this?13:02
lamontcjwatson: every instance will be one where there is a symlink between components13:04
lamontand any of them has a reasonable liklihood of being b0rked13:04
* cjwatson nods13:04
pittiah, I guess that mirror desync might be why the current live builds are failing? (hash sum mismatch)13:04
lamontpitti: verily13:10
lamontpitti: and at this point, I'm forecasting that it'll all be better about 40 minutes after the current (10 min old) publisher run finishes on cocoplum13:13
pittilamont: that sounds fine, thanks; I'll just run the cron.daily-live's then13:14
cjwatsonverily> have I mentioned a friend of mine's suggestion for fixing the problem that True/False Yes/No etc. don't line up in source code?13:16
cjwatsonwhich was to use VERILY and NOWISE13:16
cjwatsonand this has the bonus that it allows for tristates: VERILY NOWISE MAYHAP13:17
lamontcjwatson: LOL13:17
pittiand OHCRAP for error conditions13:18
cjwatsonnot quite in the right register, I feel :-)13:18
pitticjwatson: that must be from the FORTH age13:18
cjwatsonalthough I always liked dpkg's error function naming13:18
pittiheh, yes13:18
pittifortunately few people ever see this13:19
cjwatsonohshit for die-with-error-message; ohshite for die-with-error-message-and-errno13:20
pittihttp://cdimage.ubuntu.com/ubuntu-server/daily/20110921/ posted (including arm)13:21
pittiDaviey: ^ FYI13:21
lamontcjwatson: your last one violates your 6 character specification... maybe switch to latin?13:22
cjwatsonstgraber: oh, and do you think it's generally better to hardcode testcase numbers (e.g. 114) or testcase names (e.g. "Ubuntu Server EC2 EBS (Europe) amd64")?13:23
stgrabergood morning, sorry for being a bit late my ISP decided to change my IP and so I had to spend half an hour updating DNS/IPSEC/IPv6 so that I get something working again...13:27
stgrabercjwatson: testcase number shouldn't change as often as the name. Using /addbuild is currently the best way of doing it when you don't have access to limequat.canonical.com13:29
cjwatsonjust thinking of writing an autoposter for cdimage13:29
stgrabercjwatson: otherwise, I guess we could run a small service on limequat that pushes new entries directly in the DB (with a small internal only service)13:29
cjwatsonI guess that means hardcoding a load of testcase numbers in cdimage code?13:29
cjwatsonpresumably we should also have a role user for cdimage13:31
stgraberwhy do you need testcase number? don't you just need product number and milestone number?13:31
stgraberoh, nevermind just read the backscroll properly ;) you're indeed talking about product number (though as testcase number)13:32
stgraberso yeah, using the product number "Ubuntu Alternate amd64" should be safe and a lot more readable13:32
cjwatsonit's called "isota_case"13:33
stgraberthese don't change too often and when they do, they're usually different enough that you'd want to check your code anyway13:33
cjwatsonbut right, I mean products13:33
pittithey just changed a few hours ago, btw (imx51 -> mx5)13:33
pittiand we did some changes during beta-1, too13:33
pittipublish-image-set.py has quite some bzr history for these13:34
dokois heimdal on the images? or could it be approved? change to the -dev package only13:35
cjwatsonpitti: from cdimage's point of view, mx5 was already a different product from imx5113:36
cjwatsonand in that case, we got a new product number as well as a new product name, anyway13:37
cjwatsonso that's moot13:37
ogra_ev, http://paste.ubuntu.com/694452/ any idea ? is it because we dont have an oem user on armel ?13:40
ogra_(looks like it treis to query NM)13:41
stgrabercjwatson: http://paste.ubuntu.com/694453/13:41
stgrabercjwatson: I guess that's something I'd need to export whenever I get an API into that thing :)13:41
evogra_: already fixed in the new ubiquity13:41
ogra_then thats not in the current armel build13:41
pittiogra_: erk, you need ubiquity on the preinstalled ones?13:42
pittiogra_: sorry, then we need a respin13:42
pittiso far my mental model was "no ubiquity for preinstalled"13:42
ogra_pitti, yes, all preinstalled (including server) use oem-config13:43
ogra_which nowadays is ubiquity :)13:43
* ogra_ wonders who said we dont use it 13:43
pittithere were cases of ubiquity bugs where in previous releases we didn't need to rebuild the armels13:44
pittibut presumably because of bugs which didn't affect oem-config13:44
ogra_yeah, but thats just because they didnt affect arm13:44
ogra_or oem-config, right13:44
ogra_the fun is that i just got a success report from a user for the same image13:44
ogra_the error doesnt look like he could have gotten past it13:45
pittiogra_: it only crashes if you are offline13:45
pittiif you are connected to a network, it works13:45
pittiso it's quite possible13:45
ogra_well, given i have wlan and it crashes before i get even access to NM ...13:45
ogra_he might have a faster system (my rootfs goes to very slow USb media)13:45
pittiI disabled the ubuntu desktop armels in the tracker13:46
ogra_oh, i also noted that g-s-d got really really crashy on startup13:46
seb128use apport and send a bug13:46
seb128didn't get a g-s-d issue in weeks there13:46
ogra_it had to do several attempts while i saw the generic theme and icons13:46
ogra_eventually it started though13:46
pittiogra_: during oem-config, or the actual session?13:47
ogra_i dont have that on my upgraded oneiric install13:47
pittiogra_: during oem-config> that was fixed13:47
ogra_pitti, ubiquity-dm i think13:47
pittiogra_: yep, fixed in ubiquity .3413:47
ogra_ah, good13:47
ogra_so that last rebuild was kind of a waste of time :)13:47
ogra_well, jani will probably disagree, at least we got mx5 images13:48
jibelcjwatson, I already does the match here http://reports.qa.ubuntu.com/reports/isotesting/oneiric/report.html to track which image is ready for testing13:57
jibelmy problem was that limequat doesn't have access to people.canonical.com to discover which image is ready13:58
jibelbut if you can push a file to limequat with the flavor, buildnumber and name of the iso/image, it could be imported periodically and update the tracker.13:58
=== shadeslayer_ is now known as shadeslayer
utlemmingskaet: can we add the latest Oneiric daily build to tracker? http://uec-images.ubuntu.com/oneiric/20110921.1/14:08
skaetutlemming, ok, will do.14:10
utlemmingskaet: thank you kindly14:10
pittihey skaet14:11
skaetheya pitti14:14
skaethow go the builds?14:14
pittislowly :)14:14
pittiskaet: mirroring problems, and general slowness of arms14:15
pittiskaet: we had to do another ubiquity upload this morning14:15
skaetpitti, yup,  etherpad let me see that.14:15
* skaet wonders why the pad won't let me see it after 10pm *shrug*14:16
pittiskaet: builtin bedtime mode?14:16
skaetpitti,  meh,  fustration mode is more like it.   :P14:16
skaetah well.14:17
skaetpitti, so we have confirmation all the certificate issues have been resolved now?14:17
pittiskaet: ca-certificates? we have a fix in the archive, but nobody said yet "yes, it's fixed now"14:17
pittithat reminds me, someone else ran into that; didrocks, was that you?14:18
pittididrocks: libnss3 missing?14:18
cjwatson>>> import isotracker14:18
cjwatson>>> isotracker.product_code('Edubuntu DVD amd64')14:18
cjwatson>>> isotracker.product_code('Edubuntu DVD i386')14:18
cjwatsongetting there14:18
didrockspitti: indeed, just had it14:18
pittididrocks: which versino of ca-certificates{,-java} did you upgrade from and to?14:19
didrockspitti: let me see what version I had before rebooting14:19
stgrabercjwatson: cool! once I've got some time to work on the tracker and get some kind of API implemented it should be quite trivial to just update that python module then14:19
skaetstgraber, cjwatson.  :D  excellent news.14:20
stgrabercjwatson: if you want a role account for cdimage, just register one on the tracker and let me know the username so I can make it an admin14:20
didrockspitti: so I booted successfully this morning (nss3 there). Then upgraded ca-certificates:i386 (20110502+nmu1, 20110502+nmu1ubuntu3) and ca-certificates-java:i386 (20110912ubuntu1, 20110912ubuntu2). After rebooting, no nss314:21
pittididrocks: right, fix went into -java 20110912ubuntu314:21
skaetutlemming, http://uec-images.ubuntu.com/oneiric/20110921/ shows log.stdout.stderr - where do you want me refreshing the tracker from?14:21
didrockspitti: yeah, I updated it before rebooting in fact: ca-certificates-java:i386 (20110912ubuntu2, 20110912ubuntu3)14:22
didrockspitti: but I guess the file was already removed14:22
pittiif you install ubuntu2, you are doomed, I'm afraid14:22
didrocksso can't really confirm the fix14:22
didrockscan try downgrading14:22
pittididrocks: you could downgrade to the old version14:22
didrocksdoing then14:22
pittithen install nss3, and upgrade again?14:22
didrocksdowngrading ca-certificates-java to 20110912ubuntu1, isn't it?14:23
didrocksthen reboot, then upgrade to 20110912ubuntu314:23
didrocksandd check the file14:23
pittishouldn't really need a reboot14:23
pittijust reinstall of nss314:23
utlemmingskaet: http://uec-images.ubuntu.com/oneiric/20110921.1/  -- you're missing the .114:23
didrockspitti: reinstalled is already done, otherwise, I won't be online :)14:23
skaetutlemming,  thanks!14:24
utlemmingskaet: :)14:25
cjwatsonis it just me or is iso.qa refusing connections right now?14:26
stgrabercjwatson: works here14:26
pittioh, look! mirrors work again, ubuntu DVD built14:27
pitti^ lamont :)14:27
* pitti builds the other missing live images then14:27
didrockspitti: works here, still have the file after the upgrade14:27
* didrocks updates the bug14:27
lamontpitti: cool14:27
cjwatsonworks now for me, must have been transient14:28
Davieycjwatson: it was done for a period, along with all the other sites on the box14:28
skaetutlemming, ok should be published.14:29
pittihttp://cdimage.ubuntu.com/dvd/20110921/ posted14:30
jamespageare there current/outstanding issues with archive mirrors?  I'm seeing 403 errors on all ec2 regions during litmus testing prior to testing 20110921.114:31
Daviey403?!  That is unrelated to the other issues,  i believe14:32
DavieyI suspect the ec2 mirrors are just broken.14:33
cjwatsonDaviey: same thing I believe; alternates between 404 and 40314:34
cjwatsonjamespage: I think this is what lamont has been working on14:34
jamespagecjwatson: OK - I'll hold off the full test and can re-run the litmus test as and when required to validate its good14:34
Davieycjwatson: ah, ok.14:35
lamontjamespage: I'm going to guess you don't want to wait up to 3 hours for that,right?14:37
jamespagelamont: not really14:37
jamespagethe full test run takes another 1.5 hours after tha14:37
jamespageso if we can get it fixed now that would be great14:37
pittiogra_: staring new ubuntu preinstalled build14:38
pitti"starting", too14:38
lamontjamespage: triggered all 5 regions.  they'll come current sometimeish14:39
jamespagelamont: thankyou14:40
pittihttp://cdimage.ubuntu.com/xubuntu/daily-live/20110921.2/ posted14:52
charlie-tcaThank you14:52
pittihttp://cdimage.ubuntu.com/mythbuntu/daily-live/20110921.1/ posted14:54
pittihttp://cdimage.ubuntu.com/lubuntu/daily-live/20110921.1/ posted14:56
cjwatsonis there a product I could harmlessly post something to on iso.qa for testing?14:56
pitticjwatson: ubuntu netbook perhaps?14:56
cjwatsonanyone object to that?15:01
cjwatsonI guess it might cause some spurious mails; I'd like something nobody is subscribed to15:01
pitticjwatson: Netboot arm imx51 perhaps?15:02
cjwatsonstgraber: is anyone subscribed to ^- that?15:03
stgrabercjwatson: checking15:03
GrueMasterProbably me.  Filters activated.  Fire at will.15:03
pittihttp://cdimage.ubuntu.com/kubuntu/daily-preinstalled/20110921/ posted15:05
pittinice, after hours of waiting they now come in in hordes15:05
jpdsPoor will.15:05
stgrabercjwatson: two users are subscribed, checking who they are15:06
stgrabercjwatson: GrueMaster and plars15:06
cjwatsonok, I guess they can both cope15:06
GrueMasterplars likes mail.  Have fun.15:07
cjwatsonGrueMaster: can you let plars know to ignore this?15:07
cjwatsonexcellent, that worked15:07
cjwatson$ ./post-image-to-iso-tracker.py 'Ubuntu Netbook armel+imx51' 2011092115:07
GrueMasteryes, I'll ping him.  Or can you just unsubscribe him?15:07
cjwatsonI already posted and have removed it agan15:07
cjwatsoncommitted to ubuntu-archive-tools; hopefully I haven't broken post-amis-to-iso-tracker.py15:09
stgrabercjwatson: yeah!15:11
pittihttp://cdimage.ubuntu.com/kubuntu/daily-live/20110921.1/ posted15:11
cjwatsonskaet: do you want to specify exactly when cdimage should auto-post images to the tracker?  you suggested that it should post an image that was marked rebuilding, but I wonder if perhaps we should be posting anything during certain time periods, or something like that15:12
skaet cjwatson,  yeah, we should probably all come up with some heuristics.   certainly when the iso-tracker is primed for a release (ie. switched over to beta 2 from beta 1),  might be part of the heuristic15:13
skaetI figured it it was marked for rebuild it was obvious something was expected, and a change was expected.15:14
skaetOne thing I'm worrying about is an image gets built and "stomps" on something that wasn't expected to be updated.15:14
cjwatsonmm, cdimage doesn't really know whether isotracker's default release is an imminent one or not15:14
cjwatsonexperimental builds15:15
skaetindeed.   maybe just keeping it when the tracker is expecting a build for now?   Then work on some heuristics together either on list, or at UDS?15:15
cjwatsonmaybe just a CDIMAGE_POST_QA environmenet variable?15:15
skaetthat could be an option too.15:15
cjwatsonif you set to non-empty, the image gets auto-postd15:15
cjwatsonsince all of these builds are getting done manually anyway15:16
cjwatsonyou have to remember to unset it at the end of a build pass15:16
skaetyeah, that could work.   remembering to unset it though could be triggered by the release being done?15:17
cjwatsoncan't see how that could unset environment variables in people's shells :-)15:18
skaetah yeah, I was thinking it might be something on cdimage - but that's not what is happening today. :)15:19
GrueMasterWhat is the status of armel rebuilds?  I heard earlier that we were respinning (yet again) due to oem-config issues?15:29
pittiGrueMaster: it's running15:29
pittiGrueMaster: kubuntu and server are already up to date and in the tracker15:30
GrueMasterok.  kubuntu is low on my list, but will pull separately for testing.15:30
pittiGrueMaster: pad and tracker are both up to date15:30
cjwatsonphew.  are we still going?15:35
cjwatsonoh, blast, echan15:37
pitticjwatson: we are still going as well, anyway :)15:37
pittiskaet, infinity: as noted on the pad, kubuntu DVD, edubuntu DVD, and ubuntu preinstalled images are currently building, the rest is built/published15:38
pittino known blockers/breakage15:38
pittiskaet, infinity: can I hand over the baton back to you? I'd like to go to Taekwondo this evening15:39
pittialready skipped on Monday, and I can really use some exercise, I think :)15:39
skaetpitti,  thanks.   yes,  baton accepted.  :)15:39
pittiskaet: can you add the images to the tracker as they come in? kubuntu ETA 10 mins, edubuntu ETA 30 mins, ubuntu preinst ETA 3 h15:39
skaetpitti, sure will do.15:40
skaetpitti,  by the way,  the latest updates seem to resolve most of the crashes I was seeing yesterday.  \o/15:40
pittithanks; good night everyone!15:40
pittiskaet: nice15:40
* skaet reinstalling natty now, and trying to do upgrade from there. 15:40
pittiskaet: oh, kubuntu DVD just coming in, adding15:41
pittiinfinity: will you do the pre-publishing later today, when some u/k desktop images testing results?15:41
* pitti waves15:42
* skaet waves back to pitti15:49
infinitypitti: Been a while since I did that, but I'm sure I can dust off the skills.15:54
cjwatsonare there any install-from-USB test reports on the tracker?15:56
jamespagelamont, all regions aside from us-east-1 now look OK15:57
* lamont takes a quick peek16:00
charlie-tcaSo, after all that time, software center did not get the fix for Xubuntu. It is unusable by Xubuntu users in Oneiric.16:05
cjwatsonmvo: ^-16:07
cjwatsonurgh, bits of iso.qa are painful to screen-scrape16:08
cjwatsonlike the front page16:09
infinitycharlie-tca: What's wrong with it in Xubuntu?  Not that I use SC, but starting it up, it seems fine...16:09
infinity(Other than being unthemed because it's GTK3, and I'm using a GTK2-only theme...)16:10
charlie-tcain a fresh install with the latest images, it crashes16:10
mvocharlie-tca: its waiting in the queue16:10
charlie-tcaIt will not start16:10
infinityWeird.  I wonder why it works here.16:10
charlie-tcamvo: I know16:10
charlie-tcabut I would have thought after waiting all night for images, we might have gotten it in16:10
charlie-tcainfinity: it will not start at all, 32bit and 64bit installs on hardware16:12
skaetmvo,  is that what's fixed by the new update-manager that's just gone on the queue?16:13
mvoskaet: u-m is a different fix, its not urgent (at all)16:14
skaetmvo,  thanks.16:15
infinityskaet: This is software-centre we're talking about.16:15
infinityI wish someone had told me how broken it was yesterday, I would have pushed it through before the last world rebuild. :/16:16
charlie-tcaThe best I could suggest now is updates, since I am running out of hours already to get things tested.16:17
skaetinfinity:  gotcha.16:17
charlie-tcaI have to plan 6-8 hours for all the images16:17
infinitycharlie-tca: Updates?16:18
charlie-tcayeah, sudo apt-get dist-upgrade right after installing?16:18
infinityOh, yeah.16:18
infinityI thought you meant "oneiric-updates", and I was about to point out that this is a beta, not final. :P16:18
charlie-tcasorry, bad wording16:19
infinityBut yes, SC broken on Xubuntu probably isn't the end of the world for a beta, just unfortunate.16:19
infinityAnd not install-path-critical, so yes, updating tomorrow would fix it.16:19
charlie-tcaI agree, and we still include Synaptic Package Manager by default, too.16:19
utlemmingAutomated testing for cloud-images is currently blocked due to EC2 mirrors in US-East being out. IS will be looking at that shortly.16:24
skaetScottK,  kubuntu dvd posted16:27
jamespageutlemming: just testing again now16:41
jamespageutlemming: https://jenkins.qa.ubuntu.com/job/oneiric-server-ec2-adhoc/ looking OK now16:41
jamespagewill kick off the full run16:41
skaetmvo, jibel - fresh update from natty is stumbling into crash on update.  Can anyone else confirm?16:50
skaet(issue is gnome-settings-daemon crashed with SIGSEGV in g_simple_asynch_result_complete())16:51
charlie-tcaconfirmed on Xubuntu, bug 83260316:53
ubot4Launchpad bug 832603 in gnome-settings-daemon (Ubuntu Oneiric) (and 2 other projects) "gnome-settings-daemon crashed with SIGSEGV in g_simple_async_result_complete() (affects: 601) (dups: 75) (heat: 2762)" [High,Triaged] https://launchpad.net/bugs/83260316:53
jibelskaet, bug 83260316:53
jibelskaet, excuse my slow brain. charlie-tca was faster16:54
utlemmingjamespage: thanks for kickign testing again16:54
jamespageutlemming, np16:54
skaetjibel, charlie-tca - thanks.16:54
jamespageif we see specific issues with mirrors we can always re-run tests individually16:55
skaetjibel, charlie-tca - have marked mine as a duplicate of that one then.16:59
cjwatsonI have a cdimage patch to do iso.qa posting based on an environment variable, but I guess I should hold off until after beta-217:00
cjwatsonbesides, pretty much EOD now anyway17:01
skaetstgraber,  edubuntu dvd posted17:35
* stgraber startings zsyncing17:36
ScottKAre the current Kubuntu desktop/alternates ones we want testing on?17:40
highvoltagestgraber: I've been meaning to ask, when you removed some of those gnome admin packages, did you remove the slides too or are they still there?17:40
ScottKIt looks like desktop is current.17:42
cjwatsonskaet: oh, hmm, when rebuilding an image whose hash matches something on the iso.qa list it would probably be helpful to automatically mark it as rebuilding, right?17:45
cjwatsonwell, if we're going to post a new one anyway17:45
skaetcjwatson,  yeah that would be very helpful indeed.17:45
stgraberhighvoltage: removed the slides too17:46
highvoltageah great17:49
ScottKskaet: Is there any image building going on right now?18:14
infinityAll I see building is some arm preinstalled images.  But I'm not sure what others have been up to.18:15
ScottKev: Bug #855763 looks like it's exploding almost exactly where you changed stuff in the last upload.  Ideas?18:19
ubot4Launchpad bug 855763 in ubiquity (Ubuntu) "installer crashed (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/85576318:19
evScottK: just fixed on trunk.  Apols for that.  I did test the KDE frontend stuff, so I'm baffled as to how that slipped through.18:23
ScottKev: OK.  I just confirmed it.18:24
ScottKI guess we'll need an upload and respins for it.18:24
* GrueMaster hears the word "respins" and cringes. No armel desktop testing has happened since Beta 1.18:25
ScottKskaet: ^^^ That's a blocker.18:25
ScottKGrueMaster: You don't use Ubiquity do you?18:25
GrueMasterWhich is part of ubiquity.18:26
GrueMasterAnd I'm still waiting on the last desktop respin to finish.18:26
skaetScottK, ack.18:27
ScottKskaet: While we're waiting for that, Kubuntu alternate respins would be nice to pick up the kdepim data loss fix if there's builders available.18:27
skaetev, can we live with just respinning the Kubuntu images?18:28
GrueMasterGuess I can do a netboot install and start testing from that.18:28
skaetScottK,  ok, will kick it off now.18:28
skaetScottK,  just to double check which package version should the data loss fix be in?18:31
ScottKskaet: 4:4.7.1-0ubuntu3.18:31
ScottKI checked and it's already on the dvd/desktop images (not that that helps)18:31
skaetScottK,  ok, its kicked off.   Will look for it in about 30 minutes.18:36
slangasekGrueMaster: if it's a matter of you being blocked on doing any smoke testing of ARM images, we can certainly make sure that we get some images out for you to test even if we know they won't be final for beta-2; would that help?18:44
slangasek(I believe ubiquity is currently in a consistent state in the archive, so we shouldn't have to worry about that breaking the actual image building)18:44
GrueMasterslangasek: There are images being built now.  It just takes several hours between respins.18:45
GrueMasterAnd as I said, worst case I do a netboot install and revert to app testing.18:45
skaetGrueMaster, per pitti's estimate,  the images should be emerging from the builder shortly.   Will flag you directly as soon as I spot them.18:47
GrueMasterThanks skaet.18:48
skaetScottK,  kbuntu alternates (20110921) posted.19:11
* skaet drums fingers waiting for arm builders....19:12
micahgskaet: am I ok to upload some mozilla builds now to the security PPA?19:14
skaetmicahg, as long as they can be killed off if testing throws up a blocker.19:17
skaetesp on the arm side.19:17
micahgskaet: yep, no problem (don't need the arm/powerpc until next tuesday)19:17
micahgthe others are fine to kill as well if needed19:18
skaetmicahg, ok.19:18
micahgthese are still <1hr except on armel though, I'm still waiting on the firefox 7 builds and will check in again before uploading those (4.5hr+ on every arch)19:19
ScottKThe armel rebuild test is done, so getting armel builders should be less of an issue than it has been recently.19:20
micahgyeah, half of them are free ATM19:21
infinityGrueMaster: I see some new daily-preinstalled images.19:29
infinityGrueMaster: Yeah, all 4 look there.19:30
GrueMasterok.  Pulling.  Hope the bandwidth is decent this time.  Last pull took 4 hours.19:31
infinityskaet / slangasek : Are we headed into another respin cycle here soon?  Looks like ARM's previous run is all done, so we have stuff to smoketest.19:31
skaetinfinity,  GrueMaster - just posted the latest images fresh off the ARM builders to the iso tracker.19:32
infinityOh, looks like we still need a new ubiquity?19:32
slangaseksounds like it19:33
slangasekev: you said the kubuntu fix is on trunk? Are you preparing an upload today?19:33
infinityIn that case, can we pull in software-center to make Xubuntu happy? :P19:33
slangaseksounds appropriate to me19:33
skaetinfinity, we can pull in software-center.   Just not sure if charlie-tca will have bandwith to test the updated image.19:34
infinityzsync is a beautiful thing.19:34
infinityWell, when it works.19:34
GrueMasterI'm still wondering what the last respin was about.  I have the 20110921 desktop running on panda and while there are visual glitches, it is running smoothly.19:34
skaetre: ubiquity,  can it just be a kubuntu spin,  or is there a need for all the images.   It wasn't clear to me.19:34
stgraberisn't the new ubiquity a kde-only fix?19:34
infinityGrueMaster: Sanity respin, since ubiquity keeps getting revved, probably.19:35
skaetstgraber,  that was my understanding.19:35
infinityAnd an LP timeout.  Twice.19:35
* infinity goes to accept the old fashioned way.19:36
slangasekhmm, was ubiquity in the queue already? I didn't see it19:37
infinitycharlie-tca: software-center accepted, BTW.  Xubuntu respins, yay?19:37
infinityslangasek: No.19:37
skaetslangasek,  ev:  please post scope of respin when its known.   My preference is to just redo Kubuntu unless compelling reason otherwise.19:37
stgraberskaet: there's also a fix for bug 848000 in the branch but I wouldn't think it's worth rebuilding for that19:37
ubot4Launchpad bug 848000 in ubiquity (Ubuntu) "Shouldn't show "should be plugged in" when on a desktop (affects: 1) (heat: 6)" [Low,Fix committed] https://launchpad.net/bugs/84800019:37
slangasekinfinity: so it's the software-center that you accepted?19:37
infinityslangasek: Yeah.19:37
* skaet looking19:37
stgraberskaet: so current ubiquity trunk contains: bugfix for bug 848000 and bug 855763 + a new unit test19:38
ubot4Launchpad bug 855763 in ubiquity (Ubuntu Oneiric) (and 1 other project) "installer crashed (affects: 2) (heat: 10)" [Critical,Confirmed] https://launchpad.net/bugs/85576319:38
infinitycharlie-tca: Your o is missing the \/ around it.  Armless man cheering?19:38
charlie-tcaI would go with skaet on this19:38
infinitycharlie-tca: Oh, as in you don't have time to test the fix you wanted? ;)19:39
charlie-tcaIf we need to respin, gereat119:39
charlie-tcaif not, I would wait19:39
infinitycharlie-tca: We're respinning some/all anyway for ubiquity.19:39
infinitycharlie-tca: So... You get software-center. :P19:39
charlie-tcago for it, then19:39
skaetcharlie-tca,  :)19:39
slangasekskaet: the usual compelling reason is to have consistency between the images and the archive at the point of the milestone; I also see a fix for bug #848000 on trunk, which benefits Ubuntu but isn't a major issue.  The fix for bug #855763 definitely only affects KDE.19:39
ubot4Launchpad bug 848000 in ubiquity (Ubuntu) "Shouldn't show "should be plugged in" when on a desktop (affects: 1) (heat: 6)" [Low,Fix committed] https://launchpad.net/bugs/84800019:39
ubot4Launchpad bug 855763 in ubiquity (Ubuntu Oneiric) (and 1 other project) "installer crashed (affects: 2) (heat: 10)" [Critical,Confirmed] https://launchpad.net/bugs/85576319:39
infinityslangasek: I'm pretty anal about the consistency thing, but I'll concede that since we don't snapshot the archive for pre-release milestones, it's not like it actually matters either.19:40
slangasekskaet: if we're pressed for time on testing and don't want to respin the world, kubuntu-only respins are viable here19:40
infinityWell, I may have just committed to Xubuntu too. ;)19:41
skaetslangasek,  ok will definitely mark down kubuntu and xubuntu for respin when the ubiquity lands.   I'd like to get a read from jibel on testing impact before those get posted.19:41
slangasekinfinity: right; it's annoying to not be able to use jigdo for milestone alternates, but the window when you can do that is diminishingly small anyway19:41
infinityslangasek: Well, it's also good practice for "real" releases.  Saying "we don't have time to test X again, so let's no refresh the image" is not the right answer. :P19:41
Davieypeople use jigdo?19:42
skaetre: read from jibel, is whether he has bandwidth to do a retest on ubuntu images in time as well.   Will build them after kubuntu and xubuntu, and then hold off on posting.19:42
infinityDaviey: With a local mirror, it's insanely nice.19:42
Davieyinfinity: with a *local* mirror, wget should be pretty damn fast :)19:42
stgraberskaet, slangasek: want me to upload the current ubiquity? not sure if ev is still around19:43
infinityDaviey: Well, yes.  Hence why jigdo's awesome.  (As in, I keep a local package mirror, but not ISOs)19:43
charlie-tcaI only have one desktop test done anyway19:43
slangasekDaviey: a local package mirror doesn't making wget'ing of images fast19:43
slangasekstgraber: yes please19:43
Davieyoh. i thought infinity was talking about a local iso mirror.19:43
infinityDaviey: Local ISO mirroring is just insanity unless you're a QA dude who tests every day.  *glances at GrueMaster*19:44
skaetstgraber,  what slangasek said.  and thanks!19:45
Davieyinfinity: Last cycle, i did rsync the server iso's daily.. but not bothered this cycle.19:45
stgraberubiquity uploaded. Generating the debdiff locally shows a change in d-i/source/tzsetup/debian/common.templates (included source package), wiped my local copy of d-i/source/ and re-updated it and it's still there, so I guess that was a problem in a previous upload20:04
skaetstgraber,  thanks.   slangasek, can you review?20:15
slangasekdo we want the one from 6 minutes ago or the one from 11 minutes ago?20:16
skaetstgraber, ^^20:17
infinityThe one with .gitignore vomit all over it seems suspect.20:18
infinityAnd yet, that's the newer one. :)20:18
infinityslangasek: gitignore aside, without a response from stgraber, I'd be inclined to take the newer one, since it only addresses the bugs and doesn't randomly regen/change a debconf template.20:21
* stgraber goes to look at the queue20:22
stgraberhmm, weird, I didn't see evan's upload in the branch20:23
slangasekit wasn't there when you uploaded... his is the newer upload20:24
stgraberI think it'd be best to go with my upload so that it matches what's in the branch20:24
slangasekstgraber: hmm, I've just accepted ev's because as infinity says, random changes to debconf templates are troubling20:25
slangasekespecially unreviewable ones like changes to a 2000-item list20:25
stgraberstgraber@arkose-tmpW3TJ50:~/data/code/ubiquity$ md5sum current-tz/tzsetup-0.26ubuntu10/debian/common.templates ubiquity/d-i/source/tzsetup/debian/common.templates tmp/ubiquity-2.7.34/d-i/source/tzsetup/debian/common.templates20:28
stgraber533f96595d0e372bf970dce026f5add8  current-tz/tzsetup-0.26ubuntu10/debian/common.templates20:28
stgraber533f96595d0e372bf970dce026f5add8  ubiquity/d-i/source/tzsetup/debian/common.templates20:28
stgraber2b607e6faffa4794d6aa284435a32822  tmp/ubiquity-2.7.34/d-i/source/tzsetup/debian/common.templates20:29
stgraberfirst one is the md5 of that debconf template from tzsetup itself, second is the ubiquity on my system (the one I uploaded earlier), third is the one in the last ubiquity upload (evan's system)20:29
stgrabernot sure if there's any potential impact, but "mine" seems to be the right one20:29
slangasekstgraber: well... too late to un-accept :/  could you fix up the branches so that it gets properly imported on the next upload?20:31
infinitySo, speaking of not respinning for package consistency.20:34
stgraberthe included sources aren't in the branch but on the uploader's system (you basically need to run "fakeroot debian/rules update" to get them, then run debuild -S -sa to build the source package).20:34
infinityWho feels good about a no-change rebuild upload of nss, just to force updates on poeple who lost their libraries?20:34
infinityskaet / slangasek ^20:36
stgraberev: ^ (apparently you've got something weird in d-i/source)20:36
skaetinfinity, am not sure about the implications of that.   what is scope of rebuild needed?20:36
infinityskaet: Well, if we don't care deeply about the images and the archive having identical package versions, it means little to beta, really.20:38
infinityskaet: But the version rev will force an update on people who had their libnss3 library deleted by ca-certificates yesterday, without them having to hunt for support, manually download a package, etc.20:38
micahgI'd actually like to update nss before final, but was going to bring that up after release tomorrow20:38
infinitymicahg: Well, there still seems to be a bit of a support panic with people who have no idea WTF has gone wrong.  A quick version bump would kill a lot of that.20:40
slangasekinfinity: if there's enough noise about it to be on your radar, I think a no-change rebuild of it would be best20:40
micahginfinity: yeah, I'm ok with that, was just thinking out loud, sounds like a no change rebuild wouldn't be so bad(it's pretty fast too)20:41
infinityYeah, it's speedy.20:41
skaetinfinity, ok by me then.20:41
infinityI'll just bump it now.20:41
jbichaI think it breaks network-manager so people might have to chroot anyway or use a wired connection but it seemed better to tell people to upgrade than to go find a .deb to install20:41
slangasekjbicha: the point is to get it to the archive so that it fixes itself for users who haven't already rebooted20:41
jbichaslangasek: yes :)20:42
charlie-tcaskaet: release overview updated for Xubuntu20:44
skaetthanks charlie-tca20:44
* infinity daringly accepts his own upload.20:47
* Daviey watches the world implode.20:48
stgraberwow, I didn't remember the qatracker module being such a mess ;) spent the last 30 minutes porting it from the current Drupal 4/5-ish code over to Drupal 7 and it finally loads though will need all of the DB interaction rewritten21:02
stgraberconsidering how easy it's to write a Drupal 7 module, I might just as well rewrite it, keeping the DB as it's (that part was easy to port)21:02
skaetScottK,  do you want the Kubuntu ARM images rebuilt?21:09
skaetokie,  just checking.21:09
ScottKI doubt anyone is using kmail on armel and I'm sure GrueMaster has enough testing to do already without me adding to his trouble.21:10
* GrueMaster twitches.21:13
dokoskaet, would you mind, if I set the milestone 11.10 for ftbfs issue for packages in universe which are in package sets? (5 packages)21:26
skaetdoko, for 5 packages, sure21:26
lamontskaet: slangasek: so about this publisher thang...  I'm trying to understand why, if we publish hourly, we get publisher triggers for archive on syncproxy every 30 minutes21:29
lamontand more to the point, I'd like to see that timeframe doubled for at least a little while21:29
slangaseklamont: ask the LP folks?21:29
slangaseklamont: it's really "every 30 minutes", not "twice back-to-back in a publisher run"?21:30
lamontit's one crontab entry that triggers at 03 * * * *21:31
lamontso yeah, I'll go ask the lp folks21:32
slangasekDaviey: hmm, you guys opted not to do the FFe for qemu-kvm?  I guess that means I'm on my own for sorting out qemu-linaro then? :)21:32
lamontthe issue right now is that every other sync request causes ZOMG email to all of us and gets dropped on the floor... so... yeah21:32
slangaseklamont: yeah, we don't exactly control the contents of that cronjob21:33
slangasekas in, I can't even work out where the actual code for the cronjob is without hurting my brane21:34
skaetlamont, any options for improving this part of the cycle would be very welcome.21:36
slangaseklamont: well, I take that back.  looking at publish_ftpmaster.py, I do see that we're calling runFinalizeParts() twice, once for the "quick" security sync and once for the full-distro sync.  The first one should be a very small sync; is the problem we're having that it isn't?21:37
slangaseklamont: should /srv/launchpad.net/codelines/current/cronscripts/publishing/distro-parts/ubuntu/finalize.d/90-trigger-mirrors have different handling based on SECURITY_UPLOAD_ONLY?21:38
slangasek(if so, what should the difference be?)21:38
slangasek^^ makes gtalk plugin work on amd6421:45
skaetstgraber, do you want edubuntu added to the respin list?21:47
stgraberskaet: yeah, still have plenty of time to re-test, so let's be up to date!21:49
skaetstgraber, ok, adding in.21:50
skaetanyone else what the latest ubiquity?21:50
infinitylamont: That's two triggers from the same script.  I'm sure I've answered this before...21:51
infinitylamont: And it's been like that for years.21:51
infinityslangasek: Making it not trigger on sec_up_only sort of defeats the entire purpose of the quick-turnaround security run. :)21:53
slangasekinfinity: unless the mirrors lamont is having problems from are not the mirrors used for mirroring security?21:53
infinityslangasek: Well, everything passes through syncproxy.21:55
infinityslangasek: And I have a sneaking suspicion that's where the angry mails are coming from.21:55
slangasekinfinity: does it?  There are three mirrors being triggered in that script21:56
slangasekI don't know which machine does what, but there's clearly more than one21:56
infinityEverything public-facing passes through syncproxy? :)21:56
* skaet waiting on built ubiquity 2.7.35 to show up on archive now.... speaking of mirrors. 21:59
infinityEverything but armel should be fine.22:00
skaetbuilds started for all except armel.   see pad for details.22:17
skaetthanks infinity22:17
infinityskaet: Just desktop CDs, I hope?22:22
infinityskaet: (Well, if you were basing it on ftpmaster having the files you wanted)22:22
skaetinfinity, yes, just desktop cd/dvds (see pad).   waiting on armel.22:23
infinityOh, did I miss the memo on DVDs no longer being live/alternate hybrids?22:23
infinity(Let me guess, that changed 3 years ago, and I wasn't paying attention)22:23
slangasekit changed this cycle22:23
lamontslangasek: its archive and security mirrors that are affected by the issue22:24
slangaseklamont: ok, well, see infinity's comments... the double-pulse per hour is expected then due to the security "quick-run".  If that's not actually serving the intended function, it's easy enough for LP to disable the extra pulse and just do it all in one go...22:25
slangaseksee also the discussion elsechan of whether there's cruft on the filesystem that needs cleaning up22:25
infinitylamont: Yeah.  We can disable the quick sec run.  Though there was a valid reason for it (not wanting to have to wait 45 minutes to push out something that's actually critical)22:26
slangasekhowever, if overlapping runs means you're usually waiting 1h15 instead, there's a clear lesser evil22:26
infinitylamont: There's also the part where IS has been laughing at LP for 6+ years about the publisher being so slow that it can't run twice an hour like dinstall did.  Might not want to lose face there. ;)22:26
infinity(no pressure)22:27
lamontslangasek: having LP disable it for the rest of oneiric would probably be best22:56
* lamont must run for a while22:57
skaetScottK, kubuntu daily-live  20110921.2 posted23:17
skaetcharlie-tca, xubuntu desktop (20110921.2) posted23:31
charlie-tcaskaet: that was there hours ago, already23:36
charlie-tcaIt was posted when infinity called for the respin23:36
stgrabercharlie-tca: 21.3 just got appeared23:37
charlie-tcaThat's what I was looking for23:38
charlie-tcaThank you both, it is getting complicated now23:38
stgrabercharlie-tca: I guess you want 20110921.3 on the tracker right?23:39
charlie-tcayes, I think so. That's the one we were waiting for23:39
stgraberok, added23:39
charlie-tcathank you23:40
stgraberskaet: updated TechnicalOverview. I'll ask highvoltage to check I didn't forget anything.23:47
ScottLskaet, i'll get the technical overview tonight, i promise ;)23:50
skaetThanks stgraber,  ScottL.  :)23:51
skaetcharlie-tca,  sorry 21.3 is what I was looking at and then posted 21.2.   Thanks for fixing stgraber!23:53
* skaet figures its time got go get some dinner...23:54

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