/srv/irclogs.ubuntu.com/2015/12/10/#ubuntu-devel.txt

=== cpaelzer is now known as cpaelzer_afk
=== _salem is now known as salem_
=== salem_ is now known as _salem
pittiGood morning05:40
pittiLaney: oh, one of the armhf nodes still had the regressing lxcfs installed which caused the timeouts with systemctl daemon-reload; downgraded now and retried everything06:07
Mirvgood morning06:19
Mirvpitti: do you know what needs to be done for the transition still?06:22
pittihey Mirv06:23
pittiMirv: we made a lot of progress last night, but I think it now hinges on aptdaemon not working properly with apt 1.106:23
Mirvpitti: ah, the apt transition is still there, ok06:23
pittiMirv: and the whole Qt transition depends on the apt transition06:23
MirvI've kindly asked Kubuntu to not upload a new KDE since that could set as back for another week06:24
Mirvright, now I saw the right parts of the backlog06:31
=== nudtrobert1 is now known as nudtrobert
pittixnox: just stumbled over missing "git" on s390; impressive dependency chain :)07:30
pittigit needs subversion needs ruby, wow07:30
pittialthough ruby-defaults and ruby2.2 ought to be there now07:31
pittihm, I can install ruby and ruby-dev on the autopkgtest system, but apparently the buildd can't07:33
xnoxpitti, Mirv we should have been building kde for s390x in the bootstrap archive.08:50
* pitti fixes apport for apt 1.108:51
apwdoko, i am suddendly seeing build failures (for the kernel) on arm64, i am suspicious that i have a binutils issue: https://launchpadlibrarian.net/229533923/buildlog_ubuntu-xenial-arm64.linux_4.3.0-3.12_BUILDING.txt.gz10:03
apwdoko, the previous build was identicle souce in arm64 and built just fine10:04
=== cpaelzer is now known as cpaelzer_afk
=== _salem is now known as salem_
Mirvpitti: did mv_o have a chance to look at the aptdaemon failures?11:36
pittiI haven't heard anything yet; mvo ^11:36
pittimvo: would be nice to know if that's ignorable for now, or serious enough to block propagation11:36
mvopitti: I did not had a chance, sorry11:41
mvopitti: can you please give me the link again11:42
pittimvo: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/a/aptdaemon/20151209_192259@/log.gz is the log11:42
pittimvo: i. e. http://autopkgtest.ubuntu.com/packages/a/aptdaemon/xenial/amd64/11:42
mvopitti: its just the cdrom test, so go ahead and promote and we will figure out the reason once there is a bit of time11:43
pittimvo: test_archives_lock (tests.test_lock.LockTest)11:44
pittimvo: error code 100 is "apt error", that doesn't seem to be CD-ROM only?11:44
pittiErr:4 copy:/tmp/adt-run.z6d472/build.z7b/aptdaemon-1.1.1+bzr982/tests/repo ./ Packages11:44
pitti  Hash Sum mismatch11:44
pittioh, perhaps just that11:44
pittibut that seems to happen consistently11:45
mvopitti: hm, right. need to look but in a meeting11:46
pittimvo: at least it looks likely to be a test-side problem11:46
mvopitti: I can reproduce I suspect a test issue because the new apt is stricted and its less easy to fake data11:49
pittimvo: right; ok, so are you ok with force-badtest'ing it and let the new apt land?11:50
mvoyes11:53
pittimvo: ack, thanks for the review11:53
* pitti commits hint11:53
pittimeh, this is also a regression: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/u/ubuntu-release-upgrader/20151210_062305@/log.gz11:55
pittiapparently with new python-apt11:55
jamespageany archive admins around? I need a binary only promotion of libboost-random-dev to main to get ceph 9.2.0 building...12:04
jamespagethat will pull in libboost-random1.58-dev libboost-random1.58.012:05
pittijamespage: ah, so these two need to go to main too12:05
jamespagepitti, yup12:05
pittijamespage: done12:06
jamespagepitti, thankyou!12:06
pittiMirv, xnox: apt and friends are valid candidates now, but still installability errors :(12:20
Mirvhmm12:24
Mirvpitti: do I parse update_output correctly that it'd claim big installability problems on amd64 too? I don't see problems on my xenial lxc if I enable -proposed, it seems I can install pretty much install + upgrade all of Qt / KDE etc12:31
pittiright, not arch specific12:34
pittisomething in that list is still not built against the new apt12:34
pittior this needs to be hinted, not entirely sure12:34
Laneyqtdeclarative is not a candidate12:41
pittiah, qtmir-gles tests?12:41
pittiindeed, FTBFS against new Qt?12:42
pittihttps://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/q/qtmir-gles/20151210_062159@/log.gz12:42
pittiMirv: ^ ?12:42
pittioh, but apparently against the whole stack, like in the third on http://autopkgtest.ubuntu.com/packages/q/qtmir-gles/xenial/amd64/12:42
pittiso, just insufficient build deps12:42
Mirvpitti: yes, whole stack12:42
Laneyprobably have the line from yesterday12:43
MirvI guess they should be tightened12:43
pittiok, hint it is, let's not reupload just to tighten build deps12:43
Mirvmeanwhile I'll file a bug for it12:43
pittihinted12:44
Mirvpitti: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtdeclarative-opensource-src also shows non-hinted random timeouts with kaccounts-integration12:45
pittiShould wait for kaccounts-integration 4:15.08.2-0ubuntu1 test, but forced by pitti12:46
pittiMirv: already hinted12:46
* Mirv re-learns to read12:46
pittia lot of tech debt when this lands :)12:46
pittiMirv: yeah, sorry, it's not immediately under that line, easy to miss12:46
LocutusOfBorg1pitti, syncpackage pbuilder pretty please LP: #152408313:08
ubottuLaunchpad bug 1524083 in pbuilder (Ubuntu) "Sync pbuilder 0.221.2 (main) from Debian unstable (main)" [High,Confirmed] https://launchpad.net/bugs/152408313:08
LocutusOfBorg1and if you can lp: #152431513:08
ubottuLaunchpad bug 1524315 in boinc (Ubuntu) "Sync boinc 7.6.20+dfsg-4 (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/152431513:08
=== pat_ is now known as Guest15515
Mirvpitti: still some but a lot less uninstallable?13:26
Mirv(or claimed as such)13:26
Mirvapt seems pretty happy about installing those for me, so far13:27
MirvI found unbuilt arm64 plasma-workspace, rebuilding https://launchpad.net/ubuntu/+source/plasma-workspace/4:5.4.3-0ubuntu1/+build/833058013:29
MirvI triggered a chain of ~30 KDE packages for arm64 before I landed Qt 5.5 since they had been stuck since beginning of November13:29
Mirvcalligra armhf FTBFS related to the poppler transition? xnox?13:33
Mirvxnox: and gdcm not considered13:35
Mirvpitti: related to apt, openscap ICE on ppc64el, rebuilding13:38
mterrypitti, can I have some help deciphering update-excuses?  I'm trying to get the new gsl to land.  the update_output.txt file indicates there's something going on with cpl-plugin-naco and slgsl.  But I'm not sure what it is13:41
mterryGranted, the naco plugin is also held in proposed, because autopkg isn't testing with the latest gsl...13:42
mterryIs that a circular loop?  Or did it just test with the old gsl and hasn't been retested yet?13:43
Mirvnot sure how much it helps, but I managed to get successful builds for ppc64el: openscap lxqt-panel arm64: user-manager systemsettings plasma-framework (next: plasma-desktop) s390x: libqtxdg13:56
mterrydidrocks, thanks for looking at the s390x MIRs14:01
didrocksmterry: yw! there are still 2 to be done14:07
didrocksmaybe doko or you have time for them?14:07
dokoyeah, I should have time ...14:08
didrocksmterry: also look if they were pre-promoted. Some were without any message on the bug report14:08
didrocksdoko: ^14:08
mterrydidrocks, yeah I saw your comments14:09
didrocksI trust thus xnox to fix things quickly then :)14:09
pittiLocutusOfBorg1: pbuilder synced; for boinc, the debian changelog does not mention the ubuntu changes at all, so doesn't this need merging?14:12
mapreripitti: thanks for pbuilder! ♥14:12
pittimapreri: no worries, thanks to you for making the package syncable, that's fantastic!14:13
pittiMirv: hm, apt uninstallablity is still the same?14:13
pittiMirv: right, the KDE uploads failed on arm64 on several attempts, but why do they block apt?14:13
Mirvpitti: I don't know if they block apt, I'm just flexibly interpreting problems on excuses or update_output page to be possibly related to the migration14:14
pittipete-woods: any idea about https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/p/python-dbusmock/20151210_061403@/log.gz ? I didn't see that in my local test14:15
Mirvthe calligra armhf is actually an ICE https://launchpadlibrarian.net/229169305/buildlog_ubuntu-xenial-armhf.calligra_1%3A2.9.7-0ubuntu8_BUILDING.txt.gz so I guess it could be retried. calligra is among else listed in the trying easy from easyhinter portion of update_output.14:15
pittimeh, and poppler is also part of that transition14:16
pittiand rather old14:16
pittiit seems folks have become very sloppy with actually finishing what they start :(14:16
pittimterry: so update_excuses says that the new gsl breaks cpl-plugin-naco indeed14:19
pittiMirv: so it seems it depends on the new gsl but doesn't declare that14:19
mterrypitti, I think that's a lie?14:19
mterrypitti, it's hard because they changed SONAME but not package name14:20
Laneywho's become sloppy?14:20
Laneypoppler got dragged back from almost finished by s390x14:20
Laneyand was entangled into the parallel qt and apt transitions14:20
mterrypitti, right now gsl being stuck in proposed is making a lot of broken packages (because they build against proposed SONAME, land in release, and expect that same SONAME)14:21
pittimterry: no, not a lie, the new gsl is indeed not installable with the old naco14:21
mterrypitti, right, but the naco in proposed that it does work with is being stuck for bogus reasons (it was tested against release pocket version of gsl)14:21
pittiso, let's try to test the proposed naco against the proposed gsl14:22
mterrypitti, exactly14:22
pittimterry: yes, as I said -- it doesn't depend on the -proposed gsl, so it doesn't get tested against it14:22
mterrypitti, right I get that logic.  That's why I'm coming to you for manual futzing  :)14:22
pittimterry: started now; if that succeeds, it should unblock naco and thus gsl14:23
mterrypitti, Ubuntu got a botched version of the debian transition for gsl14:23
mterrypitti, awesome thanks14:23
pittiah, that's why14:23
pittimterry: so we aren't hiding a soname change without package rename with this, but we fix it?14:23
mterrypitti, that's the idea (2.0 had package name transition, 2.1 bumped soname to match -- but in debian, 2.0 never hit testing / rdeps didn't seem to adjust for it until 2.1)14:24
mterrypitti, but in Ubuntu, we had a delta for 2.014:24
pete-woodspitti: I've seen that before when you run the tests individually (e.g. ./tests/foo.py)14:25
mterrypitti, so we didn't get 2.1 in a timely fashion, but we got all of Debian's rdep changes to require >=2.014:25
pete-woodsI guess there's some magic setup in the main setup.py that registers a mainloop or something14:25
mterrypitti, (we could fix this in Ubuntu by adding lots of deltas on >=2.1, but I figured it was easier to accept one time pain than that)14:26
pittimterry: passed now, that's better14:28
mterrypitti, yay14:29
mterrypitti, something seems weird about that migration logic though -- new naco passed its autopkg test with new gsl.  But we blocked both new packages because naco didn't pass with old gsl -- why would we care there?  (I get why it was tested with old gsl, but seems like we should ignore that specific test result when considering gsl promotion)14:30
pittimterry: because neither package can be promoted individually, and since the new naco doesn't dependd on the new gsl it's not attempted to be promoted as a group14:31
pittimterry: that "botched transition/missing dependency" is a case for manual promotion/review indeed; not sure if that can be formalized14:32
mterrypitti, sure.  But the migration script has enough information here to know that it ought to treat them as a group.  But yeah, maybe this case doesn't come up except in broken cases14:32
pittimterry: right, it happens seldomly only; normally dependencies (particular for library transitions) DTRT14:33
mterrypitti, well thanks for setting this one straight -- this was an annoying transition14:33
pittimterry: thanks for grinding through it :)14:35
mapreriin ubuntu this worked, can somebody try a retry? https://launchpad.net/ubuntu/+source/cowdancer/0.75/+build/825496014:45
mapreris/ubuntu/debian/, clearly....14:45
mapreripitti: ↑14:45
pittimapreri: kicked14:46
maprerithx14:46
Mirvok plasma-desktop is building for arm64 too now14:46
maprerithe launchpad build farm is so scary nowadays, you upload a thing, 2 seconds later is already building14:46
pittimapreri: +1 :)14:47
pittiand there's lots of capacity too (for most arches)14:47
mapreriI recall the times where for a ppa build you had to wait nearly day in the worst case14:48
mapreria retry of a failed ppa build, that is14:48
mapreriok, failed again, anyway14:48
mapreri"* '/' is not mounted, something is wrong with the system or the code" — meh14:49
flexiondotorgdidrocks, Thanks for updating plymouth for Ubuntu MATE. Much appreciated :-)14:50
dobeypitti, Mirv: what's up with proposed migration btw? i see stuff as "valid candidate" on excuses for some time now, but still not migrated. is it just incredibly slow atm?14:54
pittidobey: no, but it still renders stuff uninstallable14:54
pittidobey: that's "phase 2" of p-m, on http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt14:55
dobeyoh, hmm :-/14:55
pittiapt+poppler+three dozen Qt packages, some KDE interspersed, yummy ;/14:55
pittimterry: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#cpl-plugin-naco \o/14:56
pittimterry: it's  being promoted14:57
mterrypitti, heh, great14:57
pittimterry: hm, but not http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#gsl itself yet14:58
mterrypitti, update_output.txt also mentioned slang-gsl (from slgsl)14:59
mterrypitti, but I wasn't sure why there14:59
pittimterry: that's already promoted14:59
pittimterry: so maybe that needs another rebuild against the new gsl?14:59
dobeypitti: yeah, i'm mostly concerned about ubuntuone-credentials at the moment. i guess it's just in an unlucky position, dependency-wise15:00
mterrypitti, no the promoted version should be built against new one (it snuck in because it didn't have autopkgtests and this was a silent transition)15:00
dobeyoh, and i guess it just made it through. whee :)15:01
mterrypitti, wait...15:01
mterrypitti, no..  it's building against some ancient gsl version (looking at build log)15:01
mterrybut this was a couple days ago15:01
LocutusOfBorg1[15:12:23] <pitti> LocutusOfBorg1: pbuilder synced; for boinc, the debian changelog does not mention the ubuntu changes at all, so doesn't this need merging?15:01
LocutusOfBorg1it does15:01
LocutusOfBorg1http://metadata.ftp-master.debian.org/changelogs/main/b/boinc/unstable_changelog15:01
pittihttps://launchpad.net/ubuntu/+source/qtbase-opensource-src/+publishinghistory !15:01
pittiMirv, Laney, xnox ^15:01
LocutusOfBorg1just on a older entry :)15:02
pittiand apt too15:02
pittiyippie!15:02
Laneypitti: what changed?15:02
seb128pitti, how did that happen?15:02
seb128britney got slippering fingers? ;-)15:03
* pitti watches two metric tons of packages land in xenial15:03
pittifinally enough ignored test regressions and the arm64 rebuilds from Mirv15:03
seb128wasn't s390 blocking things as well?15:03
pittiseb128: xnox was busy :)15:04
seb128no15:04
seb128he's sitting at the table doing "wth" with Laney15:04
pittinow we just need to get out of the Haskhell and then -proposed should become halfway manageable again15:04
Laneywe thought it was still far off15:04
pittiseb128: well, I wasn't aware of any remaining blockers, what was left?15:04
pittithis morning we were at qtmir-gles and some leftover arm64 FTBFS15:05
LocutusOfBorg1FWIW I uploaded ghc-testsuite a few hours ago15:05
seb128xnox though that s390 had libreoffice depending on poppler triggered kde things15:05
cjwatsonI'm gradually working my way up the Haskell stack15:05
LocutusOfBorg1seb128, can I ask you a really difficult question? the problem is your keyutils sync. it didn't went to -release, because it didn't build everywhere. Now a package depending on it, is failing to build from source where it is built, and building correctly where it failed (because the older one was picked). Since nothing in the code should have changed, I'm lost, maybe you can consider disabling again the testsuite?15:05
pitticjwatson: ah, thanks; is that mostly doing build retries in mostly the right order?15:05
seb128LocutusOfBorg1, somebody should fix it15:06
cjwatsonpitti: partly, some manual rebuilds, and there are some bits still broken in Debian15:06
seb128LocutusOfBorg1, that's not a difficult question15:07
LocutusOfBorg1seb128, I lost half the day without any clue15:07
Mirvpitti: !!!15:07
LocutusOfBorg1but disabling the testsuite again should be the best fix15:07
LocutusOfBorg1do you think you can sponsor it?15:07
* Mirv hugs pitti xnox Laney mterry + everyone15:08
* pitti hugs Mirv back15:08
mterry:)15:08
LocutusOfBorg1seb128, https://launchpadlibrarian.net/187477970/keyutils_1.5.9-5_1.5.9-5ubuntu1.diff.gz something like that15:08
pittimême pas mal !15:08
Laneybritney traded uninstallables15:09
pittiLaney: on s390?15:10
cjwatsonIt'll do that15:10
Mirvsil2100 ^15:10
sil2100Is it DONE?15:10
sil2100Did it happen?!15:10
cjwatsonIn the sense that unity8 is about to be uninstallable on xenial/armhf, yes :P15:11
Laney:)15:11
seb128cross arch trading?15:11
cjwatsonYes15:11
sil2100\o/15:11
pittiuh, the "Newly uninstallable packages in testing"?15:12
seb128:-(15:12
pittithat's a loot15:12
seb128"fun"15:12
geoffthey, would someone who can see private bugs mind summarizing #723515? it's mentioned in libhugetlbfs's debian/rules15:12
pittiI didn't know that britney allowed that kind of trading15:12
geofftand I'm wondering if that can be dropped15:12
seb128is it supposed to?15:13
seb128or is that a bug?15:13
cjwatsonit's a misfeature15:13
Mirvhmm15:13
cjwatsonactually, it's *supposed* to check per-arch15:15
cjwatson                # if the uninstallability counter is worse than before, break the loop15:16
cjwatson                if ((item.architecture != 'source' and arch not in new_arches) or \15:16
cjwatson                    (arch not in break_arches)) and len(nuninst[arch]) > len(nuninst_comp[arch]):15:16
cjwatson                    better = False15:16
cjwatson                    break15:16
cjwatsonmaybe easy hints are different15:16
cjwatsonI think they may be :(15:17
cjwatsonsee is_nuninst_asgood_generous15:18
Mirvso ubuntu-ui-toolkit is stuck due to s390x issues, which makes the phone world not happy yet and which was the interesting trade done15:31
pittimdeslaur: playing notify bot, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#php5 causes a lot of regressions, so it's stuck; what's worse is that they all look different :(15:33
cjwatsonlooks like https://launchpad.net/ubuntu/+source/ubuntu-app-launch/0.5+15.10.20150817-0ubuntu1/+build/8382760, but is that really just "fails when rebuilt with current glib" or similar?15:34
pitticoreycb: FYI, new python-oslo.log needs a bunch of universe b-deps so it doesn't build: https://launchpad.net/ubuntu/+source/python-oslo.log/2.0.0-1ubuntu1/+build/837083815:35
coreycbpitti, those depends should be in main.  i've not been able to figure out why they're stuck in proposed though.15:36
cjwatsonI think u-a-l probably wants something like http://paste.ubuntu.com/13897054/15:37
Mirvxnox: ubuntu-app-launch ftbfs on s390x due to warning treated as error. that's a pre-requirent for building autopilot which is one of the blockers keeping ubuntu-ui-toolkit in -proposed15:37
cjwatsonMirv: ^-15:37
pitticoreycb: uh, indeed15:37
Mirvcjwatson: right, I read just after pressing enter15:37
coreycbpitti, like this one, it builds ok but stuck in proposed: https://launchpad.net/ubuntu/+source/python-oslo.utils15:37
pitticoreycb: sorry, they are uninstallable, not in universe15:38
* cjwatson tries it on amd6415:38
pitticoreycb: https://launchpadlibrarian.net/228297733/buildlog_ubuntu-xenial-amd64.python-oslo.log_2.0.0-1ubuntu1_BUILDING.txt.gz15:38
pitti# apt-get build-dep python-oslo.log15:40
pitti: Build-Depends-Indep dependency for python-oslo.log cannot be satisfied because candidate version of package python-oslo.serialization can't satisfy version requirements15:40
pitticoreycb: ah, it has python-oslo.serialization (>= 1.10.0), but only 1.9.0-2 is available15:41
pitticoreycb: 1.9.02 is in debian unstable, 2.0.0-1 is in experimental15:42
pitticoreycb: did you merge the others from experimental too? i. e. shoudl the exp version be synced?15:42
coreycbpitti, I think the new oslo.serialization is stuck in proposed.  I think the real blocker starts with oslo.utils (see link above)15:42
coreycbpitti, oslo.utils is building ok but stuck in proposed and I don't see any update excuses issues15:42
pitticoreycb: hm, but builds are done against -proposed15:43
coreycbpitti, odd15:43
pitticoreycb: I'll just retry again, it seems they all interlock on each other then15:43
coreycbpitti, yes they are, thanks15:43
pittiah right, o-serialization is also depwait15:43
pitticoreycb: btw, please document ubuntu changes in changelogs; "upload to xenial" is empty contents15:44
pitti(as that's quite clear from the other parts of the changelog already)15:44
pittiand there have been no previous ubuntu changes15:44
coreycbpitti, ok. yeah that was a weird situation where it could have been a sync but hadn't yet been uploaded to experimental.15:45
cjwatsonMirv: yep, same failure on amd6415:45
pittithis makes it hard to see what we changed, what bug refs are, etc.15:45
pitticoreycb: oh, ok; please use ~fakesync or ~build1 or something then15:45
coreycbpitti, ok15:45
pittihm, reubild didn't help15:45
didrocksflexiondotorg: yw! :)15:47
pitticoreycb: so https://launchpad.net/ubuntu/+source/python-oslo.utils/3.0.0-1ubuntu1/+build/8370376 builds python-oslo.utils, but apt-cache policy python-oslo.utils doesn't show it (in -proposed); WTH15:48
juliankmvo and/or anyone who cares: I'm right that you'd like to have stars in gnome-software when switching to it, right? hughsie thought about removing star ratings, I wrote that I think you still want it15:49
pittiit's like someone removed the binary15:49
pittiit's not in the binNEW queue15:50
coreycbpitti, hmm, fwiw I may be hitting the same issues with the cloud archive staging ppa15:50
juliankOh, APT 1.1 has passed proposed :)15:50
pittihttps://launchpad.net/ubuntu/xenial/amd64/python-oslo.utils/3.0.0-1ubuntu1 - Status: superseded15:50
pitticjwatson: ^ any idea about that?15:50
pitticjwatson: is that from binary package removal or so?15:50
pittithe binaries clearly have been built, are not in binNEW, but are missing from the archive (http://paste.ubuntu.com/13897353/)15:51
cjwatsonI'll look in a minute, I just Ctrl-q'ed my browser by mistake :P15:51
pitticjwatson: uh, I hope you have tab restoration enabled15:53
cjwatsonsure do15:53
cjwatsonpitti: I think that was possibly double-override-bug - have copied back in15:53
pitticjwatson: cheers15:53
cjwatsonMirv,tedg,mterry: any chance we could please get https://code.launchpad.net/~mterry/ubuntu-app-launch/fix-ftbfs/+merge/279322 landed, perhaps in isolation so that we can get past this cluster of problems?15:55
tedgOh, sure, I didn't realize it was blocking anything.15:56
tedgGot a couple meetings and then I can do it after that.15:57
cjwatsonthanks15:58
seb128juliank, thanks for the rating comment15:58
seb128juliank, do they want to replace it with something else?15:58
juliankseb128: I'm not sure what it was used for, I don't think they had rating data. But he'll keep the widget in now, and rely on plugins to do the right thing.15:59
seb128k15:59
juliankseb128: hughsie now added stuff like "available in your language" "integrated into your desktop" "has documentation"16:01
juliankI still think stars may be useful, though16:01
seb128yeah16:01
seb128rating&reviews are useful16:01
seb128and every other platform have those16:02
seb128it's a bit weird they remove that16:02
mvojuliank: yeah, I think we want ratings&reviews, there is even a git branch iirc by robert ancil16:02
juliankYes16:02
juliankhttps://git.gnome.org/browse/gnome-software/log/?h=wip/rancell/ubuntu-ratings16:02
Mirvtedg cjwatson: I can put it building into a silo16:10
cjwatsonMirv: that sounds like a good plan16:11
seb128LocutusOfBorg1, does https://launchpadlibrarian.net/187477970/keyutils_1.5.9-5_1.5.9-5ubuntu1.diff.gz still apply/would work?16:17
Mirvtedg: mterry cjwatson: ok it's building and amd64 + ppc64el already successful, ticket https://requests.ci-train.ubuntu.com/#/ticket/771. please follow up since I'm in a bus already.16:25
LocutusOfBorg1seb128, the testsuite is failing, so I presume it works16:30
LocutusOfBorg1I can try16:30
seb128LocutusOfBorg1, k, thanks16:32
seb128those issues don't happen in Debian?16:32
LocutusOfBorg1http://paste.ubuntu.com/13898370/16:33
LocutusOfBorg1seb128, according to the changelogs between 5 and 8, many different debian kernels have issues16:33
LocutusOfBorg1and debian disabled tests in those revisions16:33
LocutusOfBorg1so I presume also Debian is broken with some kernel combos16:33
LocutusOfBorg1Let's see how my costamagnagianfranco/costamagnagianfranco-ppa behaves in the build16:34
seb128hum16:37
seb128diff doesn't apply16:37
LocutusOfBorg1the one above?16:37
seb128I wonder if pastebin screwed new lines or something16:37
LocutusOfBorg1damn yes16:37
LocutusOfBorg1http://paste.ubuntu.com/13898496/16:37
LocutusOfBorg1does this one work?16:37
LocutusOfBorg1the problem wasn't pastebin, but that I copy-pasted from vim :)16:38
seb128better16:38
Mirvcjwatson: ah what I was hoping for before regarding multiple uploads in proposed was that LP would close the bug with the whole changelog leading to the fix, not just the last upload. but I went through the bugs now like bug #1502883 copy-pasting the relevant changelog manually.16:38
ubottubug 1502883 in qtdeclarative-opensource-src (Ubuntu) "Impossible to pull to refresh scopes with Qt 5.5" [Undecided,Fix released] https://launchpad.net/bugs/150288316:38
Mirvbut I think I've tried that using -v when building doesn't help there either16:39
seb128LocutusOfBorg1, sponsored16:39
LocutusOfBorg1thanks!16:39
LocutusOfBorg1I uploaded arrayfire a few seconds ago on debian16:39
LocutusOfBorg1https://buildd.debian.org/status/package.php?p=arrayfire&suite=unstable16:39
LocutusOfBorg1maybe on the next dinstall it will just work!16:39
LocutusOfBorg1btw, I drafted a MOTU application https://wiki.ubuntu.com/CostamagnaGianfranco/MOTUApplication16:41
LocutusOfBorg1I had many different sponsors ~10 and ~100 uploads sponsored16:43
LocutusOfBorg1and they are low just because I maintain a no-delta policy from Debian for my packages :)16:43
Odd_BlokeIs UDD being turned on for xenial at some point?16:50
slangasekpitti: btw, don't know if you've seen LP: #1524480... the plymouth breaks: are tickling an extant bug in the lubuntu theme package16:50
ubottuLaunchpad bug 1524480 in lubuntu-artwork (Ubuntu) "package plymouth 0.9.2-3ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1" [High,Triaged] https://launchpad.net/bugs/152448016:51
slangasekOdd_Bloke: according to cjwatson's mail to ubuntu-devel, it seems not; I would really prefer to have it turned on, imperfect as it is, given that a git replacement is not on the horizon16:51
Odd_BlokeThanks; I thought that's what I'd read but I couldn't think where I'd seen it to go and check. :p16:53
seb128slangasek, hey, do you have an opinion on samba versions for the LTS? or do you know who else might have?16:53
slangasekseb128: I do not, sorry16:56
seb128k :-/16:56
pittislangasek: ah, will look at that with didrocks tomorrow, thanks17:00
pittislangasek: (dealing with s390 ATM, and EOD, sorry)17:00
slangasekpitti: no problem17:00
didrockssame here, dealing with google code in student, will look at it tomorrow17:01
seb128what's the right way to merge a git branch on launchpad?17:23
seb128e.g equivalent of "bzr merge lp:~user/project/branch"17:23
cjwatsongit remote add CONTRIBUTOR lp:~CONTRIBUTOR/PROJECT; git remote update CONTRIBUTOR; git merge CONTRIBUTOR/BRANCH17:26
cjwatsonor something like that17:26
cjwatsonat some point we'd like to add a merge/ ref namespace for all the active merge proposals into your repository, which would make that easier17:27
cjwatson(github has a pull/ namespace; similar idea)17:27
seb128cjwatson, thanks17:28
seb128cjwatson, are mps supposed to be closed if you pull your branch into master and push that?17:28
cjwatsonseb128: yes17:28
cjwatsonI did merge detection in ~June17:29
seb128merge17:29
seb128but not pull/push?17:29
seb128https://code.launchpad.net/~seb128/geonames/+git/reviewchanges/+merge/28004417:29
cjwatsonwhatever :)17:29
seb128didn't close17:29
cjwatsongit merges are often fast-forward17:30
cjwatson== pull17:30
seb128I guess I pushed at the wrong place :-/17:30
cjwatsonlet me check17:30
seb128hum, no17:30
seb128https://git.launchpad.net/~geonames-dev/geonames/+git/geonames/log/?h=debian17:30
seb128has it17:30
cjwatsonlet me check17:30
seb128thanks17:31
cjwatsonBTW you should just use ~seb128/geonames - no need to add a repository name17:31
seb128k17:31
cjwatsonthe intent is that the per-user default is suitable for basic patch contribution17:31
cjwatsonseb128: so I don't know what you did but you didn't merge - I think you rebased or something17:32
cjwatsonseb128: the commit hashes don't match17:33
seb128I did what Laney suggested :p17:33
seb128which is basically "clone master, pull my branch, rebase, and push"17:33
cjwatsonwell we can't detect rebases17:34
cjwatsonif you'd merged we'd have detected that17:34
seb128k17:34
seb128I need to learn git better17:34
seb128thanks ;-)17:34
cjwatsonif you're going to rebase, push the rebase to your branch first17:34
* seb128 closes that one manually17:34
cjwatsoni.e. git push <whatever the name of the remote is> +debian17:35
cjwatson(since this is the debian branch)17:35
cjwatsonif you do that then LP has the information to know that the MP is actually merged17:35
seb128k17:36
dokodirecthex, what's the story with the arm64 support in mono?17:56
xnox_infinity: is lttng ust broken on arm64? it tries to use CLOCK_MONOTONIC which is not defined...18:03
xnox_https://launchpadlibrarian.net/229616606/buildlog_ubuntu-xenial-arm64.ubuntu-app-launch_0.5%2B15.10.20150817-0ubuntu2_BUILDING.txt.gz18:03
infinityxnox_: Certainly sounds broken to me.18:05
cjwatsonsomething needs to include the appropriate feature test macro in CPPFLAGS, I guess18:10
xnox_infinity: cjwatson: https://git.lttng.org/?p=lttng-ust.git;a=commitdiff;h=ca4525b556680256149ead3746b566103e043d8e;hp=f7b16408b00ecce757bdde940853a48534b25edd18:12
xnox_somebody things it's great everywhere.18:12
xnox_i think i'll revert this check and make it conditional on actually ahving said clock available....18:12
cjwatsonwhat18:12
cjwatsonno18:12
cjwatsonit just needs the right feature test macro18:12
xnox_hm?18:13
cjwatson-D_WHATEVER18:13
cjwatsonTBH, a quick workaround is probably to just have ubuntu-app-launch compile with -D_GNU_SOURCE18:13
xnox_oh18:15
cjwatsonor '#define _POSIX_C_SOURCE 199309L' (or newer)18:15
cjwatsonu-a-l defines _POSIX_C_SOURCE in a few places already18:15
cjwatsonso it may even be that's the correct fix - if you're using liburcu perhaps you should be defining FTMs declaring new enough standards18:15
infinityOh, quite.  But curious that the feature guards differ between arches...18:16
infinityPerhaps hysterical raisins on older arches where it was always wrong and they didn't want to break backward compat by making it right?18:17
dokodirecthex, looks like you reverted: https://github.com/directhex/mono-1/blob/master/mono/arch/arm64/arm64-codegen.h  pointing to an out-of-tree file. but where is this file supposed to live?18:19
infinityxnox: mono 4.2 fails on s390x as well (was fine on Debian), perhaps a -pie thing?18:19
=== sarnold is now known as sarnold_
directhexdoko: the arm64 port is xamarin proprietary code, so it lives in a secret vault for such things ¬_¬19:21
dokoargh ...19:21
directhexdoko: no i'm not happy about that state of affairs, i try to moan about it every now & again19:21
directhexinfinity, xnox for s390x, talk to neale ferguson, neale@sinenomine.net, for mono s390x issues19:37
infinitydirecthex: I'm guessing the issue isn't s390x, but rather that we build with -pie by default on (currently) only s390x.19:37
infinitydirecthex: Hence why it's happy in Debian but not Ubuntu.19:37
infinitydirecthex: But just a guess right now, haven't experimented.19:38
rharpercyphermox: did you have any plans to do a merge of tgt for xenial  (1.057 -> 1.0.61 from debian unstable?)20:08
cyphermoxrharper: it's on the list but not high on it. if you want to do the merge, feel free (and I'm happy to review and sponsor)20:08
rharpercyphermox: thanks;  I've got a bug related to tgt under containers that I'm fixing, and noticed the delta;  I'll work a merge and apply a fix to the updated version as well20:09
cyphermoxfor now I'm focusing on things that are either a) haven't been merged in > 365 days or b) blocking a)20:09
cyphermoxrharper: cool20:09
rharpersure; just checking to avoid any duplicate work, sounds like we have a plan20:10
cyphermoxalright :)20:10
* mterry hugs pitti21:19
mterrypitti, gsl got promoted!  ;)21:19
rharpercyphermox: at your leisure, https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/152498221:36
ubottuLaunchpad bug 1524982 in tgt (Ubuntu) "Please merge tgt 1.0.61-1 (main) from Debian unstable (main)" [Wishlist,Confirmed]21:36
cyphermoxrharper: ok, reviewing now21:49
Unit193LocutusOfBorg1: Sorry, haven't had time to really test vbox's vboxweb, but it looks like it's still missing something to pull the username from.21:53
smoserinfinity, https://bugs.launchpad.net/curtin/+bug/152495422:04
ubottuLaunchpad bug 1524954 in curtin "Curtin error when deploying a maas/juju environment" [Undecided,New]22:04
smoseri believe what that is is that grub2-signed needs moving to -updates as grub2 made it through22:05
smoserdannf, maybe you can push on that ?22:05
dannfslangasek: ^22:07
slangasekdannf, smoser: whoops.  sorting22:09
slangaseksorry :/22:10
Unit193slangasek: Hi.  Did you get a chance to review merge proposals?22:10
cyphermoxrharper: sponsored22:12
slangasekUnit193: I have not, sorry; it's in my queue to look at still22:13
Unit193slangasek: There's a couple things that'll need to be updated, but that's broken since we last fixed it.  We've not fixed it due to it likely just getting broken again before approved.  We'll fix that when the time comes though.22:14
rharpercyphermox: \o/22:18
rharperawesome22:18
Unit193sarnold: Welcome back!22:22
sarnoldthanks Unit193 :)22:22
=== salem_ is now known as _salem
xnoxcjwatson, infinity: re-prior conversation http://paste.ubuntu.com/13909472/23:31
xnoxLaney, ^23:32

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