[08:49] <danboid> Is Ubuntu Server 20.04 going to support installing to ZFS RAID-Z2?
[09:02] <doko> https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191220-focal-focal.html
[09:03] <doko> ginggs, tumbleweed: some more unexpected py2-removals
[09:42] <cjwatson> brlin: glibc's libraries specifically support being executed for various reasons - you can execute that particular one and get things like feature information
[09:43] <brlin> cjwatson: Thanks for the info.
[10:29] <cpaelzer> jamespage: hiho, about openvsiwtch I wanted to ask how we should order uploads
[10:29] <cpaelzer> as we discussed in december DPDK 19.11 needs OVS 2.13
[10:29] <jamespage> cpaelzer: morning
[10:30] <cpaelzer> and happy new year!
[10:30] <cpaelzer> you said you'd be ok to carve a 2.13 from git into focal
[10:30] <cpaelzer> which would allow me to get DPDK 19.11 in as-is
[10:30] <cpaelzer> and we can later on move to 2.13 final once available
[10:30] <cpaelzer> I was now wondering how we'd want to order things
[10:30] <cpaelzer> should I get DPDK 19.11 into focal-proposed first
[10:31] <jamespage> cpaelzer: right I remember
[10:31] <jamespage> I can work on that today/this week
[10:31] <cpaelzer> or would you prefer trying to build the new OVS against the former 18.11 first
[10:31] <jamespage> let me generate a new snapshot
[10:32] <cpaelzer> ok, thanks for looking into it jamespage
[10:32] <cpaelzer> once from your testing you know if you prefer OVS or DPDK to hit focal-proposed first let me know
[10:32] <jamespage> I suspect I'll have to deal with the OVN/OVS splitout at the same time
[10:33] <cpaelzer> ok, so you'll need some more time than "update & upload" with it anyway
[10:33] <cpaelzer> jamespage: I'll leave it with you then and you let me know when you want the new DODK synced then ok?
[10:33] <jamespage> yep fine with me
[10:33] <cpaelzer> rather DPDK
[10:33] <cpaelzer> great thank you jamespage
[11:05] <jamespage> cpaelzer: might need the DPDK upload first - can you drop a 19.11 release into https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3694/+packages for me?
[11:05] <cpaelzer> yes jamespage
[11:05] <jamespage> ta
[11:11] <cpaelzer> jamespage: uploaded - last build was ~3 weeks ago, lets see if it still works fine
[11:14] <jamespage> cpaelzer: needs a new dep - libbpf-dev
[11:14] <cpaelzer> oh yeah the kernel team still didn't get that one resolved
[11:14] <cpaelzer> :-/
[11:14] <cpaelzer> easily done ...
[11:15] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836708 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826410 if you are interested
[11:20] <ginggs> i just uploaded https://launchpad.net/ubuntu/+source/file/1:5.37-6ubuntu1 to prevent autosync of 1:5.38-2
[11:20] <ginggs> see debian bug #948269
[11:25] <cpaelzer> jamespage: new version uploaded
[11:25] <jamespage> ta
[11:25] <cpaelzer> jamespage: IIRC there was something else that we needed to disable but I fail to remember which exactly
[11:25] <cpaelzer> but if it FTBFS again it should be another easy one
[11:26]  * cpaelzer checks his stale branches to remember
[11:32] <cpaelzer> jamespage: it failed again sorry, I'm rather sure to have something working shortly ...
[11:37] <cpaelzer> the one now is more interesting, reported around texlive-latex-extra but not showing up in a sbuild focal-proposed build of today
[11:38] <Laney> ginggs: nice one
[11:38] <Laney> fun place for a bug
[11:43] <jamespage> fnordahl: hey - did you pickup any information at OVN/OVS con about alignment of versioning between OVS and OVN
[11:43] <jamespage> the OVN build requires a build OVS source tree to compile/test
[11:44] <jamespage> and I'm just considering the best way todo that
[11:44] <jamespage> thinking about and openvswitch-src:all package that provides the OVS source code in distro, that the OVN build can use to build itself
[11:44] <jamespage> but I don't understand the versioning just yet
[12:40] <fnordahl> jamespage: they are planning on a year+month release naming for OVN with a three month release cadence, the first probably being 20.03.  There was also talk about supporting building OVN against multiple versions of OVS and making it pussible to build against a -dev type package instead of a whole source tree.
[12:42] <fnordahl> jamespage: I'll try to get a pulse on how it's progressing
[14:20] <danboid> Hi didrocks! Does the 20.04 installer have any more ZFS options yet eg RAID Z2?
[14:21] <didrocks> danboid: hey! No, it has a slightly different partitionning scheme, but nothing like this nor planned to. We will work more on the automated snapshots, rollbacks side of thing for this cycle + command line options
[14:22] <danboid> didrocks, So are you saying that 20.04 (server) will still only support using one whole disk for ZFS installs?
[14:23] <didrocks> danboid: I don't think the server will have the ZFS option yet, we only added it as experimental on the ubiquity (desktop) installer for now
[14:24] <danboid> Oh that's a shame. I was expecting ZFS support in Ubuntu server 20.04
[14:24] <didrocks> post-install, people can add mirrors (manually) for now though, I think RAID Z2 is the same but haven't tried
[14:24] <didrocks> better to have thing strongly tested before pushing experimental things that are not tested. And this is even more true for a LTS
[14:26] <danboid> Sounds like proxmox ve gets another year or two ruling the Linux ZFS roost then
[14:27] <cpaelzer> coreycb: I saw you update 1770295 have you seen reproduce this issue?
[14:28] <coreycb> cpaelzer: no, I haven't. I was mainly just keeping the cloud archive triage in line with the ubuntu triage.
[14:29] <cpaelzer> ok, I ahve asked if "openstack people have seen or reproduced that" on the bug in comment #5
[14:30] <cpaelzer> coreycb: if you have the minute to do so even a "no we haven't" documented on the bug would be useful
[14:30] <cpaelzer> as it would confirm my "this is odd, prio low" triage
[14:32] <ahasenack> roaksoax: hi, good morning/afternoon. Just saw this commit to debian's bind9 package fly past: https://salsa.debian.org/dns-team/bind9/commit/e6e079c0fa9689aff6eb373ddd997adf3e22e849
[14:32] <ahasenack> they removed the apport hook which has you as the author, because it's gpl
[14:33] <ahasenack> roaksoax: I'm wondering how it could be relicensed. If it was writte while you were working for canonical, then we could change the copyright I think, but if it was done on your spare time, then it's different
[14:34] <cpaelzer> rafaeldtinoco: if you give the ipxe change a review and if possible a test and chime in on the debian MR that would be great
[14:34] <rafaeldtinoco> ok
[14:34] <cpaelzer> I wanted to take the change (if it was proven to be ok) for us on this cycles merge if debian hasn't done so in time
[14:35] <cpaelzer> so whatever the outcome is updating both MRs is probably a good thing (jsut copy and paste will do)
[14:35] <rafaeldtinoco> makes sense
[14:35] <rafaeldtinoco> ok
[14:35] <rafaeldtinoco> tks
[14:35] <cpaelzer> your ping on the debain MR might revive that
[14:35] <cpaelzer> and the one on our side helps me to trust the change on the qemu merge
[14:35] <cpaelzer> on that topci, I know that the maintainer hasn't seen my Mrs so I'll ping him
[14:49] <ahasenack> cpaelzer: hm, I think the python transition might have bitten me just now
[14:49] <ahasenack> haproxy won't build anymore
[14:50] <ahasenack> sbuild-build-depends-haproxy-dummy : Depends: python but it is not going to be installed
[14:50] <ahasenack>                                       Depends: python-mako but it is not going to be installed
[14:54] <ahasenack> yeah, "python" is uninstallable
[15:10] <cpaelzer> ahasenack: yes doko sent a mail a few hours ago
[15:11] <doko> s/python/python2/g
[15:14] <cpaelzer> jamespage: I forgot to ping you - you have dpdk - 19.11-2~ubuntu1~ppa3 in your PPA
[15:15] <doko> ahasenack: please fix, or I'll look at that specific one as a priority
[15:15] <cpaelzer> it was blocked by the python2->3 transition and for now I worked around that by disabling docs as that was the only tihng it was needed for
[15:16] <cpaelzer> doko: while being at the topic, let me ask for a python2/3 best practise
[15:16] <cpaelzer> doko: texlive-latex-extra has a Dependency line containing this "python, python3"
[15:16] <cpaelzer> which makes it fail to install
[15:16] <cpaelzer> => https://paste.ubuntu.com/p/mynQxT2Hh2/
[15:17] <doko> the debian maintainer said that it's not completely ported, so that should be python2, python3 instead
[15:17] <cpaelzer> yeah I have read https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938656
[15:17] <cpaelzer> doko: so "python2, python3" is what you'd expect to be in this Dependency line then?
[15:17] <doko> yes
[15:18] <cpaelzer> thank you
[15:18] <doko> and make sure that you have the python2 shebangs as well
[15:19] <cpaelzer> not sure I'll do a change, but I'll take a look and ping the bug for sure to keep it alive
[15:19] <cpaelzer> chances are the shebang changes would have to be an all the reverse-deps of texlive-extra
[15:21] <jamespage> cpaelzer: ta
[15:21] <jamespage> just working on some OVN bits in the OVS package for the split out
[15:44] <cpaelzer> rafaeldtinoco: 1809682 1733889 came up on triage as "not touched for 180 days"
[15:44] <cpaelzer> rafaeldtinoco: are those two ok with you or do we need to do anything from a team perspective?
[15:56] <rafaeldtinoco> cpaelzer: checking
[15:59] <rafaeldtinoco> cpaelzer: they're part of the cleanup phase after merges are finished. I got them.. hopefully I can start cleaning up and documenting this week, after all HA merges are finished (at least this 1st phase)
[16:22] <roaksoax> ahasenack: howdy! I have no claim over the license, feel free to relicensed if needed
[16:26] <ahasenack> roaksoax: can I email you at that address in the header? Is that still you?
[16:28] <roaksoax> ahasenack: that should still be me indeed
[16:34] <doko> juliank: any idea why that fails now? https://launchpadlibrarian.net/459395331/buildlog_ubuntu-focal-s390x.protobuf_3.6.1.3-2ubuntu2_BUILDING.txt.gz
[16:35] <juliank> heh, what's protobuf doing with apt-file?
[16:35] <juliank> doko: oh, that's ruby gem2deb
[16:36] <doko> cpaelzer: texlive-extra uploaded
[16:37] <juliank> I'm not sure what's going on but this seems like a bug in gem2deb or dh_ruby<
[16:47] <roaksoax> 3xit
[18:11] <deadrom> hi. where is the place for hwe bugs?
[18:22] <ahasenack> deadrom: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+filebug I believe
[18:22] <ahasenack> deadrom: or do you mean "hardware" bugs?
[18:22] <ahasenack> the link I pasted is for bugs against the hwe (hardware enablement) kernel
[18:22] <deadrom> HardWare Enablement
[18:22] <deadrom> why couldn't I get there myself? I went in circles in Launchpad
[18:23] <deadrom> told all sorts of how to report a bug, but never actually how
[18:57] <gQuigs> deadrom: usually recommended to use apport to file a bug,  apport (generally) will be able to get it to the right package given what you have installed
[22:18] <doko> coreycb: please could you have a look at networkx/python-networkx? currently creates a lot of componet mismatches, and you're the last uploader, sorry ;p
[22:42] <coreycb> doko: sure I'll take a look
[23:14] <rafajafar> heyyy is there a problem is 18.04.3-74 because I just updated and now my computer freezes. If I go to 18.04.3-72 everything works again.