[16:45] <zx2c4> apw: oh cool "UBUNTU: Ubuntu-5.4-5.4.0-13.16"
[16:45] <zx2c4> it's been tagged
[16:45] <zx2c4> !!
[16:46] <apw> zx2c4, its on its way thorugh the sausage machine
[16:46] <zx2c4> is that what "cranking" is?
[16:46] <apw> just a colloquialism, as in 'turning the crank' over and over to make things happen
[16:46] <zx2c4> haha
[17:24] <sdhd-sascha> I already ask at netplan. I can't set link up on a bond device. The members of the bond are all in UP state. I can ping the local bond. What could be wrong ?
[17:31] <sdhd-sascha> Not sure, what happens. But know i got a link. What i have done:
[17:31] <sdhd-sascha> 1) add an ip addr on one bond member
[17:31] <sdhd-sascha> 2) ip link set up dev bond0
[17:31] <sdhd-sascha> 3) netplan apply
[17:31] <sdhd-sascha> Now it works?!
[17:31] <sdhd-sascha> Thank you 
[17:54] <zx2c4> apw: is there a .deb built somewhere of those modules?
[17:54] <apw> zx2c4, heh the sausage machine is not _that_ quick
[17:55] <zx2c4> oh... my
[17:55] <apw> zx2c4, and signing into the efi trusty thing takes time too
[17:55] <zx2c4> tag was 2 hours ago.... this cranking machine must be some insane aparatus
[17:55] <apw> zx2c4, the amd64 build is quick-ish, but there are other arches on there
[17:55] <zx2c4> does it require you keep pressing buttons or is it pretty automaed
[17:55] <zx2c4> automated
[17:56] <apw> zx2c4, its mostly automated as you would expect; but it is building on the launchpad builders so it has to wait for availablity etc
[17:56] <apw> zx2c4, and the arm arches take like 8 hours to build
[17:56] <zx2c4> oooo it's a launchpad procedure so of course it takes forever
[17:56] <zx2c4> holy cow
[17:57] <apw> zx2c4, it was only actually uploaded like 20m ago, so ... it'll be a bit
[17:57] <zx2c4> oh :D
[17:57] <apw>       NEW : wireguard
[17:57] <apw> s390x has finished and actually has built a new module ...
[17:58] <apw> so that is hopeful
[17:58] <zx2c4> haha cool what webpage is that
[17:58] <zx2c4> https://launchpad.net/ubuntu/+source/linux/+publishinghistory is empty
[17:59] <apw> yeah it gets built in a team ppa
[18:01] <apw> zx2c4, once all the arches are built it gets one last review then copied to -proposed to be signed; then it gets properly tested before release
[18:02] <apw> zx2c4, i expect i get to test wireguard :)
[18:05] <zx2c4> hehe
[18:06] <zx2c4> apw: http://demo.wireguard.com/ might be useful
[18:07] <zx2c4> curl https://git.zx2c4.com/wireguard-tools/plain/contrib/ncat-client-server/client.sh | sudo bash && ping 192.168.4.1
[18:07] <zx2c4> curl https://git.zx2c4.com/wireguard-tools/plain/contrib/ncat-client-server/client.sh | sudo bash && ping 192.168.4.1 && ip link del dev wg0
[18:08] <zx2c4> curl https://git.zx2c4.com/wireguard-tools/plain/contrib/ncat-client-server/client.sh | sudo bash && ping -c 4 192.168.4.1 && ip link del dev wg0
[18:08] <zx2c4> voila.
[18:08] <zx2c4> output looks like this: https://א.cc/ygmapdKc
[18:08] <apw> zx2c4: oh I use it in anger I will know if it works
[18:08] <zx2c4> haha
[20:54] <ricotz> sforshee, hi :), do you mind to retry they finished archs to reduce the automatic delay? https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/+packages?field.name_filter=&field.status_filter=published&field.series_filter=focal
[20:55] <ricotz> s/reduce/avoid
[20:57] <sforshee> ricotz: done
[20:57] <ricotz> sforshee, ty