[13:17] <yurtesen> good afternoon
[13:19] <yurtesen> utkarsh2102: still nothing... :( 
[13:50] <kanashiro> yurtesen, from the email thread I understood that ahasenack will be checking frr which is impacted by the same rsyslog issue and from that we might have a good solution for the others affected packages, including tomcat
[14:35] <utkarsh2102> yes! 
[20:20] <yurtesen> I must have missed some e-mails somehow... btw what is "frr"
[20:21] <sarnold> yurtesen: the replacement for quagga https://frrouting.org/
[20:29] <ahasenack> waveform: hah, just spent a couple of hours debugging an odd DEP8 error in a debian sid container (while in ubuntu it works), only to realize debian still hasn't fixed that dpkg-reconfigure restart bug in debconf
[20:30] <ahasenack> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010677
[20:30] <ahasenack> any idea why that stalled over there?
[20:30] <waveform> ahasenack, argh -- someone did mention that on salsa somewhere the other day and I completely forgot to reply to it -- I (think?) I proposed that change in salsa for dpkg-reconfigure already but I've been too busy with other things to check on it
[20:31] <ahasenack> this bug I linked I think is against the wrong package even, it's against debhelper
[20:31] <ahasenack> there is one against slapd too https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010678
[20:33] <waveform> oh, https://salsa.debian.org/pkg-debconf/debconf/-/merge_requests/10 -- that's the PR I made for dpkg-reconfigure and I still haven't replied to Colin's remarks ... right, will try and get to that shortly
[20:33] <ahasenack> thx waveform !
[20:35] <waveform> oh, now I remember, I needed to research his suggesetion about postrm upgrade and didn't find the time with the jammy release looming. Right, I'll try and get that done tomorrow night (won't have time tonight unfortunately)
[20:45] <ahasenack> why tomorrow, it's saturday :)
[20:45]  * ahasenack double checks
[20:45] <ahasenack> yes, it's saturday
[21:12] <znf> Hi.
[21:12] <znf> Big question
[21:12] <znf> Where the f* is a mini.iso for 22.04 ?
[21:13] <sarnold> I don't think that's existed for a few years, it was part of the old debian-installer
[21:13] <znf> yes please, give me that
[21:13] <znf> the new subiquity stuff is... horrid
[21:19] <znf> no really, is there no way to build a mini.iso?
[21:22] <athos> oh... ahasenack I just spent a few hours deebugging postgresql-common autopkgtest failures; which are related to this dpkg-reconfigure issue; thanks, sergiodj, for pointing me to the issue :D
[21:29] <Soni> how do you setup a basic FORWARD = DROP(?) and make it load that way?
[21:32] <athos> ahasenack: the interesting part is that for the postgresql-common issue, it is the opposite: the dep8 tests pass in debian and fail in ubuntu
[21:32] <Soni> hmm, actually no...
[21:34] <znf> ok, so, basically, the new installer just threw away years of preseeding systems for the old debian-installers that DCs, MSPs and other similar businesses have relied on
[21:34] <znf> And now doing the Netboot requires you to, uhm, download a 1.4GB ISO each time you boot 
[21:34] <sergiodj> waveform: heya.  what athos found is interesting.  we will keep an eye to see if it could be a regression
[21:34] <znf> ?!
[21:36] <Soni> hmm no that doesn't seem to have worked...
[21:39] <Soni> aside from setting net.ipv6.conf.wg0.forwarding=1 what else is needed for local forwarding?
[21:43] <znf> Why can't I create a DOS partition table in the new installer, wtf 
[21:44] <sarnold> try switching your BIOS to boot legacy (or CSM) and see if that works?
[21:45] <znf> It's a VM booted in BIOS mode
[21:46] <znf> creating the partition table manually, with fdisk... still makes the installer create a bios_boot partition
[21:47] <znf> https://i.imgur.com/uWPnnFP.png
[21:47] <znf> how the hell is it required if: 1. it's not GPT, 2. I'm not in UEFI mode 
[21:48] <znf> great, I can't even change mount options for the partitions
[21:49] <Soni> hmm, we can't figure out how to make packets from ipv6_prefix::2 reach ipv6_prefix::3 through ipv6_prefix::1 (where ipv6_prefix is chosen from fd00::/8)...
[21:50] <sdeziel> Soni: what you describe sounds like trying to have routing but inside the same subnet (ipv6_prefix::/64) which is not what you want normally
[21:51] <Soni> sdeziel: cba to setup p2p wireguard links
[21:52] <Soni> just wanna let the server route it
[21:52] <Soni> sdeziel: also wait, outside the server context, how does wifi work without same-subnet routing?
[21:53] <Soni> like, you have a wired LAN, and then you have a wireless LAN, and those are 2 different interfaces and you need a router to bring them together, yeah?
[21:54] <sdeziel> Soni: sorry I don't have much time but if you want to forward IPv6 between NICs, you typically want to set `net.ipv6.conf.all.forwarding=1`
[21:54] <Soni> ... anyway we digress
[21:54] <Soni> so how do you forward packets within the same interface when the hosts can't see eachother because it's a VPN?
[21:55] <znf> Does subiquity allow for incomplete auto-configurations like the debian installer?
[21:56] <sarnold> znf: if you're booting vms, why not use the cloud images instead and skip the install step entirely?
[21:56] <znf> because I want my own custom install instead of the cloud images
[21:57] <sarnold> znf: I *think* "You can designate particular sections in the config as “interactive”, which means the installer will still stop and ask about those." means you can get prompted when you want https://ubuntu.com/server/docs/install/autoinstall
[21:58] <sarnold> https://ubuntu.com/server/docs/install/autoinstall-reference is probably more useful
[21:58] <znf> *sigh*
[21:59] <znf> I'm really not happy about this at all, it's gonna add up hours just to be able to support 22.04 for us, and we're a small company 
[22:03] <znf> the cloud image is EFI... 
[22:04] <tomreyn> and EFI booting is out of question? BIOS support will probably fade sooner or later.
[22:05] <znf> EFI booting in a VM setting just makes no sense, doesn't really provide any advantages, and with OMVF it actually adds extra complexion, as now I have to add a 2nd disk to store EFI Vars...
[22:06] <znf> Besides, our public facing VM system doesn't even support it, as there was no need for it. It would probably confuse clients anyway
[22:08] <znf> Heck, vmware vcenter doesn't even recommend it, it suggest you should use BIOS when you create a new VM 
[22:23] <tomreyn> zmf: so i just downloaded https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64.vmdk (547 MB download) and booted it in bios mode
[22:25] <znf> the .img ones for KVM are UEFI, mine just get stuck like this: https://i.imgur.com/AonaQK8.png
[22:27] <athos> waveform, ahasenack, sergiodj: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1973382
[22:28] <znf> but sure, let me try to convert the vmdk 
[22:29] <tomreyn> you mentioned vmware, so that's why i gave that a try.
[22:30] <znf> Our "private" stuff is in vmware, but our public stuff is kvm :)
[22:30] <znf> I work with both on a daily basis, that's why I mentioned it
[22:33] <znf> meh, it's GPT anyway