=== Foxtrot is now known as foxtrot
[02:21] <smoser> nacc, hey.
[02:21] <smoser> usd import -v --directory=isc-dhcp --lp-user=smoser --lp-owner=usd-import-team isc-dhcp
[02:21] <smoser> KeyError: "Cannot describe - No tags can describe '02c1acc925e9b52df3cdb807c525d56464102d26'."
[02:23] <smoser> never mind. seems better now (after a git pull)
[02:23] <smoser> well, now i get
[02:23] <smoser>  NameError: name 'remote_namespace' is not defined
[02:35] <smoser> nacc, i pushed fix
=== JanC is now known as Guest78373
=== JanC_ is now known as JanC
=== salem_ is now known as _salem
[06:15] <pitti> Good morning
[06:40] <cpaelzer_> good morning
=== cpaelzer_ is now known as cpaelzer
[06:40] <cpaelzer> hi pitti, thanks for pushing gnutls through
[06:41] <pitti> cpaelzer: no worries
[07:54] <cpaelzer> tjaalton: hi, since you have the required "powers" and were related to bug 1640805 in the past, could you take a look at reviewing and uploading the fix I attached?
[07:54] <ubottu> bug 1640805 in sssd (Ubuntu) "SSSD authentication fails after upgrade to 1.11.8-0ubuntu0.2" [High,Fix released] https://launchpad.net/bugs/1640805
[07:54] <cpaelzer> That is the Trusty SRU portion of it which needs a sponsor
[08:01] <tjaalton> cpaelzer: yep, uploaded
[08:01] <cpaelzer> thank you tjaalton
[08:01] <tjaalton> and committed to git
[08:01] <cpaelzer> tjaalton: sorry I didn't check on the VCS - thank you
[08:01] <tjaalton> no worries, easy to apply the debdiff
[08:02] <cpaelzer> tjaalton: would that have been a LP git or is the Ubuntu branch on alioth
[08:02]  * cpaelzer is looking up the pkg
[08:02] <tjaalton> on alioth
[08:02] <cpaelzer> ah ok
[08:02] <tjaalton> i'm not sure how to best integrate with lp
[09:03] <mwhudson> pitti: hello
[09:06] <pitti> hey mwhudson, how are you?
[09:07] <mwhudson> pitti: fine, wondering about autopkgtests again
[09:07] <mwhudson> pitti: is the process by which the tests to run for a given upload to -proposed documented somewhere?
[09:08] <pitti> mwhudson: the top-level page is https://wiki.ubuntu.com/ProposedMigration; it links to various details
[09:08] <mwhudson> pitti: in particular, does a depends on $foo in $bar's debian/tests/control mean that an upload of $foo will run $bar's tests?
[09:08] <pitti> mwhudson: yes, britney has done reverse test dependency triggering for a few months now
[09:09] <mwhudson> pitti: great, thanks
[09:09] <mwhudson> pitti: the wiki is slightly out of date then i think :-)
[09:09] <smb> good to know :)
[09:09] <pitti> we hadn't had that for many years, but it led to hard-to-diagnose regressiosn
[09:10] <pitti> mwhudson: I don't think "out of date", but I'm happy to clarify "reverse dependencies" to ".. binary and test .."
[09:10] <mwhudson> pitti: ok, i have the edit page open anyway :)
[09:11] <mwhudson> https://wiki.ubuntu.com/ProposedMigration?action=diff&rev2=25&rev1=24
[09:11] <mwhudson> pitti: anyway, thanks
[09:11] <pitti> thanks
=== _salem is now known as salem_
=== hikiko is now known as hikiko|ln
[12:09] <tinoco> cpaelzer: https://bugs.launchpad.net/qemu/+bug/1626972
[12:09] <ubottu> Launchpad bug 1626972 in qemu (Ubuntu Zesty) "QEMU memfd_create fallback mechanism change for security drivers" [Undecided,In progress]
[12:09] <tinoco> is done for you. waiting on sponsors now
[12:10] <tinoco> ill continue working with vhost log upstream in parallel
[12:10] <tinoco> cpaelzer: btw, are u a sponsor by any chance ;) if you are, feel free to test/upload it :o)
[12:13] <cpaelzer> tinoco: hi
[12:13] <tinoco> cpaelzer: o/
[12:14] <cpaelzer> tinoco: I just uploaded a minor fix to zesty which means one more debdiff for you - but not more I hope
[12:14] <tinoco> cpaelzer: i didn't do zesty
[12:14] <tinoco> since it was behind xenial
[12:14] <cpaelzer> behind yakkety I know
[12:14] <tinoco> oops, yakkety
[12:15] <cpaelzer> but I did the upload while you were writing this :-)
[12:15] <cpaelzer> just replied to you via mail as well
[12:15] <tinoco> cpaelzer: ok, let em check then. i can provide the debdiff, no problem
[12:17] <cpaelzer> tinoco: ok, I will throw all these at a ppa of mine and run some more tests against it
[12:17] <cpaelzer> tinoco: opening a query to discuss what you already tested ...
[12:17] <tinoco> cpaelzer: awesome!
=== hikiko|ln is now known as hikiko
[13:37] <doko> is anybody able to start quassel-client on a Unity desktop? the UI doesn't come up. on all of xenial, y and z. happened with a recent update ...
=== Son_Goku is now known as Conan_Kudo
=== Conan_Kudo is now known as Son_Goku
[14:43] <doko> python-vmware-nsxlib/amd64 unsatisfiable Depends: python-netaddr (>= 0.17.3)
[14:43] <doko> python3-vmware-nsxlib/amd64 unsatisfiable Depends: python-netaddr (>= 0.17.3)
[14:43] <doko> zul: ^^^
[14:43] <zul> doko: cool thanks ill have a look today
[16:31] <nacc> smoser: thanks, i was just about to fix the same way, thanks!
[16:31] <nacc> smoser: sorry for the breakage
[16:34] <nacc> rbasak: i think i found another attribute case, if a .gitattributes has specific files listed with eol, then '* -text' doesn't help :/
[16:42] <slangasek> infinity: stgraber: kees: mdeslaur: TB meeting in 18minutes
[16:43] <mdeslaur> ack
[16:59] <slangasek> rbasak: oh, you can't assign bugs to us?  well that's not good
[16:59] <slangasek> rbasak: on Gunnar's bug I ran the commands you requested, but that doesn't put any packages in that packageset; is that part something the DMB can take care of or should I do that too?
[17:18] <nacc> smoser: just pushed a small fix for gbp import-orig, fyi
[17:18] <nacc> smoser: to use the new tag namespace correctly on import
[17:48] <hjd> How can transition status be unknown? (http://people.canonical.com/~ubuntu-archive/transitions/html/html/glew.html)
[17:49] <hjd> Also, if I'm reading http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt correctly, the on-going glew transition is why for instance https://launchpad.net/ubuntu/+source/widelands hasn't migrated to zesty-release, right?
[17:49] <Laney> hjd: Affected but neither good nor bad
[18:01] <rbasak> slangasek: assign bugs> yeah, that was surprising to me. I guess I need to be a member of the community team or something.
[18:01] <rbasak> slangasek: yes, I can take care of populating the packageset. Thanks!
[18:01] <Laney> rbasak: FYI edit-acl has a 'copy' action
[18:02] <Laney> Which creates and copies the packages
[18:02] <Laney> Might want to advise the TB to use that next time
[18:02] <rbasak> Oh, neat. Thanks!
[18:08] <rbasak> "<slangasek> I suggested using the bug tracker"
[18:08] <rbasak> slangasek: I don't see an email. Did I miss a note somewhere?
[18:10] <rbasak> slangasek: also I'd be quite happy if the process was manual - I file a bug *and* send to the ML. As long as I can forget once fired :-)
=== JanC_ is now known as JanC
[18:27] <nacc> smoser: fyi, another fix pushed!
[18:32] <slangasek> rbasak: I did cc: you on my email reply
[18:52] <nacc> smoser: what would be the ideal way (given our usd.run) to invoke `git tag -a` for creating an annotated tag (using the git-tag spawned editor)?
[18:54] <nacc> smoser: nm, i think i figured it out
[18:56] <smoser>  run.run(['git', 'tag', '--annotate', 'foo'], stdin=None, stdout=None, stderr=None)
[18:56] <smoser> nacc, i think that works
[18:56] <nacc> smoser: well, then how would you get input to the tag command? it'll just sit forever, afaict
[18:56] <nacc> smoser: i think run() doesn't actually work without a string as an argument if shell=True
[18:57] <nacc> smoser: it ends up calling 'sh -c git tag -a upload/1%9.10.3.dfsg.P4-10.1ubuntu2 HEAD'
[18:57] <nacc> smoser: note the missing "" around the command
[18:58] <nacc> smoser: if i put "" around that command (e.g., sh -c "git tag -a upload/1%9.10.3.dfsg.P4-10.1ubuntu2 HEAD"), it runs from the shell; without it, git just spits out its usage
[18:58] <smoser> hm. it worked forme
[18:58] <smoser> in ipython
[18:58] <smoser> it brought up an editor
[18:58] <nacc> smoser: strange, i'll keep testing then, might be something elese
[18:59] <smoser> nacc, i just tagged the usd repository with 'foo', by doing:
[18:59] <smoser> python3 -c 'from usd import run; run.run(["git", "tag", "--annotate", "foo"], stdin=None, stdout=None, stderr=None)'
[19:01] <nacc> smoser: oh! i see what i'm doing wrong
[19:01] <nacc> smoser: thanks!
[19:04] <smoser> and, fwiw, both:
[19:04] <smoser>  python3 -c 'from usd import run; run.run(["ls"], stdin=None, stdout=None, stderr=None, shell=True)'
[19:04] <smoser> and
[19:04] <smoser>  python3 -c 'from usd import run; run.run("ls", stdin=None, stdout=None, stderr=None, shell=True)'
[19:04] <smoser> work for me
[19:04] <nacc> smoser: yeah, my problem was not passing all of the None arguments
[19:04] <nacc> smoser: thanks for the pointers!
[20:14] <jgrimm> smoser, stgraber, slangasek: any idea why '::1' line in /etc/hosts differs between cloud-images and ISO d-i installed?   the latter, includes 'localhost', the former does not.
[20:15] <stgraber> not sure. it does make sense having localhost listed for ::1 though, otherwise "ping6 -n localhost" wouldn't work
[20:16] <smoser> jgrimm, i suspect that the process that writes that file is older than writing ipv6 localhost
[20:16] <jgrimm> stgraber, indeed
[20:17] <jgrimm> smoser, agreed.. though my desktop is missing it too
[20:17] <slangasek> my desktop is not missing it fwiw
[20:18] <jgrimm> slangasek, interesting
[20:18] <slangasek> but my desktop was installed with d-i, not ubiquity, because lvm+crypt
[20:18] <jgrimm> ah
[20:18] <slangasek> I'm trying to remember if this was a bug we fixed in ubiquity
[20:18] <jgrimm> mine was ubiquity installed, circa wily
[20:18] <jgrimm> slangasek, ryan found an old one claiming it was fixed
[20:19] <slangasek> so, I think the right answer is to include localhost for the ipv6 address, and we should fix the cloud image build scripts to match d-i here
[20:19] <jgrimm> slangasek, cool. that's was my gut feel, except to wonder if someone intentionally backed it out at some point??
[20:19] <slangasek> jgrimm: checking the current /var/lib/dpkg/info/netbase.postinst, which should be considered authoritative, we are including localhost for ::1.
[20:19] <smoser> well, if that were the case then hopefully said process has version control on its /etc/hosts writing.
[20:20] <smoser> slangasek, is it 'localhost' ?
[20:20] <slangasek> things that deviate from that probably do so out of ignorance rather than by design
[20:20] <smoser> i have ip6-localhost and ip6-loopback
[20:20] <slangasek> smoser: in /var/lib/dpkg/info/netbase.postinst?
[20:20] <smoser> no, in /etc/hsots
[20:21] <smoser> yeah, i have no 'localhost' entry for ::1
[20:21] <jgrimm> smoser, then presumably you were a cloud-image, or ubiquity installation
[20:22] <smoser> ubiquity, yeah.
[20:23] <smoser> i didnt realize we were speciically speaking of 'localhost'
[20:23] <jgrimm> no worries
[20:24] <jgrimm> slangasek, given responses i'll just open bugs against the offenders
[20:25] <slangasek> jgrimm: I suspect livecd-rootfs for both
[20:26] <jgrimm> slangasek, cool. thanks
[20:41] <jgrimm> 1644009
[20:41] <jgrimm> bug 1644009
[20:41] <ubottu> bug 1644009 in livecd-rootfs (Ubuntu) "/etc/hosts ::1 line should additionally include 'localhost'" [Undecided,New] https://launchpad.net/bugs/1644009
[21:00] <nacc> rbasak: jgrimm: well, in pleasant news, even with all the changes to the importer, continuing the php-imagick import to re-merge worked and the rebase went through straightforwardly. In that particular case, we may be able to drop parts of the delta (testing those cases now), but it's nice to see.
[21:00] <jgrimm> nacc, nice!
[21:01] <jgrimm> nacc, did you see my poke about usd merge error I was getting this morning?
=== salem_ is now known as _salem
[21:44] <nacc> jgrimm: no, sorry!
[21:44] <nacc> jgrimm: too many overnight pings, i expect
[21:45] <jgrimm> :)
[21:45] <nacc> jgrimm: can you resend?
[21:46] <jgrimm> ack
[21:46] <jgrimm> nacc: pretty simple, i was just trying to do a usd merge, with a fresh usd, and fresh clone
[21:47] <jgrimm> nacc, ERROR:Failed to create local branch (debian/sid). Does it already exist (pass -f)?
[21:47] <nacc> jgrimm: ok, i just pushed those fixes before lunch
[21:47] <jgrimm> nacc, ok i'll retry, thanks
[21:47] <nacc> jgrimm: can you try it again and let me know, and if it stilld oesn't work, send me the src pkg name and i'll reproduce
[21:49] <jgrimm> nacc, different behavior at least.  fyi, i did a fresh clone again too
[21:49] <jgrimm> nacc, ERROR:tag is not a defined object in this git repository.
[21:49] <jgrimm> nacc, the package is at
[21:50] <nacc> jgrimm: ah, sorry, i just changed behavior! :)
[21:50] <nacc> jgrimm: just run `usd merge ubuntu/devel`
[21:50] <jgrimm> nacc, ah... :)
[21:50] <nacc> jgrimm: the subcommands were unnecessary -- in the general case you'll do both back to back
[21:50] <nacc> jgrimm: that succeeded for me locally
[21:51] <nacc> let me update the wiki too
[21:51] <jgrimm> nacc, thanks sir
[21:52] <jgrimm> nacc, indeed verified that works
[21:52] <nacc> jgrimm: note that if you are doing a re-merge
[21:52] <nacc> jgrimm: meaning there is an upload tag earlier
[21:52] <jgrimm> its not a remerge
[21:52] <nacc> jgrimm: then you might want `usd merge --tag-only`, and then actually do a git-rebase
[21:52] <nacc> jgrimm: ok
[21:53] <jgrimm> good to know tho!
[21:54] <nacc> jgrimm: presuming no new delta added, that is; (meaning your last upload/ tag matches ubuntu/devel)
[21:55] <nacc> jgrimm: i'll try and document these cases on the wiki
[21:56] <jgrimm> nacc, sounds good!  fyi <cmd> -h output on wiki page are stale too
[21:56] <nacc> jgrimm: yep, i was trying to stabilize the tooling and then c&p again
[21:56] <jgrimm> thanks sir
[21:56] <nacc> jgrimm: will update by EOD
[22:16] <nacc> mdeslaur: i think your imagemagick upload clobbered the fixes that were in 8:6.8.9.9-7ubuntu4 (and thus it regresses php-imagick)
[22:17] <nacc> mdeslaur: this is because (and i'm pretty sure i reported this to the debian maintainer who ignored it), the debian backports of certain upstream fixes are wrong/incomplete
[22:17] <rbasak> slangasek: that's odd. I think I'm missing it. Did you Cc the list too? https://lists.ubuntu.com/archives/technical-board/2016-November/thread.html doesn't have it either.
[22:18] <rbasak> jgrimm, nacc: that's odd. "ERROR:Failed to create local branch (debian/sid)" was what I complained about the other day too, but it since worked for me since before today.
[22:19] <nacc> rbasak: it was the importer -> lpusip change
[22:19] <LStranger> could anyone tell me why openbox-3.6.1-3 is still in proposed? gilir put it there a month ago and it's still there.
[22:19] <rbasak> Ah
[22:19] <nacc> rbasak: it should work now on a fresh clone and merge
[22:19] <rbasak> OK, thanks.
[22:19] <nacc> LStranger: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#openbox
[22:19] <nacc> LStranger: it regressed plasma-framework's autopkgtests
[22:20] <LStranger> nacc: ah, I see, thank you very much
[22:20] <LStranger> probably I should poke debian maintainer to add the dependency in debian too
[22:21] <LStranger> or may be just open a RC bug instead :D
[22:23] <LStranger> if I get it right, the openbox-kde session would not work in current state unless kde session is installed
[22:25] <tarpman> LStranger: are we looking at the same log? the failure linked there looks like bug 1590956 to me... doesn't look like openbox's fault
[22:25] <ubottu> bug 1590956 in plasma-framework (Ubuntu) "plasma-framework 5.22.0a-0ubuntu1 fails tests on s390x" [Undecided,Confirmed] https://launchpad.net/bugs/1590956
[22:25] <mdeslaur> nacc: hrm, I'll take a look tomorrow. Is there a bug for php-imagick being broken now?
[22:25] <mdeslaur> nacc: I have another imagemagick update coming out in a few days I believe, so I can fix it at the same time
[22:26] <slangasek> rbasak: oh wow, my local dns is broken and mail not going out, thanks for the prod :)
[22:29] <nacc> mdeslaur: i think what's missing is that the deb8u5 did refresh one bug and pick up the patch, but the original backport that was refresh is still wrong (see my messages in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811308)
[22:29] <ubottu> Debian bug 811308 in imagemagick "Multiple minor security issues" [Normal,Fixed]
[22:29] <nacc> mdeslaur: that has the three upstream backports that are missing, and cause php-imagick to fail
[22:29] <nacc> mdeslaur: well, imagemagick is stuck in proposed
[22:29] <nacc> mdeslaur: so no bug, but i can file one :)
[22:33] <LStranger> tarpman: well, I thought it was about missing dependency on plasma-workspace there, probably I'm wrong
[22:34] <nacc> mdeslaur: so the issue is ubuntu9's 0070-Fix-PixelColor-off-by-one-on-i386.patch and ubuntu10's are different. I'm guessing that is due to taking Debian's version
[22:34] <nacc> mdeslaur: but our version had add-on fixes, i apologize for my poor changelog not indicating that more clearly (i've since learned better!)
[22:35] <nacc> mdeslaur: would it be more productive to just merge imagemagick?
[22:42] <mdeslaur> nacc: I have to see if the cves are fixed in unstable, but sure we should be merging it
[22:42] <mdeslaur> nacc: sorry for overwriting your fix, I'll make sure to correct it in my next updates to the stable release
[22:43] <nacc> mdeslaur: sorry, just to make sure i'm not crossing wires -- i'm only seeing the failure to migrate in z-p
[22:44] <mdeslaur> oh! Does it just affect the autopkgtest?
[22:44] <nacc> mdeslaur: we'd be able to drop my backports, at least, if we merge, as they are fixes from upstream that were mis-cherry-picked back. I'm happy to take a look at the merge, if you want
[22:44] <nacc> mdeslaur: yeah, i think so -- i mean it's a functional bug in the package, that only php-imagick provokes :)
[22:44] <mdeslaur> nacc: sure, could you handle the merge?
[22:45] <mdeslaur> nacc: I can check tomorrow if all the cves are fixed in unstable
[22:46] <nacc> mdeslaur: yep, i'll add it to my list, most of the updates to the package were by me :)
[22:46] <mdeslaur> cool, thanks!
[22:47] <nacc> mdeslaur: thank you!
[22:47] <slangasek> pitti: so, systemd-resolved apparently stopped resolving ipv6 names for me, and I'm not sure how to debug
[22:48] <juliank> Hmm, should I pass -v1.2.15 when building apt 1.2.17 which replaces the 1.2.16 in the xenial-proposed unapproved queue (1.2.15 is the one in -updates), or does that not matter at all?
[22:49] <juliank> Currently it also has a weird test failure, not sure what's going on there...
[22:52] <LStranger> anyway, I've filed an RC bug against Openbox in Debian, should it help to get openbox from proposed into zesty?
[22:54] <LStranger> why I'm interested - my friends need #1336521 to be fixed in LTS releases.
[22:54] <Unit193> (Debian #845386)
[22:54] <ubottu> Debian bug 845386 in openbox-kde-session "openbox-kde-session package is unusable" [Grave,Open] http://bugs.debian.org/845386
[22:57] <LStranger> for myself I've created a patched package but I want others to have fix too. :)
[23:04] <LStranger> tarpman: so far, if that isn't openbox fault, what can be done to let openbox 3.6.1-3 enter zesty? this another bug will be fixed later then.
[23:04] <juliank> Hmm, the arm64 build failure for trusty bash holding back bug 1422795  is not a regression of that upload (the failing file was not changed at all) Should I still generate a  regression-proposed bug report for that?
[23:04] <ubottu> bug 1422795 in bash (Ubuntu Trusty) "bash crashes often if inputrc contains revert-all-at-newline" [High,Fix committed] https://launchpad.net/bugs/1422795
[23:05] <juliank> The fix is basically ready
[23:05] <tarpman> LStranger: you have to find someone who has the ability to bypass that autopkgtest regression... I don't know who that would be. someone here, I'm sure
[23:06] <juliank> Proposed bash fix: http://paste.ubuntu.com/23519397/
[23:06] <LStranger> well, I'm asking such someone then -- do it, please, bug 1336521 is pretty annoying for people
[23:06] <ubottu> bug 1336521 in pcmanfm (Ubuntu) "Application Startup Notify fully ignored" [Undecided,Confirmed] https://launchpad.net/bugs/1336521
[23:07] <Unit193> LStranger: They tend to want you to attach debdiffs, and sub sponsors.
[23:08] <LStranger> Unit193: the matter is in migration Debian updated package into Ubuntu
[23:10] <juliank> Hmm, it's even stranger.
[23:11] <juliank> The same line causing the error on arm64 in trusty is present in zesty as well, but it works there.
[23:11] <LStranger> Unit193: the difference in 3.6.1-1ubuntu2 was kde-workspace was replaced with plasma-desktop, which is also wrong but in 3.6.1-3 that kde-workspace-bin dependency is removed so no difference except missing dependency, which I filed as a grave bug so it will be fixed soon
[23:12] <juliank> doko: You might want to look into bug 1644048 - there's a printf(ngettext(...)) line in bash's builtins/help.def that causes a FTBFS on arm64 in trusty, but not on other architectures, and not in newer releases.
[23:12] <ubottu> bug 1644048 in bash (Ubuntu Trusty) "4.3-7ubuntu1.6 FTBFS on arm64" [Undecided,New] https://launchpad.net/bugs/1644048
[23:12] <LStranger> so far it fits into zesty so I hope someone would push a button here
[23:14] <LStranger> well, time to sleep for me :)