/srv/irclogs.ubuntu.com/2013/04/22/#ubuntu-release.txt

jbichaplease reject that u-g-default-settings00:45
jbichaI'd like to see the gnome-shell & u-g-default-settings uploads in for raring00:51
ScottKLet's hope I rejected the right one.04:22
=== highvolt1ge is now known as highvoltage
stgrabergood morning06:50
pgranermorning stgraber07:13
* infinity is questioning the wisdom of waking up today.07:23
Laneydoko__: yes indeed (I get mailed about them). I'll upload something in a second.08:19
cjwatsonI'm going to temporarily remove ubuntuone-couch in order to be able to copy it back (there was an override accident).08:25
infinitydouble-override explodey bug?08:26
cjwatsonwgrant reckoned "overridden twice the same way"08:26
wgrantcjwatson: You shouldn't actually have to remove it08:27
wgrantJust copying it over itself should work08:27
infinityYeah, just copying over itself works.08:27
infinityJinx.08:28
infinityEither way, it's an irksome bug because no one notices the effects right away.08:28
cjwatsonwgrant: It didn't earlier, but I only just noticed that that was because I forgot to use -b08:28
cjwatsonBut too late now08:28
wgrantAha08:28
wgrantyes, that would do it :)08:28
infinityWe now have shankbot double-checking my work on kernel SRUs to make sure things don't disappear.08:28
cjwatsonLooks like it worked08:28
cjwatson(That's what I get for trying to do out-of-the-ordinary LP-related jobs at the weekend)08:29
cjwatsoninfinity: My new orphaned-sources script in u-a-t turns out to be good at spotting this08:29
infinitycjwatson: \o/08:30
infinityremoved and blacklisted mozilla-gnome-keyring08:30
cjwatsonThough it probably doesn't work right on stable releases08:30
cjwatsonSo shankbot's still helpful for SRUs08:30
wgrantcjwatson: That won't notice things with arch-dep stuff as well, will it?08:31
cjwatsonIt won't notice if a binary only disappears on a subset of architectures, if that's what you mean08:32
cjwatsonOr if only a subset of binaries disappear08:32
infinityThat nyquist/i386 FTBFS is messing with my head.08:32
stgrabercjwatson: hey, I just went through the ReleaseProcess wiki page, updating the bits about the ISO tracker. I was also surprised to see no mention of britney/proposed-migration on there. What's the plan? turn off britney before we start rolling final images (so we can decide what goes as SRU and what goes as last minute changes to raring)?08:32
cjwatsonstgraber: Probably because it's the first release with it and we haven't made up a process yet :)08:33
infinitystgraber: Yeah, a global block and unblock things as we want them, methinks.08:33
infinity(ie: the same thing Debian does near release)08:33
cjwatsonIndeed, global block makes more sense than commenting out the cron job08:33
cjwatson("block-all source")08:33
cjwatsonI'll edit ReleaseProcess now08:34
stgraberhmm, yeah, block-all indeed sounds better, that way we don't have to do all the checks ourselves before copying08:34
* infinity nods.08:34
cjwatsonIt's not really a time-dependent thing though, it's "before publishing anything that's going to be a zero-day SRU"08:35
infinityWould be nice if we could extend britney to understand seeds and do something like "block-all seeded-source", but meh.08:35
cjwatsonI think I'll put it at -3 days (i.e. now) and apply the hint08:35
cjwatsonUnless anyone objects?08:35
infinitycjwatson: Go nuts.08:36
infinityWe'll definitely have a few things to let through, but I prefer us putting thought into it at this point anyway.08:36
cjwatsonYeah08:36
stgraberfine with me08:36
* cjwatson remembers to make a paired change to NewReleaseCycleProcess08:36
cjwatsonOK, hint applied, let's see if it works08:38
infinitySuch confidence.08:38
cjwatsonWe'll need to keep an eye on excuses08:38
infinityunblocks are just "unblock foo/ver"?08:39
cjwatsonhttp://ftp-master.debian.org/testing/hints/README08:39
cjwatsonBut indeed08:39
infinityYeah, I have to google that every time.  We should just have the README in the hints bzr.08:39
infinityAssuming britney will ignore it because the user "README" has no perms. :P08:40
cjwatsondoko__: Should we remove avian/armhf, or do you expect to be able to fix that?08:45
=== doko__ is now known as doko
dokocjwatson, hmm, can we remove it proposed instead?08:45
dokoit in ...08:45
cjwatsonHow do you mean?08:45
cjwatsonThere isn't an armhf build of avian in -proposed; that's kind of the problem08:46
dokoI mean, remove the source in binaries in -proposed08:47
dokos/in/and/08:47
cjwatsonOh.  Sure, if you want to withdraw the upload from -proposed you can, or if you'd prefer we can just put it on the list of uploads to carry over to s-proposed08:48
cjwatsonThe latter might be cleaner if it's an "I'll fix it up, but not this week" kind of thing08:48
dokoyep, we can carry it over too08:49
infinityEh.  No point in keeping it in s-proposed if the plan is for doko to upload a newer version at some point.08:49
infinityBut either way.08:49
dokosame for handbrake, that was a bad sync :(08:50
infinitydoko: handbrake will be carried over, it builds fine against libav9, we just haven't migrated yet.08:50
cjwatsoninfinity: Might just make the history clearer08:50
infinitycjwatson: Did you have any clever ideas for git-annex's suckage?08:51
Laneyi am trying to penetrate this makefile08:52
Laneyto find out where to insert flags08:52
cjwatsonYeah, Laney's clearly ahead of me here :)08:52
cjwatsonLaney: Or you could just build-dep on yesod on powerpc too - doesn't it work there now?08:53
Laneyyes, but armhf08:53
infinitySomeone sorting out pytables/ppc wouldn't hurt my feelings either.08:53
cjwatsonarmhf won't work anyway will it?  git-annex uses template haskell08:53
cjwatsonUnless that's only in stuff that can be avoided ...08:54
Laneynot sure; the current version at least builds there on debian08:54
Laney(in unstable)08:54
Laneyanyway, I ought to do some normal work, so feel free to take over08:54
LaneyI was trying to find out how to poke an -f-Webapp in for the non-yesod case in d/rules08:54
cjwatsonOh, it got more cabalised?08:55
Laneyit kind of is, but I cannot tell at this point how much that gets used08:55
cjwatsonI'm happy (ish) to have a look08:56
cjwatsoninfinity: Don't suppose you left leviathan on?08:56
infinitycjwatson: I did.08:57
cjwatsonOrsome.08:57
Laneythe new version in Debian is evne more so, so if you get ragey looking at that might be an option08:57
xnoxinfinity: i briefly looked at pytables/ppc but can only look at it against past EOD really as it quite a weird one =)08:57
cjwatsonLaney: Yeah, I was considering that a while back but it had a load of extra features and stuff08:57
Laneyla la la08:58
cjwatsonWe probably should have done that weeks ago08:58
LaneyWell, hopefully we can find out how to do this, or decide that leaving armhf broken is alright08:58
cjwatsonIt doesn't matter for proposed-migration at this point, but I agree it'd be good to fix09:00
cjwatsonYeah, I think it's easier than you think.  -f-Webapp isn't the problem09:03
Laneyoh, good09:04
stgraberinfinity: hey, I just had a quick look at http://people.canonical.com/~ubuntu-archive/testing-ports/raring_probs.html and noticed it's not empty. For that hv-kvp-daemon-init entry, shouldn't it be safe to just make the package build only on i386 and amd64 (since AFAIK hyperV only supports those anyway)?09:07
infinitystgraber: That absolutely should be arch-restricted, yes.09:09
infinitystgraber: I'll do that right now.09:09
dokocjwatson, cinnamon now built on armhf, but is it blocked now manually?09:14
infinityI'll unblock in a sec.09:14
infinityWe've blocked the world now.09:14
xnoxstgraber: on the iso tracker, I'm failing to look up when was the last time the 3 MAAS testcases were fully tested on raring.09:15
xnoxAlso do we have anyone confirmed to test MAAS with candidate images? =) jamespage had his turn already with quantal release ;-) so maybe someone else this time around?09:16
infinitystgraber: New hv-kvp-daemon-init in the queue in 2 mins.09:18
stgraberxnox: I'll get the dates from the DB, one sec09:18
stgraberinfinity: cool, I'll review once queuebot notices, should be an easy review ;)09:18
xnoxstgraber: cuase a recent enough test, might be ok for that. Thanks!09:18
stgraber(will just need to remember to remove any leftover armhf and powerpc binaries afterwards)09:19
infinitystgraber: I'll remove those now, so britney doesn't have a sad.09:19
infinitystgraber: Done.09:20
stgraberxnox: 2013-02-13 and 2013-02-14 was the last time those were covered, so they definitely need re-testing09:21
xnoxhm at Alpha2 time. stgraber do you know who did the test? Can we ping the same person? =)09:22
stgraber       1289 |   37582 |      1 | 2013-02-14 17:00:37 | hggdh209:25
stgraber       1288 |   37582 |      1 | 2013-02-14 16:13:55 | hggdh209:25
stgraber       1290 |   37582 |      1 | 2013-02-13 21:26:06 | hggdh209:25
stgraberthat was a day before he announced he was leaving Canonical, so that'd explain why we didn't get any result after that09:26
pgranerstgraber, I'll track someone down to do it09:27
stgraberpgraner: thanks09:27
pgranerstgraber, no prob09:28
infinitystgraber: OMG REVIEW FASTER RELEASE IS SOON EEEE!09:29
stgraberinfinity: had to wait 5 minutes for LP to give me a two lines diff ;)09:31
ogra_there is a release ?09:31
infinityogra_: That's the plan.09:31
LaneyOh crap, we aren't rolling?09:32
xnoxWell, at such a last notice, I guess we'll scrap pressing CDs =)09:32
cjwatsonstgraber: bug 1170120 :-)09:35
ubot2Launchpad bug 1170120 in Launchpad itself "Package diff generation is unnecessarily unresponsive" [Low,In progress] https://launchpad.net/bugs/117012009:35
stgrabercjwatson: yay, thanks for fixing this!09:38
cjwatsonwell, pending review and unlikely to make it now in time to be useful for raring, but yeah09:41
cjwatsonwhen I actually looked at it it became clear that the slowness was largely artificial09:41
cjwatsonpytables> I started looking at that the other day, it's just an endian-related bug I think, just didn't quite finish ...10:29
cjwatson^- that git-annex test-builds fine on armhf and powerpc10:49
Laney+-- utf-8 umbrella (utf-8 cloud looks too stormy)10:51
infinitycjwatson: Awesomesauce.10:53
* Laney wonders why that works, since it still seems to use yesod10:53
cjwatsonIt's moved into a bit that's conditional on webapp10:53
cjwatsoninstead of on assistant10:53
Laneyah10:53
LaneyI see, Assistant.hs:14010:54
dokodobey, u1db currently ftbfs, see http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20130329-raring.html10:54
cjwatsonHm.  I wonder why we don't have a similar non-multiarch tclConfig.sh hack in tcl8.5-dev as in tcl-dev10:54
cjwatsonQuite tempted to add one10:54
* Laney gets back to renaming variables in lightdm10:54
infinityGrr, missed accepting that by a few seconds. :P10:55
xnoxcjwatson: good point. =) should be there.10:57
cjwatsonDoing that now11:00
dokocjwatson, are there that many more?11:00
cjwatsonWell, I found at least one, that's enough for me :-)11:01
dokoI just fear if we add it, then all of daniel chen's patches maybe get reverted in the s-series ...11:02
cjwatsonDoesn't seem like a big deal if they do11:02
xnoxthe less the changes to packages, the quicker we can multiarch tktcl in debian the better.....11:02
xnoxas we do want to drop all patches and just be in sync with debian on most of those packages.11:03
cjwatsonYeah, I'd rather increase the chances of actually getting this transition landed in Debian, TBH11:03
cjwatsonIt's not as if it renders it any less M-A: same11:03
cjwatsonAnd it'll probably help various third-party builds11:04
xnoxand keep us more compatible with the rest of distributions out there....11:05
* xnox doesn't like how interractive parted chokes on uefi-enabled cds dd'ed onto pen-drives.11:06
=== seb128_ is now known as seb128
ScottKinfinity: We have to britney unblock everything now?  Might be worth a mail to ubuntu-release to let everyone know.12:40
cjwatsonI'll do it12:40
ScottKThanks.12:41
infinitycjwatson: dpkg-architecture is in dpkg-dev, do you want to, I dunno, make tk8.5-dev depend on it?12:42
cjwatsoninfinity: Hmm.  tcl-dev and tk-dev don't12:43
infinitycjwatson: Right, that was sort of my point.12:44
cjwatsonWell, I meant the existing ones in the archive (from tcltk-defaults) as opposed to tcl8.5-dev and tk8.5-dev12:44
cjwatsonBut you may be right ...12:44
infinitycjwatson: For package builds, this makes no difference, since dpkg-dev is build-essential, but for random people installing tcl8.5-dev and expecting the config script to work, it won't.12:44
infinitycjwatson: Oh, does tcl-dev do the same wrong thing?12:45
cjwatsonYeah12:45
cjwatsonI'll go fix it all12:45
infinityWell, fixing that would be nice too.  Thanks. :)12:45
infinity(Is there a non-dpkg-arch way to get that string, I wonder?)12:45
cjwatsonDon't think so12:46
infinityActually, wait, tcl-dev isn't MA:same is it, so there's no reason you can't embed that string at build time instead of doing it at runtime.12:46
infinityWhich seems more correct, since it should match the package arch, not the default dpkg arch.12:46
xnoxinfinity: it is.12:46
infinityOh, it is.12:46
infinityI missed the header in my apt-cache.12:46
infinityDrat.12:46
xnoxinfinity: MA & Arch should match between foo-defaults and fooX.Y12:46
cjwatsonYeah, hence this hack.12:47
xnoxotherwise it just doesn't work......12:47
infinityThat hack will not work if your tcl8.5-dev is not the primary dpkg arch.12:47
cjwatsonCorrect12:47
infinityOh well.12:47
infinityCross that bridge when it annoys us for cross-building, I suppose. :P12:48
cjwatsonBut if you're doing that sort of thing I don't think it's excessive to convert to the right path for finding {tcl,tk}Config.sh12:48
infinityAnyhow, if you want to add run-time deps on dpkg-dev, that would be shiny.  If you don't care, I can also pretend not to.12:48
xnoxI am slightly surprised that dpkg-architecture is in dpkg-dev and not dpkg, since I would have thought something like that would be desirable on e.g. all amd64 installs where we auto-enable multiarch out of the box.12:48
infinityxnox: I don't see how the first part of your sentence relates to the second.12:49
cjwatsonIt's irrelevant at run-time12:49
infinitydpkg-architecture has pretty much zero runtime utlity (except when people try to do hacks like this)12:49
cjwatsonEven this isn't really run-time12:49
infinityTrue, it's runtime of a dev package.12:49
cjwatsonThe linker knows about the multiarch path, which is all that's needed12:49
cjwatson(And the odd string embedded in binaries and such)12:50
cjwatsoninfinity: All uploaded, should show up shortly12:50
ogra_infinity, FYI https://wiki.ubuntu.com/Touch/AndroidAutobuilds12:50
xnoxinfinity: ok. libdpkg-perl is only optional, despite being in many seeds. I somehow thought if dpkg-architecture scripts dependencies are all essential, there is no harm moving dpkg-architecture into dpkg. but turns out there is.12:51
seb128if I upload an updated ubuntu-docs package, can it still get in for the release? (we updated the translation template on thursday last week and quite some translation teams worked over the W.E to get the new strings translated)13:00
cjwatsonI think so13:00
seb128great, upload on its way13:00
seb128thanks13:00
dokocjwatson, using dpkg-architecture, and not b-d on dpkg-dev? I mean, it won't file on the buildds ...13:00
cjwatsondoko: Read scrollback :-)13:00
cjwatsonThat's fixed in latest uploads13:00
dokoheh13:00
cjwatsonAnd doesn't need a build-dep, only dep13:01
cjwatsoninfinity: When're we stopping image builds?13:01
cjwatsonScottK: your unblock syntax is wrong - needs to be "unblock SOURCE-NAME/SOURCE-VERSION" as in my mail13:30
ScottKcjwatson: Thanks.  I'll fix.13:31
ScottKFixed.  In my defense, I did that before you sent the mail.13:32
cjwatson:)13:32
cjwatsonStill wrong though13:32
cjwatsonFirst / needs to be a space13:33
ScottKoh13:33
ScottKok13:33
ScottKMaybe that ....13:33
cjwatsonYeah, looks better, thanks13:34
ScottKThanks for setting me straight.13:34
cjwatsonScottK: oh, except you have the versions the wrong way round13:34
ScottKHeh.  Not my morning.13:34
cjwatsonas in, the imageshack-uploader name with the ddtp-translations version and v.v.13:34
cjwatsonnot meaning to call you out in public or anything, sorry :)13:35
ScottKNo problem.13:36
ScottKFixed even more.13:36
Laneyhandily you can copy and paste from queue accept, afaics13:37
cjwatsonScottK: not pushed though ... maybe a clash with my most recent rev?13:39
ScottKYep13:39
ScottKFixing13:39
infinitycjwatson: After that openjdk-7 is done and migrated seems like a decent cutoff to do a respin and uncron.13:39
ScottKFigures.  The ONE time I don't pull "since it's just been a minute since my last change."13:40
* Laney runs13:41
=== mmrazik is now known as mmrazik|otp
=== mmrazik|otp is now known as mmrazik
jbichaseb128: your ubuntu-docs upload doesn't matter if we don't regenerate the language packs, right?14:22
seb128jbicha, not sure, I tested a local build and some page are generated at build time14:59
seb128jbicha, but in any case we are ready for the next langpack update14:59
Davieystgraber: I understand you reviewed juju.. and asked for some fixes.  It's in the queue now. Do you want to take that review or not?15:04
stgraberDaviey: ah, I didn't notice it getting back in the queue. Yep, I'll take a look15:04
Davieystgraber: thanks!15:05
=== smartboyhw_ is now known as smartboyhw
stgraberDaviey: there you go15:33
Davieywoot15:34
Davieysuper stgraber15:34
dobeydoko: can i get a retry for u1db? i just pulled it from bzr, built a source package, updated pbuilder, and built it in there, with no errors :-/15:37
Davieystgraber: I assume you checked suitable break/replaces ^ ?15:40
stgraberDaviey: I think I did last week, anyway, I did a test build + test upgrade here today and it worked, so it should be good15:42
infinitycjwatson: nyquist sorted.  Was a particularly icky and silly bug.16:14
infinitycjwatson: Any traction on pytables?16:14
cjwatsonnyquist> good stuff16:14
cjwatsonpytables> Test-building a really crude fix now16:14
infinity\o/16:15
cjwatsonoverlapping strcpy> ah, yeah, that would cause mass confusiong16:15
cjwatson-g16:15
ScottKIs any of the non-partner stuff in New going to be accepted or should we just reject it all now?16:16
infinitycjwatson: Yeah, there was a lot of tag-team WTFery to get down there.16:16
cjwatsonI was just looking at tegaki-omg-long-package-name16:16
infinityScottK: I just did vala earlier, I might still poke one or two others.16:16
ScottKOK16:16
dokodobey, given back on amd64. but the last retry was on Sat ...16:21
cjwatsondobey: It fails in exactly the same way in a local sbuild instance.  Perhaps try that instead of pbuilder16:29
* cjwatson does a little dance as we get rid of magellanic (old torrent.u.c)16:36
infinity!!16:36
infinityReally?16:36
cjwatsonmagellanic is dead, long live caranda16:37
infinityFuck yeah.16:38
infinityI assume the new machine is all disky and RAMy and CPUy?16:38
cjwatsonNo idea but I'd have hoped so.  It can't be that much worse than mag16:38
infinitymagellanic was a 486, I'm sure.16:39
cjwatsonWell, tegaki-zinnia-traditional-chinese has a giant prebuilt model file in its source which it ships, but it does include a Makefile for rebuilding it from the XML file, and apparently the Debian ftpmasters were happy with tegaki-zinnia-simplified-chinese which is basically the same16:48
cjwatsonSo minded to accept if only because otherwise it's kind of unfairly inconsistent16:49
utlemmingstgraber: around?17:05
dobeycjwatson: but the build depends isn't different for the package, so the same dependencies should be installed in both. why would it fail in sbuild but not pbuilder? that makes absolutely no sense to me.17:05
infinitydobey: Which package is this?17:05
infinitydobey: I missed the context.17:06
dobeyinfinity: u1db17:06
=== cjohnston_ is now known as cjohnston
dobeyinfinity: the tests failed in doko's archive test rebuild17:06
dobeybut they aren't failing under pbuilder17:06
dobeythough i do get similar failures running tests for u1db trunk, on my actual raring system. but it's pretty hard to determine what actually broke and caused the failures, since u1db hasn't changed in the archive since december…17:07
dokodobey, did you check what cjwatson suggested (running in sbuild)?17:07
infinityExplodes here too.17:08
dobeydoko: as soon as i figure out how to do that i guess17:08
dobeydoko: but that doesn't really help, other than knowing that it does fail in sbuild (but not pbuilder)17:08
dobeydoesn't tell me why it fails17:08
infinityShouldn't need sbuild.  You can just grab the chroot tarball, unpack it, chroot in, install build-deps and build.17:08
infinityIf you really can't make it fail in a pbuilder/raring setup, your chroot might be a bit dirty.  You could compare installed packages.17:09
dokodobey, failed in the december test rebuild too ... http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20121221-raring.html17:09
dobeyi wonder what broke it17:12
cjwatsondobey: Might be some other minor difference in the environment.  I believe sbuild is a bit stricter about clearing it out.17:20
cjwatsondobey: In any case, reproducing it locally will let you investigate directly rather than guessing; it usually becomes clear once you find the cause.17:20
xnoxto me it looks like a PYTHONHASHSEED issue, worth a try running tests with 1..10 and see if some of them pass while others fail.17:21
cjwatsondobey: (sbuild has options for "don't purge the chroot if a build fails", so you can schroot in and try finer-grained things.)17:21
cjwatsonPlus, sbuild is just plain more relevant than pbuilder ...17:21
dobeyxnox: right. though hash_randomized is set to 0 in sys.flags here…17:22
dobeycjwatson: sbuild is also just plain more pain that pbuilder (documentation tends to recommend pbuilder, and it's certainly much easeir to set up and get working, especially given that local sbuild and what is on launchpad also differ)17:23
xnoxlooking at the failure somethind does produce the results out of order, might as well test them once sorted.17:23
dokoyes, hash rand. is turned off by default in 2.717:24
xnoxdobey: exacatly how "mk-sbuild raring" is harder than "pbuilder-dist raring create" with "sbuild -d raring foo*.dsc" and "pbuilder-dist raring build foo*.dsc" ??????17:24
cjwatsondobey: *shrug* I use sbuild for everything, I'm not failing to eat my own dog food here17:24
seb128quick release question17:24
cjwatsonI don't find it difficult17:24
dobeyanyway, i'm not trying to argue about sbuild vs. pbuilder or anything. i just want to be able to figure out what is going on here, because the tests work fine in quantal, but not in raring.17:24
xnoxdobey: the distro-builders use sbuild for a reason ;-)17:25
seb128the gtk patch from https://launchpad.net/ubuntu/+source/gtk+3.0/3.6.4-0ubuntu7 (uploaded a week ago) created some scrolling jerkiness for some users, who are suggesting we revert the change for the release17:25
cjwatsonAnd while it's true that local sbuild and LP sbuild differ, in practice they differ much less than any sbuild and pbuilder.17:25
xnoxthus it's good enough arguments as to which one is "better" =))))17:25
seb128the issue is not a blocker either way17:25
dobeyxnox: they also use a different sbuild setup than one can easily create locally17:25
dobeyxnox: and i don't care which one is "better"17:25
seb128would you recommend to rather got for a SRU or upload to raring still?17:26
cjwatsonNot significantly different in the majority of cases, and if you care about that then why on *earth* are you using pbuilder to try to reproduce sbuild problems?17:26
cjwatsonAt the very least try sbuild before asking other people ...17:26
cjwatsonSince in this case it didn't differ, and it also doesn't differ in most others17:26
ScottKseb128: If you're confident you could SRU it, go ahead and upload and do the SRU template in the bug.  We just won't unblock it and then it'll be available if we decide to push it in.17:27
seb128ScottK, ok, thanks17:27
DavieyI've only ever seen the chroot difference between LP's and locally created matter once.  And in that instance, i downloaded the LP tarball and based my build on that, to debug17:28
xnoxdobey: for me it fails utterly different from how it fails in the test rebuild. http://paste.ubuntu.com/5593211/17:29
xnoxdobey: the test-suite failures in the rebuild, seem like one can address them due str != unicode (note comparison of "string" and u"string") and sorting actual before comparing with reference.17:30
dobeyxnox: 'foo' == u'foo' in python 217:31
dobeyxnox: only if the encoding was actually different would it fail17:31
xnoxdobey: true, then I don't understand the first failure here https://launchpadlibrarian.net/137872928/buildlog_ubuntu-raring-i386.u1db_0.1.4-0ubuntu2_FAILEDTOBUILD.txt.gz17:32
xnoxwhitespace?! wtf =)17:32
dobeyno it's not the whitespace. it's that the values are different17:33
jbichais it ok that I marked today's Ubuntu GNOME images as ready for final testing?17:33
dobeyit's not just an ordering issue (though that is part of it)17:33
xnoxright, yeah, there is an extra one. missed it.17:34
xnoxdobey: I have just created a fresh pbuilder-dist raring create, and it fails in it as well, this time with failures as in the rebuild. Maybe your pbuilder chroot got something stray left in it? e.g. dropped essential packages and the like do not get autoremoved... or maybe it's out of date w.r.t. build dependencies.17:39
xnoxwith pbuilder-dist raring build u1*.dsc17:39
xnoxdobey: so it's not even sbuild vs pbuilder problem.17:39
dobeyso it's sqlite that broke17:40
infinitygtk?  Really?17:42
ScottKinfinity: I told him to go ahead and upload for SRU and we'd just not unblock.17:43
infinityAhh.17:43
infinityWell, we can unblock if there's a respin and we feel the urge.17:43
infinity(And we're respinning tonight anyway, so we'll see)17:43
ScottKRight.  It'll be there if it seems we want it.17:44
infinityScottK: I need to escape this network for a bit, are you going to review and accept that gtk?17:48
ScottKIt's unlikely I'll feel like I know enough to decide, but I'll look at it and accept if I'm comfortable.17:48
infinityCheck.  If no one else gets to it, I will later.17:48
ScottKI can ask someone else to review if not.17:48
seb128infinity, ScottK: the gtk upload is basically "revert to what we had until one week ago"17:54
seb128if you debdiff 0ubuntu6 and 0ubuntu8 you will just get the changelog diff17:54
seb128the bug the patch tried to fix was already there in quantal so it's not a new bug or recent regression we tried to address17:55
ScottKThanks seb12818:03
seb128ScottK, thanks to you guys for looking at it ;-)18:03
ScottKOK.  Done.18:04
dobeydoko: ok, i've filed bug #1171568 for the regression in sqlite18:30
ubot2Launchpad bug 1171568 in sqlite3 (Ubuntu) "libsqlite3-0 3.7.15 breaks u1db tests" [Undecided,New] https://launchpad.net/bugs/117156818:30
phillwis the cron off?20:27
ScottKThere's a rebuild planned for tonight.  Dunno if it's via cron or not.  (trying to answer what is, I think, your actual question)20:28
phillwthanks ScottK, yeah, that was the question, lubuntu still shows 21st :)20:29
slangasekcron is off, yes20:38
slangasekso rebuilds are manual at this point20:38
slangasekI thought they were already run though, maybe I misunderstood?20:38
* slangasek checks nusakan20:38
phillwslangasek: lubuntu shows 21st on my browser. Can someone else check.20:40
slangasekcorrect; the question on my part is whether that's because a build is pending, or because a build failed20:40
infinitycron is off, unless stgraber failed at that.  I'll kick off a bunch of rebuilds before bed, unless someone in a more sane timezone wants to do that for me.20:40
slangasekinfinity: "before bed" - are we currently waiting for some publication before kicking them off?20:41
ScottKSince pitti doesn't seem to be around, is there anyone who has a minute to examine a possible fix for a jockey problem before I take a cleaver to it to fix something?20:42
ScottKIf you can give me half an hour, I think I can have jockey working for wl again.  That may just affect Kubuntu though.20:42
infinityslangasek: gtk+3.020:42
slangasekinfinity: ok20:43
infinityslangasek: The armhf build is just finishing up, and I've unblocked it in britney.20:43
slangasekScottK: where jockey is concerned, by instruments are no less blunt20:43
slangaseks/by/my/20:43
ScottKOK.20:43
infinityslangasek: If you're cool with a respin of The World, I can pretend not to care until the morning.20:43
slangasekinfinity: I'm not sure what the current recommended method of respinning the world is - pointer?20:44
infinityslangasek: Colin and I have just been copying and pasting from crontab.20:44
slangasekok20:44
infinityThe old "pipeling" no workie since the python rewrite, and neither of us has bothered to do anything cooler just yet.20:44
slangasekany ordering constraints?20:44
infinitys/pipeling/pipeline/20:44
infinityslangasek: Just jamming it all in at once should more or less DTRT with locking.  But if you want to be clever, you can try to keep, say, the ARM and PPC builders full. *shrug*20:45
infinityslangasek: I found that, roughly, running two sessions, where you go top down in one, and bottom up in the other, and meet in the middle, seems to keep everything busy.20:46
slangasekI could just run everything in the background and trust the locking :)20:48
slangaseks/the background/parallel/20:48
ScottKTesting my jockey fix now.20:48
infinityslangasek: That should generally DTRT.20:48
=== seb128_ is now known as seb128
ScottKMeh.  Trickier than I thought.  Getting a bigger hammer.20:59
ScottKDid we stop making the Kubuntu powerpc image on purpose?22:00
ScottKSomeone's actually testing it, so it might be nice to have one less than three weeks old.22:00
ScottK(or point me to a failure log please)22:00
dokoScottK, infinity: the libfilesystem-ruby source should be removed, the new kid on the block is ruby-filesystem22:32
phillwScottK: you can blame smartboyhw. He told me that your PPC tester had lost his charger for the laptop he had and asked if our lubuntu PPC testers would assist. If it is too late for a re-spin, i will cancel the request.22:41
ScottKNo, I'm in favor of testing if we can get a current image.22:41
ScottKWhat he said was correct.22:42
phillwScottK: and 'blame' is meant with a smile, he is a dedicated tester team lead and is quite entitled to ask other teams for help, you guys on kubuntu helped lubuntu out a lot in our early days... testers repsond to any SOS22:43
ScottKAh.  OK.22:43
ScottKslangasek: Can you tell why Kubuntu PPC is out of date by several weeks?22:45
phillwScottK: ppc installer is a pain, but if you get a respin, we may be able to test it to the level that lubuntu uses for a desktop system.22:45
ScottKYeah22:45
slangasekScottK: looking to see22:46
ScottKThanks.22:46
phillwScottK: Whilst I 'can' edit test suites, I'd ask you to to set it to the same as lubuntu uses. There is more chance of getting a passed by the skin of teeth, with release notes.22:47
phillwI'm not kubuntu team :)22:48
slangasekScottK: no obvious cause; etc/default-arches appears to be correct, and there's no indication of a livefs build attempt22:51
ScottKslangasek: Someone may have stopped it due to a lack of testers.  Now we've got one.  Would you please give a respin a shot?22:52
phillw+122:52
slangasekScottK: I'm not seeing *where* it's disabled; something is preventing it from being built, I'd like to get to the bottom of that22:52
ScottKOK22:52
ScottKThanks22:52
slangasekit's not a deliberate change, that would be done in etc/default-arches22:52
slangasekso there's a bug somewhere22:52
ScottKI think the jockey problem is release notes material unless pitti makes a magical appearance.22:53
slangasekohwait, maybe my local branch is out of date; let's see22:53
slangasekmmm still no22:54
infinityslangasek: It's disabled in production.  Was done during the last milestone and not reverted.22:55
slangasekah.22:55
* slangasek reverts22:56
slangasekmmm, there's an edubuntu diff as well22:56
slangasekok, firing a kubuntu powerpc build22:57
infinityThe edubuntu diff should stay.22:57
phillwtalk about re-spin the world? :)22:58
ScottKFSVO world22:59
slangasekso as it happens, royal seems to be doing a whole lot of nothing23:01
slangasekah, no, it's really just that slow compared to the others :/23:03

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