=== juliank_ is now known as juliank
cpaelzergood morning05:32
sarnoldpitti: 1587727 (man that was quick :)06:02
pittisarnold: yep, known already :)06:52
pittisarnold: I clearly don't visit the right web sites :) (I get a crash with www.facebook.com which I never use, for example)06:52
sarnoldpitti: aha, good :) I thought you mentioned getting errors for it, wanted to make sure06:52
sarnoldpitti: hehehehehe06:53
pittiGood morning06:53
sarnoldgood morning ;)06:53
apwpitti, i am not mad in thinking that we (at least) tried to make python3 the one and only python for xenial and up?07:47
pittiapw: correct, we've been trying for a loong time07:47
pittiapw: I think we actually succeeded on the server image? (at least for some time, maybe it came back)07:47
pittiah no, python2.7 is still on http://releases.ubuntu.com/xenial/ubuntu-16.04-server-amd64.list07:48
apwpitti, but it would be a reasonable statement that it would be wrong introducing new python2 dependancies, that they should be python307:48
apwpitti, for xenial/yakkety07:48
pittievery such case throws us back07:49
sarnolddid desktop make it?07:49
sarnoldI thought something did :)07:49
apwyeah i did too :)07:49
pittiI think we managed to get rid of it on the cloud images07:49
pittino py2.7 there07:50
pittidesktop still has it07:50
sarnoldI thught cloud-init was still python 2.. http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/bin/cloud-init uses #!/usr/bin/python   anway...07:51
apwpitti, on systemd ... who supplied the resolvconf integration service ?07:59
pittiapw: for networkd you mean? that was me08:00
pittiand yes, it's horrible08:00
apwpitti, yeah for networkd ... ok i think it may be flawed08:00
apwit seems (and i may be doing it wrong) if i tell networkd about a DNS server which is specific to a domain08:01
apwwe shove that domain into /etc/resolv.conf and that then feeds back into resolved which sees /etc/resolv.conf updated08:01
apwso it becomes a (indeed the) primary DNS08:01
pittiapw: indeed, good point; so we need to look at whether the entry has Domains= as well, I figure, and then not supply it?08:02
pittiapw: networkd already sends its DNS info to resolved anyway08:03
pittiapw: this was mostly a shim for people using networkd without resolved08:03
apwpitti, it is utterly unclear how that file is to be interpreted (other than telling you it should not :)08:07
apwpitti, cirtainly it _is_ reporting in there that there is DNS but there is ROUTE_DOMAINS= in there as well, but i don't have enough configuration via networkd to know what it would look like if my primary DNS was configured in here08:09
apwpitti, do you know how to do that so perhaps i can at least fake it08:09
pittiapw: hang on, I'm trying in a VM (not using networkd on my desktop, or anywhere permanent)08:09
apwpitti, oh you meany, making me use it :-p08:10
pittiwhen did I? :-)08:10
apwwhen you uploaded it to yakkety :)08:10
apwwell the resolved bits anyhow08:11
apwas resolved gets half its config from networkd because thats not a layering violation08:11
* pitti doesn't understand these three comments, sorry08:12
pittiapw: so for a global DNS server, you just get DNS= and OPER_STATE=, no other fields08:13
apwi am trying to configure resolved which we switched to using, to do that i _have_ to configure networkd because that part of resolved configuration is stored only in files networkd also reads08:13
apwpitti, and if you have both ?08:13
pittiapw: so I think we must make /lib/systemd/system/systemd-networkd-resolvconf-update.service ignore files which have ROUTE_DOMAINS08:13
pittias these just can't be handled via glibc08:13
pitti/etc/resolv.conf simply lacks syntax for this08:13
apwthat seems appropriate to me08:14
pittiapw: do you want to file a bug about it to track it, or want me to?08:24
pitti(we might eventually need to port this fix to xenial, if anyone decides to start using networkd there)08:25
sarnoldpitti: btw what are we going to do with the KillUserProcesses thing? it apparently didn't go over well on fedora when upstream flipped it..08:25
pittisarnold: it's reverted in 230-2, which is sitting in y-proposed08:26
pittithis first attempt clearly didn't go well08:26
sarnoldpitti: woot :) thanks08:26
pittinow we're getting flak from the other side for disabling it again :)08:26
pittisarnold: but I think this needs to be re-thought08:26
pittisarnold: one recent proposal that I've seen is to use SIGHUP instead of SIGKILL08:26
sarnoldit's a nice feature to have available but to turn on by default seems a pretty drastic change08:26
pittiwhich DTRT with tmux and screen (they stay running), but should still clean up gnome leftovers08:27
sarnoldthat's way more unixy :)08:27
sarnoldnohup exists for applications that just inherit, applications which care can handle it ..08:28
apwpitti, i'll file a bug now and have a look08:30
cpaelzerpitti : is there a ppa for autopkgtest to get adt-buildvm-ubuntu-cloud for yakkety images working on a Xenial system?08:38
pitticpaelzer: not a PPA, but it's in xenial-backports (and trusty-backports too)08:38
pitticpaelzer: but it's still not working very well, I filed bug 1587188 yesterday08:39
ubottubug 1587188 in cloud-init (Ubuntu) "[yakkety regression] does not grow partition any more" [Undecided,New] https://launchpad.net/bugs/158718808:39
pittii. e. the generated images have a horribly small root partition, so only small tests actually work08:39
cpaelzerpitti: ah, your update is so recent I just don't have it got yet via backports - thanks for making me aware of the follow on issue08:39
pittinot entirely sure if that's actually in cloud-init, or a regression in how we build the cloud images themeselves, though08:40
pitticpaelzer: oh, wait, which fix do you mean?08:40
pitticpaelzer: oh, the renamed images, I see08:40
cpaelzerpitti: I was looking for the one with the name change loosing -disk108:40
pittithat fix is in 3.20.708:41
cpaelzeryeah that is why I started looking for a ppa, but backports is fine08:41
pitticpaelzer: I'm going to upload 3.20.8 to sid now, and as soon as this autosyncs, I'll backport it to t and x08:41
pitti3.20.7 just landed in testing08:41
apwpitti, bug #158776208:41
ubottubug 1587762 in systemd (Ubuntu) "systemd-networkd-resolvconf-update.service incorrectly published domain limited DNS servers to /etc/resolv.conf" [Undecided,New] https://launchpad.net/bugs/158776208:41
pitticpaelzer: in the meantime, just locally apply http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/commit/?id=6676ed6ea08:42
pitticpaelzer: and the next time you'll get a package upgrade that will include the fix08:42
cpaelzerpitti: I almost edited that lone myself before starting to think you likely fixed that already08:42
cpaelzerpitti: thanks, I'll give the cloudinit bug at least a few minutes - maybe I can find something there for us08:43
cpaelzerthe probably easiest way to get fixes early until released is pull-lp/debian-source and then run with full path like /tmp/autopkgtest-3.20.7/tools/adt-buildvm-ubuntu-cloud08:45
cpaelzersomewhat nicer than to patch the real system :-)08:45
pitticpaelzer: just run it out of git :)08:46
pitticpaelzer: that's what I do in production08:46
cpaelzer+1 evil overlord points for pitti for "run it out of git in production"08:47
pittiwell, if I do a fix I don't want to wait a day before I can roll it out, people need it NOW :)08:47
pittiand while autopkgtest's tests are annoying (they take ~ 30 mins), they are also rather effective at guarding against regressions08:48
pittiand even then, git reset --hard HEAD^, and life goes on08:49
apwpitti, cna i use awk in this context, rather than sed?08:52
pittiapw: sure, as long as it gets along with mawk08:52
pittiapw: btw, it might be easier to actually not run this horrible thing at all if resolved is being used08:53
pittiapw: this is a shim for using networkd without resolved, but with resolvconf and software that uses /etc/resolv.conf directly08:53
pittiit's not needed for anything else08:53
apwyeah that makes sense, is there an easy way to tell that ?08:54
mwhudsoni'm trying to use sbuild to build an i386 package on my laptop and it's complaining about08:54
mwhudson sbuild-build-depends-core-dummy:amd64 : Depends: crossbuild-essential-amd64:i386 but it is not installable08:54
apwmwhudson, are you building that in a amd64 chroot or something ?08:55
mwhudsoni'm confused, i don't think i need or what any cross building nonsense here08:55
pittiapw: first iteration is to add "ConditionPathExists=!/run/systemd/resolve" to /lib/systemd/system/systemd-networkd-resolvconf-update.path08:55
mwhudsonapw: i made it with mk-sbuild --arch i386 yakkety so i hope now08:55
mwhudsonand $ schroot -c yakkety-i386 --directory / -- uname -m08:56
apwyep that looks believeable08:58
mwhudsonah passing --build i386 --host i386 is happier08:58
mwhudsonor indeed --arch i38608:59
apwpitti, so without the other fix or with that together09:00
apwpitti, as i am assuming that will fix my issues completely09:00
mwhudsondoes anyone happen to know the incantation to get the filet to make --extra-repository-key=file.asc work for a ppa?09:01
mwhudsoni'm sure i can figure it out but...09:01
pittiapw: right, if you don't run this unit at all, it'll fix things for you09:02
pittiapw: I'm just not sure whether we can get away with this09:02
apwpitti, well i have done the other bit too, i'll add a diff to the bug09:04
apwpitti, then we can think about the test09:04
pittiapw: cheers09:04
pittiapw: I'll write that (before applying the patch)09:05
pittiapw: still battling with armhf lost autopkgtests and infra, getting to this later09:05
apwpitti, no rush at all09:08
apwpitti, and this way i can hand apply the fix and see if it works in practice09:08
mwhudsonhm apparently that option just doesn't work?09:09
mwhudsonor doesn't do what i think09:12
mwhudsonhacked around, anyway09:12
juliankpitti: bug 1569099 got a verification-needed, but that does not make much sense, it's a duplicate of bug 1560797 which is already closed in xenial with the same commit.09:13
ubottubug 1560797 in apt (Ubuntu Wily) "duplicate for #1569099 apt does not configure Pre-Depends: before depending package" [High,Fix released] https://launchpad.net/bugs/156079709:13
ubottubug 1560797 in apt (Ubuntu Wily) "apt does not configure Pre-Depends: before depending package" [High,Fix released] https://launchpad.net/bugs/156079709:13
apwpitti, ok patch attached and cowboy'd onto my machine ... seems to be working at least for now09:15
juliankAnyway, what is missing for the apt SRU to be moved to -release? From what I see in bug 1538438, that one should be fixed, but still verification-needed. And bug 1580952 has verification-needed, but no test case, as it's a new-micro-release-type-SRU09:16
ubottubug 1538438 in apt (Ubuntu) "apt-helper crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()" [High,Triaged] https://launchpad.net/bugs/153843809:16
ubottubug 1580952 in apt (Ubuntu Xenial) "[SRU] Update apt/xenial to 1.2.12" [Medium,Fix committed] https://launchpad.net/bugs/158095209:16
pittijuliank: for xenial you mean? nothing, but until yesterday it didn't age for 7 days yet; today it's fine09:17
juliankAh OK09:17
pittijuliank: sorry, that was for wily09:18
pittijuliank: which refers to bug 1575877 which is v-done and 7 days now09:18
ubottubug 1575877 in apt (Ubuntu Wily) "no_proxy ignored if https_proxy set" [Medium,Fix committed] https://launchpad.net/bugs/157587709:18
* pitti releases09:18
juliankYeah, xenial was uploaded 2016-05-1209:18
juliankso it's far beyond schedule09:18
pittijuliank: look at http://people.canonical.com/~ubuntu-archive/pending-sru.html09:19
pittijuliank: the dupe bug is striked through, so irrelevant; but the two other bugs weren't verified, and it's not fixed in yakkety09:19
juliankEww, and some autopkgtest regressions09:20
pittii. e. bug 1538438 (not fixed in y, not verified), and bug 1580952 (missing test case, not verified)09:20
ubottubug 1538438 in apt (Ubuntu) "apt-helper crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()" [High,Triaged] https://launchpad.net/bugs/153843809:20
ubottubug 1580952 in apt (Ubuntu Xenial) "[SRU] Update apt/xenial to 1.2.12" [Medium,Fix committed] https://launchpad.net/bugs/158095209:20
juliankpitti: Oops,  the first is fixed in yakkety09:21
juliank1.2.12 is the bugfix cherry-pick of 1.3~exp1 in yakkety09:22
juliankThe autopkgtests are strange, but unrelated it seems: sbuild fails with "E: Unable to find a source package for procenv" and apport with "https://launchpad.net/ubuntu/+archive/primary/+files/libacl1-dbgsym_2.2.52-3_i386.ddeb gnutls_handshake() failed: The TLS connection was non-properly terminated."09:23
rbasakpitti: I'm sure I've asked you this before, but I can't find a reference right now. systemd is hiding errors from postinst invoke-rc.d, and as a result it doesn't end up in bug reports. Can we amend apport to provide it in the general case?09:24
rbasakpitti: example: bug 158769509:24
ubottubug 1587695 in amavisd-new (Ubuntu) "package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1" [Undecided,Incomplete] https://launchpad.net/bugs/158769509:24
rbasakpitti: perhaps on invoke-rc.d failure, invoke-rc.d should automatically dump "systemctl status" to stderr?09:24
rbasakOr else, I'd like some other way for apport to pick it up.09:24
pittijuliank: right, the apport one is a glitch, I'll retry09:25
juliankpitti: Yes, and the sbuild one also happens in the most recent build with apt 1.2.10ubuntu109:26
pittijuliank: sbuild, this also apparently happesn with the xenial-release apt, as it also failed for the proposed dpkg: http://autopkgtest.ubuntu.com/packages/s/sbuild/xenial/amd64/09:26
pittiso something definitively broke this, but not the new apt09:26
juliankpitti: What to verify about bug 1580952? I don't think this makes a whole lot of sense there.09:28
ubottubug 1580952 in apt (Ubuntu Xenial) "[SRU] Update apt/xenial to 1.2.12" [Medium,Fix committed] https://launchpad.net/bugs/158095209:28
pittiI suggested "Please add an SRU test case which exercise the code paths that changed here."09:29
juliankIt's a "New upstream microrelease" with test cases in it.09:29
pittimaybe at least some small test plan with installing/upgrading various packages, downloading a source, etc.09:29
pittito make sure it'snot completely broken09:29
pittiright, that too09:29
juliankI mean, the autopkgtests check all those things in an automated integration test case fashion, and users apparently use it successfully (at least the one who checked that no_proxy worked correctly), so...09:32
pittijuliank: ok, agreed09:34
pittijuliank: I updated the two bugs09:37
* pitti releases09:37
pittijuliank: thanks for the updates09:37
juliankpitti: I already started queuing (currently 2) commits for 1.2.13! :) - should arrive in a few weeks. Especially fancy ones like "fail instead of segfault on unreadable config files" and the easy "Provide complete apt bash completion"09:39
juliankI'm trying to get more translations in as well, but the merge gets confusing (anyone knows a .po merge helper?)09:40
pittijuliank: msgmerge ?09:40
pittirbasak: hm, no amavis messages in https://launchpadlibrarian.net/262668434/JournalErrors.txt, so I'm not sure if that'd actually help09:41
juliankHmm, yeah, https://stackoverflow.com/questions/16214067/wheres-the-3-way-git-merge-driver-for-po-gettext-files says we can build a 3 way merge driver with that09:41
pittirbasak: might be that this is a forking service which only outputs to log files, not to stdout/err?09:41
pittirbasak: ah, wait, this only shows messags with priority >= warning, so maybe that's why09:42
pittirbasak: yeah, I guess we can amend the ubuntu hook for package failures to include the status09:42
pittiapw: nice fix! (I'd just do s/routable/route_domains/)09:43
rbasakpitti: thanks. I could see you were busy on something else so I filed bug 1587791 so as not to forget.09:43
ubottubug 1587791 in apport (Ubuntu) "apport hides systemd postinst service start failure error messages" [Undecided,New] https://launchpad.net/bugs/158779109:43
pittirbasak: yeah, sorry; still working on some test infra fallout09:44
rbasakpitti: np. I'd like to see this fixed (will save us bug triaging time) but it's hardly urgent.09:44
=== yuning_ is now known as yuning-afk
apwpitti, yeah makes more sense feel free to hack her up ;)09:47
pittitinoco, xnox: aupkg02 ( is down again; can you please prod it?10:24
tseliotpitti: aptdaemon can't be installed in yakkety, any ideas? https://launchpadlibrarian.net/262720256/buildlog_ubuntu-yakkety-amd64.ubuntu-drivers-common_1%3A0.4.19_BUILDING.txt.gz10:28
pittitseliot: because of http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#packagekit, the proposed version is incompatible10:29
pittisee bug 149629210:29
ubottubug 1496292 in packagekit (Ubuntu) "Needs to be ported to packagekit 1" [High,Confirmed] https://launchpad.net/bugs/149629210:29
tseliotpitti: ok, so it is a known issue. I need to backport some code from u-d-c to xenial (to give back about 1 second on boot), so I'll just ignore yakkety for now10:31
cpaelzerpitti: the resizing issue you reported is actually in cloud-utils, I created a MP for smoser to consider - details in the bug10:45
cpaelzerthat said back to what I actually wanted to do ... or lunch :-)10:46
pitticpaelzer: yay, you figured it out? thanks!10:47
caribououps, sorry11:26
cpaelzerpitti: just verified, 'til the fix hits the archive booting into the adt guest with your vm script and running "sudo resize2fs /dev/vda1" gets you images to work with for now11:30
pitticpaelzer: greaet11:32
=== hikiko is now known as hikiko|ln
=== hikiko|ln is now known as hikiko
=== hikiko is now known as hikiko|ln
=== hikiko|ln is now known as hikiko
=== seb128_ is now known as seb128
=== _salem is now known as salem_
cpaelzerpitti: I was happy too early about the yakkety adt now being fine a few hours before13:15
cpaelzerthe disk size is good now but something (tm) crashes it now13:15
cpaelzerdo you have any notes / best practise on debugging adt-run / adt-virt-qemu?13:15
cpaelzerwith all debug enabled I see it booting fine, but then kill the qemu by a sig 15 when executing "adt-virt-qemu: DBG: execute-timeout: /tmp/adt-virt-qemu.7vsnggp9/runcmd true"13:16
cpaelzerif it is a timeout it is rather fast - like 2 seconds :-)13:16
pitticpaelzer: should be 5 s13:20
pitticpaelzer: hm, and that's with the PYTHONHASHSEED=0 hack already?13:20
pittias this has this very symptom13:21
cpaelzerpitti: I'll build from git as you do and let you know if anything in there fixes my issue13:23
cpaelzerpitti: do I need to recreate the guest images to pick up the change?13:23
pitticpaelzer: shouldn't be necessary really13:30
cpaelzerpitti: yeah - out of git is good, thanks13:32
pitticpaelzer: which version do you have installed? 3.20.7?13:33
mitya57sil2100, hi, do you have any thoughts @ https://code.launchpad.net/~mitya57/appmenu-qt5/lp1574699/+merge/294381 ?13:33
pitticpaelzer: aside from the image rename I don't see a relevant change since 3.20.613:33
cpaelzerpitti: started with 3.20.4, then used 3.20.7 for the image create, but back to .4 for run13:34
cpaelzerpitti: now I just switched to git to stay ahead just as you do13:34
pitticpaelzer: .4 won't work, that doesn't have the PYTHONHASHSEED hack13:34
pitticpaelzer: you need >= .5 for running yakkety images13:34
pitticpaelzer: this hack applies to adt-run time, not to image creation time13:34
cpaelzerwhich is why the adt-run out of git now got it working13:35
pitti3.20.8 is uploaded to sid, but it'll take another half day or so to land in yakkety;  I'll backport it tomorrow13:35
pittiinfinity, sarnold: FYI, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#systemd is just landing13:36
pittiwith the unkill change13:36
tumbleweedcjwatson: I've hit something that feels very much like https://bugs.debian.org/708123 in an upgrade from 12.04 to 14.04 (and then we went to 16.04)14:00
ubottuDebian bug 708123 in grub-pc "[grub-pc] grub2 (2.00-14) fails to install on RAID arrays (rescue, boot is broken)" [Important,Open]14:00
tumbleweedI'll grab an image of it and muck around in qemu14:01
cjwatsoncyphermox: ^- can you deal with that?14:03
cyphermoxtumbleweed: filed a bug?14:05
tumbleweedI was wondering what you'd want to look at14:06
tumbleweedI'm going to start by trying to upgrade the metadata in a VM copy of it14:06
tumbleweedsymptoms are: rescue prompt shows no md devices, one has to boot it off a raid member14:11
tumbleweedand the raid modules all seem to be present14:11
tumbleweedalso, rescue mode seems racy :P14:40
ginggssil2100: hi, can you rebuild mtp for yakkety please? it still depends on boost from xenial15:38
sil2100ginggs: hey! Ok, no-change rebuild on its way15:41
ginggssil2100: thanks!15:42
sil2100ginggs: hm, strange that it deps on the old boost still, I did a no-change rebuild of it on the 20th of May already15:50
ginggssil2100: mtp (0.0.4+16.04.20160413-0ubuntu2) xenial; urgency=medium  <= distribution is xenial15:53
ginggsCopied from ubuntu xenial in Stable Phone Overlay PPA by Ubuntu Archive Auto-Sync <= this sounds weird to me15:54
sil2100ginggs: ah, right, my bad - I guess the rebuild didn't happen in the end16:01
sil2100Thanks :)16:02
pittihallyn: demoting cgmanager to universe for now, as per http://people.canonical.com/~ubuntu-archive/component-mismatches.txt16:35
pittihallyn: only the binary for now; we still have a few rdepends of the library in main, like upstart and ubuntu-core-libs16:36
pittihallyn: is cgmanager still actually a thing which we want to support, or is that being phased out in favor of lxcfs etc?16:36
mterry@pilot in16:41
=== udevbot changed the topic of #ubuntu-devel to: Xenial (16.04) Released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: mterry
flaiksis there a way to get kernel 4.6 running on 16.04 ? i need it for a required fix for my t460s16:42
ikoniaflaiks: we just discussed this16:42
mapreriwhat usually people do in ubuntu when a package ftbfs in one arch for reason nobody can't get? — are partial removals a thing?16:43
* mapreri is looking at cowdancer16:43
ikoniathats not what this channel is for,16:43
ikoniaflaiks: the support channel is #ubuntu16:43
jrwrenikonia: try #ubuntu-kernel you migth also ask if the patch that you see in 4.6 has been backported to the ubuntu 4.4 kernel16:46
ikoniajrwren: not for me, but thank you, it's not been backported for the record for flaiks16:46
dobeymapreri: i usually fix the problems, in my packages16:47
jrwrenikonia: sorry. I meant to direct taht to flaiks16:47
mapreridobey: "for reason nobody can't get" implies we 1/ can't figure out the problem 2/ can't reproduce it 3/ in debian just builds.16:47
mapreriwould be awesome if you can look at it and see if you can make it out! ♥16:48
ikoniajrwren: not a problem at all16:48
maprerinot having porterboxes available doesn't really help either (the actual maintainer tried in qemu but no luck)16:49
hallynpitti: phased out16:54
dobeymapreri: well i don't know enough about the code and its memory model, but it would appear that the memleak test is failing for some reason. i see in the shell script for that test a comment about LD_PRELOAD causing a memleak, so perhaps related?16:57
cjwatsonmapreri: Partial removals are certainly possible, though we prefer to avoid the cop-out option if at all possible :)16:57
cjwatsonmapreri: worth trying with -O216:58
cjwatsonmapreri: (the "obvious" difference between Debian and Ubuntu that's ppc64el-specific is that Ubuntu's toolchain defaults to -O3 on ppc64el)16:58
cjwatsonso DEB_MAINT_CFLAGS_STRIP := -O3 and DEB_MAINT_CFLAGS_APPEND := -O2 or equivalent16:59
mapreri(didn't know it)16:59
cjwatsonmapreri: you can try it in a PPA16:59
dobeyah yeah, that makes sense given that it's memory related17:00
maprerii wanted to try, before that, a no change rebuild in a ppa: https://launchpad.net/~mapreri/+archive/ubuntu/ppa/+build/9845065 — it bult..17:07
maprericould be related for it being virtualized?17:08
cjwatsonmapreri: virt/non-virt makes no difference for ppc64el17:08
cjwatsonso let's try just retrying that build17:08
cjwatsonof course it could be non-deterministic17:09
mapreri- failed17:10
maprericjwatson: any other suggestion? :)17:12
* mapreri would be very happy to have it building!17:12
maprerii have to go out for some hours now, but please do feel free to dump ideas (or even try out stuff!)17:15
cjwatsonmapreri: -O2 would definitely be my next suggestion17:19
cjwatsonalso diff build logs and see if that throws up anything (though I don't immediately spot anything very obvious)17:20
mterryseb128, so are we OK with switching packages to geoclue-2.0?  Did we ever find an actual solution for them?  (I see that empathy got switched to 2.0)17:29
seb128mterry, yeah, see the migration bug, seems like robert_ancell fixed our geoip server to talk the same api that google/mozilla use17:31
dobeymterry: is this where you end up having to write a backend for geoclue-2.0 that uses ubuntu-location-service?17:31
seb128which makes it compatible with geoclue217:31
seb128mterry, https://code.launchpad.net/~robert-ancell/canonical-is-puppet/geolocation-api/+merge/29607717:31
mterrycyphermox, in bug 1585863, $4 suggested modifying a network-manager patch of yours -- basically dropping your changes to src/supplicant-manager/nm-supplicant-interface.c -- can you comment there?  I was about to sponsor it, but wasn't sure I knew what the deal was there18:56
ubottubug 1585863 in OEM Priority Project xenial "WiFi malfunction after suspend & resume stress" [Critical,New] https://launchpad.net/bugs/158586318:56
mterry@pilot out19:11
=== udevbot changed the topic of #ubuntu-devel to: Xenial (16.04) Released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
brainwashis pkexec broken? pkexe whoami  gives me:19:45
brainwash polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie19:46
brainwashpkcheck --list-temp --> Error getting session: No session for pid <PID>19:50
maprericjwatson: is the version of sbuild used for the primary archive builds and for the ppa builds the same?  I see weird differences in the output like this (just curiosity):20:19
mapreri[-PWD=/«PKGBUILDDIR»-] {+PWD=/«BUILDDIR»/cowdancer-0.80+ppa0+}20:19
mapreri(this is the diff, for completeness: https://volatile.mapreri.org/2016-06-01/821944dc8105ba888c8857b2cacb7737/diff.html )20:19
mapreri(actually, is the full logs dwdiffed)20:20
cjwatsonmapreri: Yes, it's the same; congratulations, you've found an sbuild bug to do with + handling21:21
mapreriahahahah \o/21:21
maprericjwatson: bug in which it can't correctly compute PKGBUILDDIR and sed it over the build log?21:22
cjwatsonprobably needs to quote a regex harder21:23
pittihallyn: ok, thanks; I figure ubuntu-app-launch and ubuntu-core-libs will need some work then, but systemd-shim is gone already21:30
=== jgrimm is now known as jgrimm-afk
mwhudsondoes anyone have a script for doing a no-change rebuild of a package in a ppa?23:21
=== salem_ is now known as _salem

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