[06:02] <lordievader> Good morning
[07:25] <cpaelzer> good morning lordievader
=== mIk3_09 is now known as mIk3_08
[08:54] <cpaelzer> rafaeldtinoco: FYI I started to prep https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1840745 for AMD as discussed
[08:54] <ubottu> Launchpad bug 1840745 in qemu (Ubuntu Bionic) "backport extended amd spectre mitigations" [Medium,Triaged]
[08:54] <cpaelzer> but before I'd want to complete https://bugs.launchpad.net/ubuntu/eoan/+source/libvirt/+bug/1828495 in eoan to then do the SRUs of bother together
[08:54] <ubottu> Launchpad bug 1828495 in linux (Ubuntu Eoan) "[KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM." [Wishlist,In progress]
[08:54] <cpaelzer> due to that I started on the latter and you will see some requests to test and reivew later on
[10:50] <rafaeldtinoco> cpaelzer: perfect!
[10:50] <rafaeldtinoco> good morning o/
[11:28] <cpaelzer> rafaeldtinoco: hi
[11:28] <rafaeldtinoco> cpaelzer: o/
[11:35]  * rafaeldtinoco found a gcc9 issue in Eoan compiling clickhouse #)
[13:32] <ahasenack> I can't find python-httptools in eoan: https://launchpad.net/ubuntu/+source/python-httptools
[13:32] <ahasenack> I even have eoan-proposed enabled, and for all pockets (main, restricted, universe, multiverse)
[13:32] <ahasenack> but apt won't see it
[13:33] <ahasenack> oh
[13:33] <ahasenack> python3
=== cpaelzer__ is now known as cpaelzer
[14:51] <Odd_Bloke> rharper: https://code.launchpad.net/~daniel-thewatkins/simplestreams/+git/simplestreams/+merge/371523 <-- do you have upload rights for simplestreams?
[14:51] <rharper> Odd_Bloke: I do not
[14:54] <Odd_Bloke> Hmm, OK.
[14:54] <Odd_Bloke> powersj: Could we find someone to sponsor me for ^^?
[14:56] <Odd_Bloke> powersj: (We should probably also spend a bit of time properly dropping the Python 2 packages; I removed one which lintian reported as empty, but not the others.)
[15:08] <lordcirth> Ubuntu 16.04, I have an interface ens2f0, ens2f0.248 vlan interface attached to it, and a br248 attached to that. The bridge has "post-up ip route add 192.168.248.0/22 via 192.168.248.1 dev br248". This command isn't getting run on boot anymore (it worked before?) and the logs say "RNETLINK: Invalid argument"
[15:08] <lordcirth> Previously that error has occurred when I try to add a route whose 'via' isn't reachable. But I don't see how that can happen here, given that the br248 config has a static IP
[15:10] <sdeziel> lordcirth: does it work if you run the command manually?
[15:11] <lordcirth> sdeziel, yes, that's the weird part. It has to be some kind of race on boot
[15:11] <lordcirth> How can a post-up be running before the rest of the interface gets configured/
[15:15] <powersj> Odd_Bloke, rcj might be good to look at that once you fix ci
[15:27] <Odd_Bloke> powersj: I don't _think_ we need CI passing on the packaging branches, because we push instead of autolanding.
[15:29] <Odd_Bloke> rcj: Please to be looking. :)
[15:33] <rcj> Odd_Bloke: Looking now
[15:34] <Odd_Bloke> Thanks!
[15:39] <Odd_Bloke> rcj: We don't normally use the autolander for packaging MPs (it's normally review and then push by the submitter).  Let's see what happens!
[15:42] <rcj> Odd_Bloke: You can push, I've reviewed the MP.
[16:06] <Odd_Bloke> powersj: rcj doesn't have upload rights either.
[16:06] <powersj> Odd_Bloke, ok we can ask someone on the team
[16:08] <powersj> ahasenack, rbasak could one of you look to sponsor an upload of simplestreams for Odd_Bloke
[16:53] <rbasak> Odd_Bloke: I'm expecting to see commit ba75825b as an ancestor of ubuntu/devel, but it doesn't seem to be?
[16:54] <rbasak> I think you're meant to have merged master in to ubuntu/devel and then updated debian/changelog and tagged it
[16:59] <rbasak> I can still sponsor though
[16:59] <rbasak> Doesn't look like the commit graph will make a difference to the tooling.
[17:00] <rbasak> Odd_Bloke: tools/make-tarball works for me, or is there a different generated equivalent tarball you'd like me to use?
[17:07] <ahasenack> kanashiro: hi, did you see the bug mail from your openldap sru?
[17:33] <kanashiro> ahasenack, yes, should I do something regarding that?
[17:34] <ahasenack> kanashiro: this is now the verification step, where ideally the person who reported the bug would follow the [test] instructions and confirm that the package in -proposed fixes the bug
[17:34] <ahasenack> kanashiro: this not always happens, or takes too long
[17:34] <ahasenack> kanashiro: so what I do generally is give it a day or two, and if no-one performs the verification steps, I do it myself
[17:36] <kanashiro> ahasenack, ok, I'll keep an eye on the bug then, and if no one test it I will in a couple of days
=== Luke_ is now known as Guest93934
=== Guest93934 is now known as Luke
[18:05] <Odd_Bloke> rbasak: Ugh, the autolander squashes.
[18:06] <Odd_Bloke> rcj: This is why we shouldn't use the autolander! :p
[18:06] <Odd_Bloke> rbasak: I'll have to force-push up a fix.
[18:08] <Odd_Bloke> rbasak: Done; good catch!  tools/make-tarball is what I would use (albeit indirectly via https://github.com/CanonicalLtd/uss-tableflip/blob/master/scripts/build-package).
[19:01] <rbasak> Odd_Bloke: OK, so I'll upload an orig tarball I'll make myself?
[19:02] <Odd_Bloke> rbasak: Yep, if that's OK?
[19:02] <rbasak> Sure
[19:03] <rbasak> Uploaded
[19:16] <Odd_Bloke> Thanks!
[21:36] <lopta> Is there a simple way to list the dependencies of a package?
[21:38] <lopta> I'm standing up what might turn out to be my first production Ubuntu server.
[21:40] <lopta> Well this installer looks pretty friendly.
[21:44] <rbasak> A package that's installed? "dpkg -s package"
[21:44] <rbasak> A package in apt that you haven't yet installed: "apt-cache show package"
[21:44] <rbasak> And look for the Depends line
[21:51] <lopta> Thanks
[21:52] <lopta> Well, I went for it and installed Ubuntu Server and mono-complete.
[21:52] <lopta> ...sadly the version of mono is too old for the application.
[21:54] <lopta> I wonder whether a newer version of Ubuntu Server might open up a newer version of Mono
[21:54] <Odd_Bloke> lopta: What version of Ubuntu did you install?
[21:54] <lopta> 18.04, I think
[21:55] <lopta> uname -a doesn't tell me but I can look up the name of the .iso
[21:55] <lopta> 18.04.3
[21:55] <Odd_Bloke> lopta: `lsb_release -a` would also do it.
[21:55] <lopta> Thanks
[21:55] <lopta> Well, I'll try again tomorrow.
[21:56] <Odd_Bloke> lopta: So it looks like disco (19.04) has 5.18.0.240, but be aware that disco is only supported for 9 months from its release.
[21:56] <Odd_Bloke> So you'd need to be prepared to upgrade in the near future, to continue being security supported.
[21:56]  * lopta nods
[21:57] <lopta> I imagine I'll be long-gone by that point but I'd love to deploy this with Ubuntu if possible.
[21:57] <lopta> Oh weird, I get a 404
[21:58] <lopta> Ah, second time's the charm.
[22:00]  * lopta wipes the vm and starts from scratch
[22:00] <lopta> Thanks for your help!
[23:10] <teward> ... well i'm an idiot >.<  I have an LXD server running off an isc-dhcp-server that is in the same container subnet.  And it had the wrong gateway in the DHCP records and had an IP conflict so internet traffic was asploding to the Internet.
[23:10] <teward> ... I feel stupid >.>