=== tumbleweed_ is now known as tumbleweed
=== stokachu_ is now known as stokachu
=== andyrock_ is now known as andyrock
=== lag_ is now known as lag
[01:05] <Unit193> Something odd with the builders now?  I wouldn't expect https://launchpad.net/~xubuntu-dev/+archive/ubuntu/staging/+build/14510915 to fail, and if it were to fail I'd expect a log. (This is a retry.)
[01:05] <Unit193> https://buildd.debian.org/status/package.php?p=xfce4-timer-plugin&suite=unstable
[01:15] <flamendless> where is jml here?
[01:52] <sarnold> Unit193: maybe give it another repoke
[01:56] <nacc> smoser: ok, np
[01:58] <Unit193> sarnold: Alrighty-o.
[02:03] <Unit193> sarnold: That seems to have worked, though generally not in favor of 'retry until it works', that seems to have done it. :P
[02:04] <sarnold> Unit193: great ;) the *timing* of the "retry" wasn't exactly random, but I wasn't confident of the end result :)
[02:13] <Unit193> sarnold: So you're saying...The timing on the timer seemed on time for another issue?
[02:13]  * Unit193 ducks.
[02:13]  * sarnold swings and misses
[02:51] <wgrant> Unit193: LP builds should be happy now, just had a bit of fun with one of our core routers.
[03:10] <Unit193> wgrant: Ouch.  And indeed, thanks!
[05:16] <alkisg> Hi, I'm trying 18.04 on a raspberry pi 2, and the 4.13 linux-raspi2 kernel doesn't boot, while 4.15 from proposed boots fine. Is it stuck in proposed? LP: #1757165
[05:16] <ubottu> Launchpad bug 1757165 in Kernel SRU Workflow "linux-raspi2: 4.15.0-1005.6 -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/1757165
[06:32] <alkisg> Also, NetworkManager doesn't manage the devices by default, because `/etc/netplan/01-network-manager-all.yaml` doesn't exist. Shouldn't that be shipped as a conffile instead of created by ubiquity or whatever? Or at least netplan should default to that if nm is installed...
[08:18] <xnox> alai, maybe try #netplan? i think netplan is innert by default, which is the right thing for it to do.
[10:04] <enyc> Hrrm,  OpenSSL  have put out key security-update in 1.1.0h ...   Is it worthwhile sync'ing bionic openssl to 1.1.0h-2 from debian very soon,  or  only treat as 'security fix' later ???
[11:43] <jdstrand> sarnold: if you give me a list, I can do the packaging for the apparmor bug and do the Breaks as infinity suggests
[16:01] <pjotr> Hello, I know you guys are extremely busy right now, but is there any chance that this GDebi bug will be fixed in time for Bionic:
[16:01] <pjotr> https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238
[16:01] <ubottu> Launchpad bug 1756238 in gdebi (Ubuntu) "gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags" [Critical,Confirmed]
[16:31] <jbicha> pjotr: maybe the fix for LP: #1719746 is incomplete. I don't use gdebi though.
[16:31] <ubottu> Launchpad bug 1719746 in gdebi (Ubuntu Artful) "gdebi 0.9.5.7+nmu1ubuntu3 broke being able to open .debs on default Ubuntu desktop" [High,Triaged] https://launchpad.net/bugs/1719746
[16:31] <jbicha> I see that Ubuntu MATE includes gdebi by default so maybe ask them to look into the gdebi issues
[16:36] <pjotr> jbicha: thanks for the tip, I'll try to contact them
[21:40] <rlink> ratliff:  Tested the xmltooling packages from security-proposed.  Looks good.
[21:41] <rlink> LP: #1752306
[21:41] <ubottu> Launchpad bug 1752306 in xmltooling (Ubuntu Xenial) "Security bug in XMLTooling-C before 1.6.4 [CVE-2018-0489]" [Undecided,In progress] https://launchpad.net/bugs/1752306