[01:38] <mwhudson> i presume it's more or less standard policy that tzdata changes end up getting SRUed?
[01:38] <Unit193> Pretty normal.
[10:38] <Laney> zul: Your neutron is still failing tests.
[13:32] <tsdgeos> was a pleasure working for Canonical! /me waves
[17:55] <bdmurray> barry: What did you say about the pyclean package install failure issue?
[17:56] <barry> bdmurray: it just looks like pyclean is being run by python3 which makes no sense given that py3clean should be run by python3
[17:57] <bdmurray> barry: so presumably a local configuration issue?
[17:58] <barry> bdmurray: my guess is that this is another case of someone pointing /usr/bin/python to /usr/bin/python3
[17:58] <barry> which no one should do
[18:00] <dobey> or if you're going to do it, you should at least remove all the python2 stuff, and pin those packages so they can't be installed again
[18:01] <bdmurray> barry: Maybe we should check for that in apport?
[18:02] <barry> bdmurray: that would actually be very helpful for debugging these cases because it seems like it might not be an uncommon thing for people to do, even though they have to manually toggle the symlink
[18:09] <bdmurray> barry: bug 1681528 if you are interested
[18:10] <barry> bdmurray: thanks
[20:30]  * xnox feels kind of bad for flying united
[20:30]  * xnox hopes the fares will go down even further
[20:30] <ogra_> wel, according to some news sites you might need to use ships to leave your country after brexit :)
[20:38] <jackpot51> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1681566
[20:38] <jackpot51> Updating from 16.10 to 17.04 is broken on NVIDIA systems
[20:39] <bdmurray> could you add your upgrade log files found in /var/log/dist-upgrade?
[20:39] <jackpot51> Will do
[20:42] <jackpot51> https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1681566/+attachment/4859865/+files/dist-upgrade.tar.gz
[20:52] <jackpot51> bdmurray: Maybe it should be moved to nvidia-graphics-drivers-375?
[20:54] <bdmurray> jackpot51: I found something else suspicious
[20:59] <jackpot51> bdmurray: What is it?
[21:02] <bdmurray> jackpot51: Do you know what the system76-driver-nvidia package does?
[21:02] <dmj_s76> Why yes!
[21:05] <dmj_s76> bdmurray: It just depends on nvidia-375 and ubuntu-driver-common.  It also installs some xorg quirks to handle a few specific gpu/display combinations.
[21:07] <bdmurray> So in apt-term.log we can see dkms building the driver for the 4.8 kernel - around line 4100
[21:07] <jackpot51> Right. It does not trigger for 4.10
[21:08] <jackpot51> On line 4928, it should have run
[21:09] <jackpot51> And 5256
[21:09] <bdmurray> 4928? Mine only goes to 10 er 4823
[21:10] <dmj_s76> Line 5450 shows it loading nvidia dkms modules for 4.8
[21:10] <jackpot51> Oh, sorry. There are \r's that are counted as newlines
[21:13] <dmj_s76> Line 5450 -> 4141
[21:14] <bdmurray> The suspicious thing I saw was in main.log re nvidiaUpdate() and "no old nvidia driver installed" but that probably isn't causing this
[21:18] <jackpot51> I wonder where that comes from
[21:19] <bdmurray> ubuntu-release-upgrader's DistUpgradeCache.py
[21:20] <bdmurray> It looks like its for transitioning from different driver version numbers, but I'm guessing a bit.
[21:21] <bdmurray> Regardless ubuntu-drivers-obsolete.pkgs seems a bit old to me
[21:26] <jackpot51> bdmurray: Any ideas on how to fix this?
[21:29] <bdmurray> jackpot51: Could you test w/o the system76 ppa?
[21:30] <jackpot51> Sure thing bdmurray
[21:32] <bdmurray> jackpot51: thanks!
[21:43] <Zta> I'm trying to build a package from some random app. I want to properly fill in the Depends: section of my DEBIAN/control file.  Is there a tool for this? I mean something that analyses (ldd) the binary and looks up the epoch version?
[21:43] <Zta> So that given a binary I get "Depends: liballegro4.4, libc6 (>= 2.14), libgcc1 (>= 1:3.0), libgif7 (>= 5.1), libjpeg8 (>= 8c)"
[21:46] <Zta> I've scripted it in bash for now, but it's not pretty
[21:55] <tarpman> Zta: sounds like you might be working one or two levels too low. the stuff that goes in the binary package (DEBIAN/ and such) is normally auto-generated by the dpkg-dev tools (dpkg-gencontrol and friends). the specific tool you're looking for is called dpkg-shlibdeps. at a higher level, most packages use debhelper to orchestrate the build. start here: https://www.debian.org/doc/manuals/maint-guide/
[21:56] <Zta> Thanks!
[21:57] <Zta> I'll look into this tomorrow.
[22:10] <cardboard64> my touchpad stops working after some time on 17.04
[22:11] <cardboard64> how can I troubleshoot that?