[00:49] <kees> anyone working on the nvidia regression?
[00:49] <kees> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639663
[00:49] <kees> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639215
[00:50] <kees> :(
[00:53] <rbasak> mdeslaur, tseliot (not here?): ^
[06:37] <cpaelzer> good morning
[07:33] <ANTI_psychiatry> Psychiatry         i __ s :     F__R__A__U__D       F__R__A__U__D      F__R__A__U__D                      !!!!!!!!!!!!!!!!!!           PLS,visit: antipsychiatry.org
[07:36] <cpaelzer> pitti: hi, the gnutls28 fix is blocked on some dep8 regressions on libaws and network-manager
[07:37] <cpaelzer> pitti: it doesn't appear really to be related to me - is that a "known to happen, just buzz on retest" or what would you think?
[08:01] <pitti> Good morning
[08:02] <pitti> cpaelzer: libaws is part of the "gnat broke recently", we can just ignore that; and NM is flaky indeed; I'll have a look
[08:03] <cpaelzer> pitti: ok, thanks
[12:07] <mdeslaur> kees: nothing much we can do, nvidia hasn't published a fixed driver yet
[12:07] <mdeslaur> kees: binary blob ftw
[15:00] <rbasak> !dmb-ping
[15:10] <hron84> Hi! I trying to re-create a binary deb package without source (i have no access to the source package, this is a legacy, discontinued software) with fixed dependencies for Ubuntu Yakkety. However, I faced with error when trying to run dpkg-buildpackage against these configs: https://gist.github.com/hron84/dc1e009852e23e3357527ceefefa77cb the error is "binary build with no binary artifacts found; cannot distribute". What do I miss from my configs?
[15:11] <hron84> (cross-posted from #ubuntu and #ubuntu-app-devel)
[15:14] <lamont> recently, zesty seems to have decided that I don't need about 3 inches of my second display's width.
[15:14] <lamont> not even sure which package to file that bug against
[16:16] <mterry> @pilot in
[16:20] <vimpulse> lamont:  If this were Debian, you might be able to file it against "unknown" or maybe "general".  In Ubuntu, I'm not sure if you have any such option.
[16:20] <vimpulse> lamont:  So -- ask us which package to file it against!
[16:38] <LocutusOfBorg> rbasak, sorry, when does the addition to the team happens?
[16:56] <nacc> mdeslaur: it seems like there might have been an upgrade-regression with mysql-5.5 in trusty (LP: #1637280)
[17:05] <mdeslaur> nacc: that's weird. any idea why the postinst isn't being run?
[17:06] <nacc> mdeslaur: not yet, that might be something good to test in a container/VM and try to run the postinst manually to see if it does work (then it's a matter of debugging why it didn't get invoked)
[17:06] <nacc> mdeslaur: do you mind putting that in the bug?
[17:06] <mdeslaur> nacc: I did run upgrade tests and it worked
[17:08] <nacc> mdeslaur: ack
[17:19] <nacc> rbasak: full bind9 import with patches-applied and unapplied in the history: https://git.launchpad.net/~nacc/ubuntu/+source/bind9
[17:20] <nacc> rbasak: is LP: #1637703 one of the known classes of upgrade bugs?
[17:27] <powersj> nacc: that user also filed LP: #1637701 which I just looked at
[17:33] <rbasak> nacc: neat, thanks.
[17:33] <rbasak> nacc: maybe add the filename to the subject if "No DEP3 Subject or Description header found"? Sometimes if there's nothing else the filename is still informative.
[17:34] <rbasak> nacc: I'm starting to suspect a new bug affecting release upgrades from 14.04 to 16.04 causing that error (7703).
[17:35] <rbasak> I had reproduction steps until diglett broke (I still have them but haven't retried yet).
[17:49] <nacc> rbasak: the filename for a patch is alwasy present
[17:49] <nacc> rbasak: Gbp-Pq: ...
[17:49] <rbasak> nacc: I mean right there in the summary.
[17:49] <nacc> rbasak: oh but you want it in the commit message summary, ok
[17:49] <rbasak> nacc: right. See https://git.launchpad.net/~nacc/ubuntu/+source/bind9/log/?h=applied/ubuntu/zesty-proposed for example
[17:50] <rbasak> Perhaps even put just the filename, and "No DEP3 Subject or Description header found" only in the body?
[17:50] <rbasak> Then the summary will be bad, and the body will explain why. But that is more useful than no summary at all.
[17:50] <nacc> rbasak: so reverse the order? Gbp-Pq: as the summary ?
[17:50] <nacc> rbasak: or on ly in the case of no header found?
[17:50] <rbasak> You might still need Gbp-Pq: in the body for consistency with gbp and automation.
[17:51] <rbasak> So...if no dep3, then filename (only) in subject, both "No DEP3 Subject or Description header found" and Gbp-Pq: ... in body.
[17:51] <nacc> rbasak: ack
[17:56] <rbasak> philroche, Odd_Bloke: FYI, gce-compute-image-packages added to the ubuntu-cloud packageset for yakkety and zesty.
[18:04] <philroche> rbasak: Thank you
[18:18] <LocutusOfBorg> nacc, php-imagick merge to probably fix testsuite? (imagemagick)
[18:19]  * LocutusOfBorg leaves
[18:24] <nacc> lutostag: will look at it, yep
[18:28] <nacc> rbasak: would it make sense for mysql-server to detect 'thread_concurrency=...' like it does for key_buffer and myisam-recover? (LP: #1638521)
[18:37] <rbasak> nacc: yes. Please dupe to bug 1612517.
[18:42] <nacc> rbasak: thanks!
[18:43] <nacc> barry: is there a sensible way forward for LP: #1638583? I know little about mailman, just trying to understand the bug
[18:46] <nacc> powersj: would it make sense for the triage list to not list bugs where Ubuntu Server is already subscribed and the bug is >= triaged?
[18:47] <barry> nacc: it's a tricky one because of some choices the debian maintainers have made.  basically, the packaging refuses to upgrade if there are "qfiles" laying around.  these files are the on-disk representation of the messages and their states between processing queues.  a running mailman system will almost always have these files laying around so it effectively means mailman can't be upgraded without sysadmin intervention.  i think it's
[18:47] <barry> an overabundance of caution because lots of sites install from source where that isn't a restriction, and we try very hard not to break the qfile pickle format (i can't remember the last time we even changed it)
[18:48] <barry> nacc: tbh, i would file a bug with debian and not worry about that for unattended upgrades, but still allow it for manual upgrades, if that's possible.
[18:48] <rbasak> nacc: in that circumstance, it may still be a user volunteering a patch, in which case we might want to pay more attention.
[18:48] <barry> but i'm not the debian maintainer of the package ;)
[18:49] <nacc> rbasak: yes, that's true -- i think we could split it into two lists, though
[18:49] <nacc> rbasak: purely updates, versus those that need to be triaged properly
[18:50] <rbasak> nacc: what would be the benefit of doing that?
[18:50] <nacc> rbasak: i'm only noticing that right now, particularly when i get behind, as i always do, the list is full of bugs that i don't need ot triage
[18:51] <nacc> rbasak: it was purely a question, feel free to disregard
[18:54] <nacc> rbasak: is LP: #1642275 familar to you?
[18:57] <rbasak> 2016-11-16T13:45:43.192868Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
[18:57] <rbasak> nacc: no, not seen that before.
[18:59] <nacc> rbasak: i've seen that particular issue in a few bugs so far (the unable to lock in the logs)
[20:28] <robert_ancell> slangasek, did you upload snapd into Debian? Would you be able to sponsor snapd-glib there too?
[20:53] <slangasek> robert_ancell: I could do a sponsorship, for sure; what's the long-term plan for who will maintain this in Debian?  would you be the maintainer (are you a DM)?  have you talked to zyga about it?
[20:54] <robert_ancell> slangasek, jbicha wanted it there. I'm not a DM and don't plan to be one. Haven't talked to zyga.
[20:54] <slangasek> robert_ancell: does jbicha want to maintain it? :-)
[20:54] <robert_ancell> slangasek, mostly wanted to check who would be best to do the sponsorship
[20:54] <robert_ancell> I'm hoping :)
[20:55] <slangasek> I could help out with sponsorship, but it's best if there's a path for someone closer to the action to get direct upload rights on it in Debian (DM)
[20:56] <robert_ancell> slangasek, thanks. Will ask jbicha then
[21:55] <mterry> @pilot out
[22:48] <tsimonq2> mterry: Hello, ping. :)