=== ysnoi is now known as TheYsNoi
Riddellwhat does "Run Once" mean for test cases on iso.qa.u.c?01:08
slangasekRiddell: that the test case needs to be done once for all images, instead of once per image01:35
cjwatson[5~/wg 4401:44
GrueMasterOne more image to test and I can hit the pub.02:35
micahgslangasek: I assume disabling the publisher for hours at a time before alpha2 is released would be a bad thing?06:11
pittimicahg: is "hours" more like two or 12?06:57
pittimicahg: two hours sohuld be bearable if it's urgent06:57
pittibut not much more06:57
micahgpitti: 2-3 per release (this is for the Firefox migration to -security)06:58
micahgreleases == lucid,maverick06:58
pittiwow, copying packages takes that long?06:58
micahgyeah, I think it took 3 hrs per release from -proposed to -updates06:59
pittiI think that mostly was because jdstrand used copy-package.py for the gazillion langpacks, wasn't it?06:59
micahgis that not the right way?06:59
pittiit works, but is utterly slow06:59
pittiusing our sru-release --pattern lucid --security language-pack script, it's a matter of 15 minutes or so07:00
micahgpitti: ah, could you please document that on the archive admin page, that's what we were trying to use07:00
* micahg probably won't be ready until after release in any event though07:01
pittiurgh yes, that is a bit obsolete07:01
pittialso https://wiki.ubuntu.com/ArchiveAdministration#Standard_case07:02
pittiwill update07:02
micahgok, so, it should be <30 minutes per release then, perfect, if I'm ready before alpha2, I'll come ask in here07:03
pittimicahg: ArchiveAdmin page updated07:17
micahgpitti: thanks07:18
=== warp11 is now known as warp10
=== doko_ is now known as doko
mvois vmware-view-client waiting for approval in the precise-partner queue ? and if so, could someone have a look please :)08:27
=== jodh is now known as jhunt
pittimvo: I don't see it in new or unapproved09:01
mvoodd, I reupload09:02
* cjwatson investigates lubuntu having ended up with unity-greeter13:24
ogra_wasnt there a bug about that that was fixed ?13:33
cjwatsonnot so you'd notice in the current images.13:34
cjwatsonbug 918401 and bug 92535813:35
ubot4Launchpad bug 918401 in unity-greeter (Ubuntu) (and 1 other project) "Unity-greeter installed by default on Lubuntu, crashing on start (affects: 8) (dups: 1) (heat: 50)" [Undecided,Confirmed] https://launchpad.net/bugs/91840113:35
ubot4Launchpad bug 925358 in casper (Ubuntu) "Lubuntu Precise live CD boots to a Unity-like DE (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/92535813:35
cjwatsonbut germinate output looks right; trying a local livecd-rootfs build13:37
ogra_jibel, hey, when you get Bug 924993, do you actually get a keyboard selection dialog ? i wonder if these two issues i see are related (and if its probably only an oem-config vs ubiquity thing)13:38
ubot4Launchpad bug 924993 in ubiquity (Ubuntu) "wireless password field disabled when user selects a protected network (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/92499313:38
ogra_i use oem-config here, see the same behavior but somehow the keyboard selection is supressed in that scenario ... while on systems without wlan the kbd selection shows up13:39
jibelogra_, I do, everything works as expected apart from this password field that should be enabled.13:39
ogra_then it might be arm or oem-config specific13:39
ogra_though arm is unlikel else kbd selection wouldnt be shown on the pandaboards13:40
* ogra_ wonders wh his Y ke onl works ever 5th press13:40
jdstrandpitti: re sru-release> the name implies it can only be used for -proposed to -updates. I see now there is a --security arg to go to -security. looking at the --help, I wonder about -updates to -security for the times that things might already be out of -proposed13:51
pittijdstrand: I could add a --security-only for this occasion, it's easy to do13:51
pittijdstrand: the packages are still in -proposed, so copying from -proposed to -security will be fine13:52
pittijdstrand: you could use -s as-is, then it would copy to -updates again, plus -security13:52
pittiit's just a waste of half the time13:52
pittibut it might eventually come in handy for other occasions like firefox13:52
jdstrandwell, since we run copy-report automatically, I don't really see why we would want --security-only at this time13:53
jdstrandit was more just the case of 'if the packages were deleted from -proposed already, but still in -updates'13:53
jdstrandI admit I don't know when things get deleted from -proposed13:54
cjwatsonwhenever we c/p the lines from the pending-sru page13:55
cjwatsonwhich appear once they're in -updates13:55
pittiright, the report just doesn't cover langpacks, as it filters them out except for -en as a representative13:57
pittias the validation process is different, and it would clutter up the page too uch13:57
pittiso in practice they stay in -proposed all the time13:57
jdstrandwell, language-pack-en shows it is no longer in -proposed, but language-pack-es is13:58
jdstrandthis was more curiosity anyway. I don't know if we will have another new set of langpacks for firefox 1014:00
pittijdstrand: right, -en might have been cleaned up already, so we need to copy that manually14:02
pittibut all the other n-hundred can be done with the script14:02
pittijdstrand: no, we won't14:02
pittijdstrand: this was an one-time change for 3.6->914:03
jdstrandpitti: ah great! thanks for your time :)14:04
pittijdstrand: so, for this one time I'd just locally comment out the copying to -updates, that's easiest :)14:04
* jdstrand makes a note14:04
pittiwrt. alpha-2, I suppose there's still a potential  lubuntu rebuild?14:04
pitti(as for freeze lifting)14:05
Riddellslangasek: for Kubuntu these images should be included in alpha 2: i386 and amd64 alternate, desktop and dvd14:07
cjwatsonI think I've figured out the Lubuntu problem14:08
cjwatsonit'll be a livecd-rootfs upload, build/publisher cycle, rebuild images14:09
superm1skaet wanted me to mention we are planning a2 for mythbuntu14:09
cjwatsonhow are your tests looking?14:10
superm1last tests were a week ago, so i'm going to try to drum up the team to test candidates today14:10
cjwatsonright, this looks a few orders of magnitude more sensible.14:13
skaetcjwatson,  go ahead and start on the upload and build for Lubuntu please.   We'll wait until gilir's online to decide to retest/not.14:14
skaetLast I hear from him, was that he was ok with alternates going out, but not the livecd's.14:14
cjwatsonthe current desktop images are definitely unreleaseable by any reasonable metric.14:15
cjwatson(lubuntu I mean)14:15
cjwatsonthey simply aren't as specified14:15
cjwatsonthis should cut their size down a fair bit too ...14:17
* skaet nods14:18
* skaet figures its time for all images to go on a bit of a diet as well... after A2 ;)14:19
cjwatsonfeel free to make suggestions ;)14:19
pittiwe have some overhead due to non-empty langpack updates14:19
pittiand ubuntuone bits need to be fixed to stop using gtk 2 and webkit (underway, AFAIUI)14:20
pittithen we can drop the old webkit gtk2 bits, some 8 MB14:20
pittiI did a size analysis recently, the biggest offenders were firefox/thunderbird (+2.6 MB each), new LibO (~ 1.5 MB), and of course python3 (~ +6 MB)14:20
stgraberskaet: I prepended the resolvconf issue to the list of known issues as I'm expecting quite a lot of users to hit that one14:22
stgraberskaet: looking at Edubuntu now14:22
skaetthanks pitti.   :)14:23
skaetstgraber,  thanks!   Yes,  anyone who knows of issues that are likely to be hit,  please review the TechnicalOverview and add them.14:23
cjwatsonhmm, but isn't the resulting Lubuntu system going to need to have recommends disabled too ...14:28
cjwatsongrah, this is annoyingly complex14:28
seb128pitti, webkit-gtk2 ... isn't that still used by ubuntuone-control-panel?14:28
seb128pitti, and gwibber14:29
pittiseb128: yes, but I thought ubuntuone stuff would be moved to GTK3 (sso-client) and PyQt (control-panel)14:29
pittiseb128: ah, gwibber, too, I thought ken was working on it14:29
seb128pitti, I'm not sure the pyqt stuff is going to happen this cycle14:29
pittinow that we have gnome-keyring GIR bindings14:29
seb128but let's see14:29
seb128pitti, he is, that didn't land yet either though ;-)14:30
* slangasek waves morning-like14:30
pittianyway, it's the best thing we have right now wrt. size reduction14:30
seb128slangasek, hey14:30
pittislangasek: good morning14:30
skaetslangasek,  good morning.   grab the coffee.  ;)14:31
slangasekRiddell: so you specifically don't want the amd64+mac and powerpc images published with the alpha?14:35
cjwatsonI think the Lubuntu alternate CDs should be respun.  Explanation in bug 918401 comment 32.14:35
ubot4Launchpad bug 918401 in unity-greeter (Ubuntu) (and 2 other projects) "Unity-greeter installed by default on Lubuntu, crashing on start (affects: 9) (dups: 2) (heat: 58)" [Undecided,Confirmed] https://launchpad.net/bugs/91840114:35
stgraberskaet: the Edubuntu technical overview is a bit long, unfortunately it looks like most of our changes happened between alpha-1 and alpha-2 ;) (alpha-1 was roughly identical to Oneiric)14:36
stgraberskaet: I'm now just waiting for highvoltage to do a final review so it may still grow or shrink a bit :)14:36
cjwatsonI am fairly sure we'll need a new ubiquity if we want Lubuntu desktop to be suitable for Alpha 2.14:36
skaetstgraber,  that's fine.   Thanks!14:37
Riddellslangasek: they are untested, you can if users are clear of that14:37
cjwatsonAt which point I might as well include last night's marathon NTFS installation fix there as well.14:38
skaetslangasek,  Riddell,  if they are untested,  they shouldn't go out.14:38
cjwatsonAny opinions on a new ubiquity just for Lubuntu?14:42
cjwatsonI'm preparing it now anyway14:42
cjwatsonIWBNI a Lubuntu developer were around here ...14:43
skaetcjwatson,  given the complexity I suspect its unlikely we'll get a home run and it all work,  however they're changes that are needed, so if they don't end up in A2, getting them in the dailies tomorrow is good.14:44
cjwatsonAre all the other images golden at this point?14:44
cjwatsonI agree it will be a slight fluke if they all work; however if everything else is good (at least for desktop) then going ahead with a ubiquity upload probably wouldn't hurt14:45
skaetcjwatson,  I haven't heard any other show stoppers - so all the ones that are tested are likelies at this point.14:45
cjwatsonThe partman-auto change technically affects non-desktops although I seriously doubt anyone would notice14:46
cjwatsonOK, so how about I go ahead and if it fails we just drop Lubuntu desktop from A2 (or attempt to release it tomorrow or something)14:47
skaetcjwatson,  sounds good.14:47
cjwatsonI don't see obvious drawbacks14:48
highvoltagestgraber: looks good!14:50
slangasekok, can someone tell me what ~/.isotracker.conf should look like? :)14:54
cjwatsonyou could grab nusakan's14:54
cjwatsonthough that'll have you pretending to be ubuntu-cdimage14:54
slangasekwhat password is it wanting?  Hopefully not the SSO password?14:56
slangasekanyway, this is for publish-image-set, so pretending is probably fine14:56
cjwatsonit's its own API key14:57
slangasekhum, getting an error:14:57
slangasekERROR: Cannot handle product Ubuntu Server EC2 EBS (Asia-Pacific-NorthEast) amd6414:57
slangasek... but that should match the 'ignore' regexp that I see in here14:58
slangasekignore_product_re = re.compile('Netboot |Upgrade |Server EC2|line-through')14:58
cjwatsonlooks like a space, quacks like a space, isn't actually a space, maybe?14:59
cjwatsonok, new ubiquity on its way14:59
cjwatsonoh, it's using .match not .search15:00
cjwatsonslangasek: update and try again15:01
cjwatsonheh, now it dislikes uwbi15:01
slangasekwell, progress :)15:02
cjwatsonwhich to be fair it probably can't actually handle - I don't know that there's any non-manual release handling for wubi yet15:02
* slangasek nods15:02
cjwatsonI've added that to the ignore regex for now15:03
cjwatsonit produces sensible output now15:03
cjwatsonwell, output15:03
cjwatsonsense is your problem15:03
cjwatsonsurprising that I'm not seeing amd64+mac anywhere in the output15:04
slangasekpossibly a missing $ on the amd64 variant15:06
slangasekfix pushed15:07
cjwatsonyeah, I was just getting there :)15:07
slangasekso to mark things as not-for-publishing, do we have a better mechanism than disabling them on the tracker?15:07
cjwatsonah yes, broken since r32015:09
* cjwatson satisfies curiosity15:09
cjwatsonr330 fixed it for armel+* but not amd64+*15:10
cjwatsonslangasek: not AFAIK; I think I've just manually filtered them out of the publish-image-set output when I've done this15:10
cjwatsonoh, we should do a source build15:11
* cjwatson goes to poke that15:11
skaetslangasek,   I'm not seeing any of the amd64+mac images with testing on them,  so they shouldn't be going out with A2.15:17
skaet(nor the powerpc ones)15:17
cjwatsonI've been making some progress on scaring up powerpc testers and reminding them that they actually need to do it, but it was only a couple of days ago so they may not have got organised in time15:18
skaetdo you want me to just go in and disable the definite "no go"s?15:18
skaetcjwatson,  thanks.  :)   I've also been talking to IBM (Linux manager at LCA and he was receptive to the notion of getting some of his folks lined up to help)  but it needs to be followed up on too.15:19
slangasekskaet: does disabling them prevent people from posting tests of them?15:29
slangasekI think disabling them on the tracker is probably still best if we're pretty sure we're not publishing them, but it does mean it'd be nice to have a better way for the tool to decide what to publish15:29
skaetslangasek,  yes,  but if there are no tests posted at this point,  its unlikely we'll be getting any before we release.15:29
skaetslangasek,  yes that would be good.   Maybe we can brainstorm with stgraber about it after A2 is out.   (publish ticky box?)15:31
slangasekor the tool could embed the policy directly about what's publishable or not based on testedness15:31
stgraberskaet: we could indeed create an extra build status for "ready" (trying to find a term that works for hardware testing and package testing too ;))15:32
stgraberslangasek: the data actually is available in the API, so I could give a script using our criteria and returning the list15:32
skaetembedding the policy would be nice, but it needs to be transparent on the ship/not - maybe a color change when the testing results are satisfied to indicate its now possible to ship?15:36
slangasekwell, that implies embedding the policy in *two* places, one of which the release engineer can't edit ;)15:38
stgraberright, if we want it visible on the website, we'd need a few extra tricks. Otherwise I'd simply make a python script using the API and put it in ubuntu-archive-tools (well, likely just update publish-image-set.py)15:41
stgraberso if someone wants to change the policy, it's just a matter of changing the script15:42
stgraberwhat I could do though is have the "ready" status visible on the website, have publish-image-set.py first apply the policy to the tracker and then show the list of what's ready to be published15:43
skaetjust having the ready status visible on the website was what I was looking for.  :)15:44
stgraberthat'd allow for manual overrides on the tracker by manuall marking stuff as ready and still have the script apply the policy automatically for the rest15:44
stgraberthen show the final list15:44
* skaet nods15:44
skaetslangasek,   what are the key bugs right now preventing upgrading from 10.04 to 12.04?  I'd like to add them to the release notes.15:46
stgraberskaet: so what's the current policy exactly? we clearly don't publish anything that wasn't tested at all but do we care about the actual test results? (like not publish anything that's not fully tested or not publish something that has all its results marked as failed, ...)15:46
skaetstgraber,  we need to refine the policies and make them visible - some parts are grey right now,  and it would be good to get the expectations nice and uniform.15:48
cjwatsonskaet: bug 917173 and bug 922485 come to mind (fixed in precise but not yet successfully backported)15:48
ubot4Launchpad bug 917173 in apt (Debian) (and 12 other projects) "lucid -> precise upgrade failed: Resolver failed to calculate the upgrade - dpkg-dev held back (affects: 1) (heat: 10)" [Unknown,New] https://launchpad.net/bugs/91717315:48
ubot4Launchpad bug 922485 in apt (Debian) (and 12 other projects) "Lucid Desktop i386 failed to calculate the upgrade to Precise (affects: 1) (dups: 1) (heat: 16)" [Unknown,New] https://launchpad.net/bugs/92248515:48
skaetthanks cjwatson15:48
* skaet adding them now.15:48
cjwatsonskaet: the bugs at this point are IMO sufficiently early in the process that we do not have a good overview of problems15:49
cjwatsonI was trying to figure out why the backports failed to verify but was derailed by a2 stuff15:49
skaetcjwatson,  fair enough.  :)   expect we'll be figuring out a lot of this over next month.15:50
slangasekskaet: right, the ones cjwatson listed.  Although, does listing LTS upgrade bugs set an unreasonable expectation for people that a 10.04->12.04 upgrade is a reasonable thing for mortals to do? :)15:53
skaetslangasek,  "Upgrading from 10.04 to 12.04 still has some known issues and is not recommended at this time." - just wanted to provide some examples  ;)15:53
slangasekright-o :)15:53
slangasekskaet: as for policy on publishing... I guess I would say anything that's untested, or anything that's been tested but had only failures, should not be published, and anything else is a question of human judgement?15:55
slangaseki.e., if there's a reason we're choosing not to publish an image that *has* been successfully tested, we could still indicate that manually15:55
skaetslangasek,  yes it does seem to boil down to that.   How about I start a wiki page off after we get A2 out, and we'll get the rest of the release team's input.15:56
skaetthen we can all have the same expectations on release day ;)15:57
slangaseksounds good16:00
cjwatsonthe good bit about testing upgrades is that you have plenty of opportunities for coffee breaks.16:00
cjwatsonrebuilding Lubuntu desktop with fingers crossed16:13
* skaet crosses fingers16:14
stgraberskaet, slangasek: Using http://paste.ubuntu.com/826568/ gives me http://paste.ubuntu.com/826569/ (though iterating through everything takes almost a minute ... so custom status would be nice to avoid that, then just products.get_list and builds.get_list would be required)16:32
stgraberso that's everything that's currently active on the tracker (status = 0) and with at least one mandatory testcase marked as passed16:33
skaetstgraber,  it should actually be all mandatory testcases marked as passed.... else they shouldn't be mandatory.16:35
skaetbut its a judgement thing, depending where in the release cycle we are.16:36
skaetstgraber, http://paste.ubuntu.com/826569/ looks good though.  :)16:37
stgraberskaet: indeed, we definitely want all the mandatory passed at least once for final, all the run-once also passed at least once and we can probably ignore the optionals (or only consider failures?)16:38
stgraberskaet: anyway, writting down the policy will help quite a bit ;)16:38
slangasekskaet: but late in the cycle, those also typically gate whether we're ready to publish, rather than just whether a particular image should be published16:38
slangasekso I think having the tool just block untested and completely-failed images gets us to the right place as far as automation16:39
skaetslangasek, stgraber - fair enough.  Will work on writing it up tomorrow, and see if we can get it discussed next week.   I'll try to add a dimension for Alpha, Beta, Final criteria - so we're clearer.16:40
slangasekhmm, are Ubuntu Studio considered publish-ready?18:06
slangasekapparently there are no successful ubiquity installs, just a bunch of failures18:07
slangasekskaet: ^^ I'm holding off on ubuntustudio for now given the above18:12
skaetslangasek,  ack18:17
skaetscott-work, ^ any data that isn't in the tracker?18:17
seb128slangasek, skaet: is there any plan to unfreeze today?18:21
slangasekI think we should be unfreezing at this point; skaet?18:21
seb128just trying to schedule my end or day and friday18:21
scott-workslangasek: skaet:  i believe there were successful installs - there were cases of ubiquity failing but also lightdm not properly configured which may have been construed as "ubiquity failuers"18:21
slangasekscott-work: well, the only people who've posted test results on the tracker marked their tests as failed18:22
cjwatsonLubuntu desktop looks better to me now18:23
cjwatsonat least gives me a working desktop, haven't tried an install18:23
scott-workslangasek:  it may be better to not publish for A2 then18:24
slangasekscott-work: ok18:25
skaetthanks cjwatson,   was wanting to hear how it looked before unfreezing.   No results in from any of the lubuntu folk though yet,  but at this point,  not seeing much upside in keeping it frozen.18:25
skaetscott-work,  I'll comment out the ubuntu-studio comments from the technical overview then as well.18:25
slangasekcjwatson: evidently the rules on #ubuntu-devel /topic handling have changed since last I needed to set one; can't set it directly, chanserv won't set it for me?18:31
cjwatsonyou have +t, you should be able to use /msg chanserv topic18:32
* cjwatson tries to find what the channel mode used to be18:33
slangasekyeah, chanserv didn't like me18:35
slangasekcan't set the channel here either18:36
=== slangasek changed the topic of #ubuntu-release to: Alpha 2 testing in progress: Archive:open | http://pad.ubuntu.com/ubuntu-release | Precise Pangolin Release Coordination. Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | we accept payment in cash, check or chocolate covered ants | melior malum quod cognoscis
davmor2slangasek: you just weren't hitting it hard enough :)18:36
cjwatsonhm, you know, sod it, +t isn't mlocked on -devel afaics18:37
scott-workslangasek: skaet:  sorry for dropping the ball on A2, i will be more prepared in the future18:49
stgraberslangasek: do we want to wait a bit longer for the resolvconf upload or should I go ahead and upload it nowish? (thanks for the postrm fix btw)18:55
slangasekscott-work: no skin off my nose... :)18:55
slangasekstgraber: I'm fine with you uploading it now18:55
stgraberslangasek: good. Will do a couple more tests on it and then upload, should definitely be in the archive in time for the Edubuntu daily (assuming they've been switched back on)18:56
slangasekthey haven't been just yet18:59
slangasekwho usually handles the cloud image publishing?19:01
utlemmingslangesek: that's me19:01
slangasekutlemming: ah, hi :)19:01
slangasekutlemming: is there anything else pending from your POV before those can be published?19:01
slangaseklooks like the testing is done19:01
slangasekand we're pushing out the ISOs, so I guess it's time for the cloud images to go out also?19:02
utlemmingslangesek: no, we're good to go, just waiting for the go-ahead to publish them19:02
Riddellslangasek: announcing the release sometime soon?19:02
slangasekutlemming: go ahead then :)19:02
utlemmingslangasek: publishing now19:03
slangasekRiddell: well, skaet will be19:03
RiddellI'm away for a few hours, I'll tell my kubuntu people to watch and put on the website when they see it19:03
skaetRiddell,  sounds good.   want me to post in the #kubuntu-devel channel,  or will someone monitor here?19:04
Riddellskaet: that would be good yes19:04
utlemmingcloud-images for Alpha2 are now public19:08
skaetutlemming,  yup,  able to see them now. :)19:17
=== skaet changed the topic of #ubuntu-release to: Alpha 2 released! Archive:open | http://pad.ubuntu.com/ubuntu-release | Precise Pangolin Release Coordination. Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | we accept payment in cash, check or chocolate covered ants | melior malum quod cognoscis
skaetLooks like we're all nicely released now for A2.    Thanks slangasek!21:03
balloonsgratz everyone!21:48
=== bladernr_ is now known as bladernr_afk

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