/srv/irclogs.ubuntu.com/2012/01/09/#ubuntu-release.txt

=== AlanChicken is now known as AlanBell
cjwatsonso it turns out that the API autosyncs over the weekend synced rather more than intended11:47
cjwatsonthe selection of source packages to sync was correct, and based on testing11:47
cjwatsonbut the API method used to do the actual sync doesn't take a from_series parameter, so it took the most recent published source in Debian for each of the named source packages11:48
cjwatsonin some cases that would have been from unstable or even experimental :-/11:48
Laneydo you know what was affected?11:48
cjwatsonI'm going to fix LP as a priority, and then try to figure out a list of affected packages11:48
cjwatsonlibcdio was the one that alerted me to this11:49
Laneylast time we didn't pay anywhere near good enough attention to the impact of the borked sync and it kept cropping up later on in the cycle11:52
=== jdstrand1 is now known as jdstrand
cjwatsonLaney: OK, report sent to ubuntu-release@13:57
Laneygreat, thanks13:57
Laneydoesn't look as bad as it could be13:58
Laneyactually it is a bit surprising that it's only ~15 packages13:59
cjwatsonthe selection of packages to sync worked properly14:02
cjwatsonit was only the selection of versions for those packages14:02
cjwatsonso the only packages affected were those that were going to be synced anyway (newer in testing since the last autosync, or just plain new in testing) and that also had newer versions in unstable and/or experimental14:03
cjwatsonthat limited the damage quite a bit14:03
Laneyah14:04
Laneythat is fortunate indeed14:04
cjwatsonI've nearly got it fixed, just can't quite get the last damn test to pass14:04
cjwatsonfeeding all the libcdio rdeps to sbuild now14:11
=== bladernr_afk is now known as bladernr_
Laneymaradns ftbfs almost everywhere :(14:13
Laneyat first glance looks like arch/indep fail14:14
cjwatsonhm, must have missed that14:14
tumbleweedgiven that it's a day old in experimental, that'll probably be fixed soon14:14
cjwatsonmaybe we should get in touch with the Debian maintainer there and find out what's going on14:14
Laneyhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=65498714:14
ubot4Debian bug 654987 in maradns "maradns: FTBS in experimental" [Important,Open]14:14
cjwatsonif maradns and a single library transition is the worst of it, though, that could be a lot worse14:15
cjwatsondepending on how groovy looks14:15
cjwatsonoh, meant to CC jamespage, will bounce it to him14:15
LaneyI can't fix maradns quickly enough to do it in work hours14:20
Laneysurprised the maintainer is so confused by it though …14:22
=== bladernr_ is now known as bladernr_afk
=== bladernr_afk is now known as bladernr_
=== bladernr_ is now known as bladernr_afk
=== bladernr_afk is now known as bladernr_
cjwatsonpitti: do you think I can safely go ahead and promote mvo's release-upgrader-apt and release-upgrader-python-apt from lucid-proposed to lucid-updates?16:37
cjwatsonit doesn't have bugs associated so doesn't magically go green; but these are new packages so should be no impact16:38
pitticjwatson: oh, sure; I haven't talked to mvo about testing them, but if he is happy, I am16:38
cjwatsonhe said he'd tested with the packages in his PPA16:38
mvoshould be fine, its tested in the auto-upgrade tester for the lucid->precise upgrade profile automatically and seems to be doing ok afaict16:40
pittimvo: great, thanks; so, fine for me16:42
mvothanks! I will update update-manager to use the version from -updates then, thats great16:42
cjwatsoncopying16:43
cjwatsonoh damn I forgot the command-line syntax and also copied to -security by mistake16:43
cjwatsonI suppose I should delete that16:43
=== bladernr_ is now known as bladernr_afk
=== bladernr_afk is now known as bladernr_
=== bladernr_ is now known as bladernr_afk
=== bladernr_afk is now known as bladernr_
jbichaLaney: I mistakenly uploaded totem 3.3.4 meant for a PPA to precise, how should I fix this?21:48
Laneyerr22:24
micahgLaney: sorry, that wasn't the question he was supposed to ask you :)22:26
Laneyhmm?22:26
micahgLaney: I thought he was asking for dput tips, so that's why I sent him to you22:27
Laneyam I considered particularly knowledgable about dput? :P22:28
micahgLaney: weren't you the one suggesting people change their default dput localtion?22:28
LaneyI do suggest that, yes, but I thought it was common practice22:29
Laneyjbicha: anyway, if that's why you did it then I suggest you change the defaultkrkeyman__22:29
Laneyerr wtf22:30
* Laney bashes the x keyboard hard22:30
Laneyclipboard22:30
Laneyas for the specific upload, I assume you don't want that series to be in precise?22:31
jbichaLaney: we will definitely be sticking with totem 3.0 for precise22:31
Laneythen you'll need to revert to the previous version22:32
jbichasince the new version is in depwait, is there a way to remove/overwrite the new upload so we don't have to use 3.3.4+really3.0?22:33
micahgright, but I think the best thing to do is to have an archive admin remove 3.3.4 and he upload a regular 3.0.1-0ubuntu1322:33
micahgotherwise we're stuck with that horrible version for 5 years :(22:33
Laneywell, the source is there even if binaries are not22:34
micahgyes, but that can be removed easily :)22:34
Laneyreally?22:35
micahgyeah, it's just a source, so no problems with apt upgrading (that's the main reason to revert by uploading a higher version)22:36
Laneydoes launchpad let you do that? there will still be publications for this version22:37
micahgyep22:37
Laneyweird22:37
micahgunless something was "fixed" recently22:37
cjwatsonwe aren't going to remove that version, and we would have to edit LP code to upload an older one anyway23:03
cjwatsonat least I'm fairly sure of that23:05
cjwatsonI suppose I can try it on the basis that you're going to be uploading a newer version anyway, although I'm a bit worried of screwing up the database23:06
Laneyhrm, might set a precedent that this is the way to deal with accidental uploads23:07
cjwatsonwell, I may actually be wrong; soyuz seems to check against the ancestry whose definition includes a restriction to pending and published SPPHs23:26
cjwatsonjbicha: still around?23:26
jbichacjwatson: yes23:42
cjwatsonjbicha: will you be around in about 45 minutes?23:47
jbichacjwatson: sure23:47
cjwatsonjbicha: this is very much against my better judgement, but I'll try removing the totem 3.3.4-0ubuntu1~precise1 source23:48
lamontarm maintenence... sorry for the wave23:48
cjwatsonjbicha: I think you may be able to try re-uploading now23:49
cjwatsonbut I'm not sure; it may have to publish the deletion first23:49
cjwatsonand it may get the package ancestry wrong23:50
cjwatsonI can't predict the exact effects, although I don't think they'll be too horrible23:50
cjwatsonjbicha: I'd like to know when you've done it so I can watch logs, though23:52
jbichacjwatson: ok, I just dputted 3.0.1-0ubuntu1323:55
cjwatsontwo minutes ...23:58

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