/srv/irclogs.ubuntu.com/2012/10/19/#ubuntu-release.txt

phillwinfinity: yeah, a glass of wine / beer & a chillax with sleep will do everyone good :)00:36
xnoxphillw: I dislike encouragements of alcohol consumption.01:05
phillwso do I.. but  I dislike encouragements of respinning the world ~ 24 hours before a release... we can't win them all :P01:07
xnoxphillw: not the world, just a couple of images.01:09
ScottKSo I accept two and then I upload two ...04:08
SpamapSScottK: the neverending SRUqueuee.... it goes on and on and on05:11
ScottKYou could help that by accepting my postfix SRUs ...05:11
ScottK:-)05:12
* micahg is reminded he promised to sponsor another SRU05:12
SpamapSScottK: I will do an aggressive SRU run if I can find time next week. Otherwise, the queue will likely get nice and long until post UDS05:14
ScottKHere I am trying to show your server users how responsive the system is to issues ...05:14
* micahg is trying to keep backports chugging along05:17
lamont205:24
lamontmeh05:24
obounaimGood morning06:20
=== tkamppeter_ is now known as tkamppeter
=== henrix_ is now known as henrix
infinitycjwatson: So, we don't really have anything to upload just yet, but are we ready for me to inject chroots?08:34
=== yofel_ is now known as yofel
=== mmrazik is now known as mmrazik|lunch
cjwatsoninfinity: Yeah, please do - I think doko has some bits09:44
infinitycjwatson: Doing.09:44
infinitycjwatson: Alright, should be done.  I should throw a base-files at it to test it.09:49
infinitycjwatson: Oh, lolz, also your efi bits got dumped in raring/unapproved by IFP.09:51
infinitycjwatson: I guess that makes sense, since we've already seen that with copies.09:51
cjwatsoninfinity: Yeah, actually by the first publisher run09:54
cjwatsoninfinity: We almost explodificated the world by not following NewReleaseCycleProcess and stopping the publisher before setting raring to FROZEN09:54
infinitycjwatson: Yeah, I caught that in scrollback.  Sorry about that, didn't think about the consequences.09:55
cjwatson(Also, that stuff landing in unapproved is another symptom of the "UEFI copies within same archive shouldn't require re-approval" bug.)09:55
cjwatson(Which I should probably file and fix.)09:55
infinitycjwatson: Right, that's what I assumed.09:56
* cjwatson files bug 1068558 for that10:19
ubot2Launchpad bug 1068558 in launchpad "UEFI copies within same archive shouldn't require re-approval" [Undecided,New] https://launchpad.net/bugs/106855810:19
babyface_a lot of chinese user are complaining for this issue, can anybody take care of it? https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/104303110:23
ubot2Launchpad bug 1043031 in language-selector "fontconfig-voodoo is not included in language-selector-common" [Undecided,Confirmed]10:23
* cjwatson requests translations opening (NRCP step 16)10:28
cjwatsonbabyface_: fontconfig-voodoo was intentionally removed because (I'm told) fontconfig itself should automatically take care of it10:28
cjwatsonAs I said in that bug10:29
cjwatsonbabyface_: If it's not doing the right thing, ask the desktop team10:29
cjwatsonIt's not a matter for the release team10:29
babyface_cjwatson, ack. thanks.10:29
cjwatsonAnd, you know, I asked on that bug for more information nearly a month ago and then there was radio silence until an hour ago ...10:30
cjwatson(Not that I'm even on the desktop team)10:30
babyface_cjwatson, sorry for that. I will verify it, and talk to desktop team if needed. thanks.10:33
=== mmrazik|lunch is now known as mmrazik
cjwatsonupdated britney for raring (NRCP #17)10:43
cjwatsonupdated merge-o-matic for raring (NRCP #18)10:44
cjwatsonhmm, MoM seems to have stopped again, better investigate that ...10:45
cjwatsonI wonder how the Debian jikespg maintainer managed to upload something with a different .orig.tar.gz!10:47
cjwatsonoh well, MoM hopefully unstuck10:48
=== doko_ is now known as doko
dokocan I copy my gcc-4.7 stuff?10:51
cjwatsonerr, apparently I may have been economical with the truth when I said the publisher was back on.  It is now ...10:52
cjwatsondoko: go ahead10:52
cjwatson(feel free to accept your own; raring is only frozen to ensure that only the toolchain goes in, not because we need to control anything11:07
cjwatson)11:07
=== henrix is now known as henrix_
=== henrix_ is now known as henrix
rtgnow that the release carnage is somewhat abated, can I get an AA to NEW linux-lts-quantal and linux-meta-lts-quantal in the Precise queue ?13:23
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
infinityrtg: I'll get there shortly.14:33
infinityrtg: After I eat my lunch. ;)14:33
rtginfinity, thanks. no rush, just wanted to make sure they didn't get forgotten.14:34
TheLordOfTimewas 2d unity removed from Q?14:49
ScottKTheLordOfTime: #ubuntu-desktop14:52
tumbleweed(and, yes)14:52
bdmurrayBeing the "new guy" on the SRU team - when does the team take charge of the quantal proposed queue?15:22
ScottKAt release.15:22
ScottKAt least that's when I quit caring when I wasn't on both teams ....15:24
infinitybdmurray: What ScottK said, with a logical tautology of "stuff in -proposed is an SRU when it's an SRU" which is, yes, after release.15:33
cjwatsonSo, britney is actually not looking hopelessly terrible16:09
cjwatsonI have it able to run over a hypothetical natty-proposed -> natty, and it takes maybe five minutes or so in all and produces output that looks pretty plausible16:09
cjwatsonNow, I still need to write something that takes its output and turns it into an Archive.copyPackages call (or maybe actually a load of individual Archive.copyPackage calls, since we probably want to be quite careful about versions)16:11
cjwatsonI'll think about that parenthesis a bit16:11
cjwatsonAlso my changes to the Debian code are currently fairly brutal and disorganised16:11
cjwatsonBut this is looking promising for having it able to work by sometime next week16:12
infinityWe want to be careful about versions, we also want to be careful about getting it in one transaction, or we just lollerskated away half the reason to use britney.16:12
cjwatsonWell16:12
cjwatsonThe perfect shouldn't be the enemy of the good here16:12
cjwatsonArchive.copyPackages doesn't give any kind of transactional assurance16:12
infinityTrue, but getting half in before a publisher run, and half after will create half an hour of messy.16:12
cjwatsonIt just creates lots of jobs16:12
cjwatsonRight, but no worse in general that it would've been without britney16:13
infinityTrue, true.16:13
infinityMaybe it needs an XXX: FIXME on it, then. :P16:13
cjwatsonIt would certainly be nice to be able to copy everything in a giant transaction16:13
cjwatsonBut I suspect that attempting to do that right now would make LP explode16:14
cjwatsonPerhaps instead of processing the heidi output (a full dump of what the target suite ought to look like) I should process the update_output text16:14
cjwatsonThat would tend to result in a series of incrementally sane changes16:14
infinityWell, even a publisher "transaction"... Though, after carefully removing everything that hack lock contentions with the publisher, intentionally adding one seems bad.16:15
cjwatsonNot perfect in cases of loops, but it would optimise16:15
infinitys/hack/had/16:15
cjwatsonI think this approach would be a pretty good first cut, and we can talk with LP folks about how we might come up with safer interfaces16:16
* infinity nods.16:17
cjwatsonThe number of copies involved will tend to be limited by buildd performance, so we shouldn't be DoSing the PCJ queue in the same way that auto-sync does (or did, before I made manual copies take precedence)16:17
infinityI agree that half an hour of potential installability oopses probably isn't world ending.16:17
cjwatsonWell, the way I'd put it is reducing the probability of such events from very high to rather low.16:18
cjwatsonAs opposed to zero.16:18
infinityThough, the contention that it's "not worse than before" may not be entirely true, cause if we have a snag all moving at once, those would have previously snagged one at a time based on build-deps.  Maybe.16:18
* infinity shrugs.16:18
infinityWe'll see.16:18
cjwatsonThere may be individual situations that get worse; my contention is that it will be on average significantly better, even without transactionality :)16:18
infinityYes, on average, it should be an improvement.  We're in raging agreement.16:19
cjwatsonExcellent.16:19
bdmurrayif I do the sru verification of bug 1068389 is that sufficient to get it out soon or should it see more testing?16:35
ubot2Launchpad bug 1068389 in ubuntu-release-upgrader "P->Q - do-release-upgrade crashed with UnicodeEncodeError: 'ascii' codec can't encode character u'\xbb' in position 1: ordinal not in range(128) in DistUpgrade/DistUpgradeViewText.py", line 143, in showInPager" [Critical,In progress] https://launchpad.net/bugs/106838916:35
cjwatsonHmm, perhaps I want an equivalent of Archive.copyPackage that uses the MASS_SYNC copy policy16:44
cjwatsonBecause I want version control, but I also want to avoid lots of mail spam16:44
cjwatsonOTOH ... maybe what I want is "send mail as if this had been a direct upload to the release pocket"16:45
cjwatsonmaybe this needs to be a new copy policy16:45
infinitybdmurray: Given the nature of the bug, if it's tested to be an improvement, go ahead and release it, IMO.16:45
cjwatsonoh, notify() has its own auto-sync handling, I think16:46
infinitycjwatson: "Send a mail as if this had been a direct upload..." is what we do currently on pocket copies, isn't it?16:46
cjwatsonBet it doesn't work for copies16:46
cjwatsoninfinity: Except for the ways in which it differs16:46
infinitycjwatson: Heh.16:46
cjwatsonI'll need to check in more detail, but I believe that: (a) it sometimes has different recipients; (b) it will notify about auto-syncs16:47
cjwatsonI might be wrong about (b)16:47
cjwatsonActually, it might work if I pretend that all the copies are sponsored for katie16:50
cjwatsonThis isn't a hacky system at all16:50
infinityWait, we still special-case katie?16:51
cjwatsonOh yes16:51
infinityThere aren't enough palms for my face.16:51
cjwatsonauto-syncs are all sponsored for katie16:51
cjwatsonIt's what makes them not send giant amounts of mail16:51
infinityWell, yeah, I knew there was a hack in play, I just didn't realise it was still that.16:52
cjwatsonIt inhibits upload notifications and translation import error notifications; I think those are its only purposes16:52
cjwatsonHm, I'll need different output from britney anyway to get hold of the exact versions17:17
=== henrix is now known as henrix_
=== Ursinha is now known as Ursinha-afk
bdmurrayslangasek: I'd like to add ubuntu-release-upgrader to -updates early20:40
bdmurrayslangasek: see bug 106838920:40
ubot2Launchpad bug 1068389 in ubuntu-release-upgrader "P->Q - do-release-upgrade crashed with UnicodeEncodeError: 'ascii' codec can't encode character u'\xbb' in position 1: ordinal not in range(128) in DistUpgrade/DistUpgradeViewText.py", line 143, in showInPager" [High,In progress] https://launchpad.net/bugs/106838920:40
slangasekbdmurray: while it doesn't seem terribly urgent to me (affected users can always either restart the upgrader and not ask for details, or wait for the fix before upgrading), I also don't think we'll get much further feedback on it by letting it cook in -proposed, so ack20:43
bdmurrayslangasek: it does leave your sources.list at quantal instead of precise20:43
slangasekah20:44
slangasekbdmurray: urgency explained - so double ack :)20:44
slangasekbdmurray: maybe that program should be wrapped in a generic exception handler to roll things back on crash?20:45
slangasek(roll back && reraise)20:45
slangasekunrelated to the current SRU obviously20:45
bdmurraydo you know how long it'll take for the dist-upgrader in -updates to show up?20:53
slangasekassuming that's done automatically by the publisher, should be ~30 minutes20:54
stgraber^ marked quantal as released, archived all the quantal and 12.04.1 milestones, added raring daily and kept precise daily22:12
stgraberso the tracker should be ready for the first raring daily builds22:12
* stgraber adds a work item to make it easier to access archived series22:15
slangasekraring is quickly achieving semantic satiation for me22:29
slangasekI think future release codenames should be chosen to guard against this22:29
ScottKI think future code names should be announced before final freeze so we can make the tools aware.22:30
slangasekthat too22:31
infinityI think when we run out of alphabet, our next naming scheme should be "reusing the codenames of other distributions", just to confuse people.22:34
infinityAnd then see how long it takes for someone to make a crack about woody beefy miracles.22:35
stgraberthat or continue with utf-8 and see how many tools and other websites we can get to crash22:35
infinityI don't know any animals or adjectives that start with ☭22:36
infinityIn Communist Russia, release codenames blog about you?22:37
slangasek☭-cell-anemic ☭head shark22:37
slangasekobvs22:37
xnoxinfinity: slangasek: wait... is that not a little head and beak of a bird possibly dove?!22:42
ScottKThere's a reason we switched to version numbering from version names in backports revisions ...22:42
ScottKAs long as the calendar moves forward we've got several decades to figure out the next plan.22:42
slangasekxnox: yes, isn't that the Latvian official bird?22:42
skaetthanks stgraber22:42
xnoxslangasek: yes, it is. They taught us that in school. Strangely all the history text books were published in 1992.22:42
* skaet has moved hopefully all the quantal ref's to raring in https://wiki.ubuntu.com/ArchiveAdministration22:42
infinityNot sure that was necessary.  They were examples that used to date all the way back to... Forever ago.22:42
skaetinfinity, its a step in the process (was a link to raring-changes that needed updating, rest cosmetic, I agree).22:57
ScottK^^^ is already an accepted SRU in quantal, so just to make sure it's not forgotten ...23:46

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