[08:38] <apw> sergiodj, looks good, buttons pushed.
[12:02] <ahasenack_> good morning
[13:15] <caribou> Hello, After doing some diagnostics with the kernel team, it appears that the issue with bug LP: #1955655 has to do with some RedHat's grub patches that have not been upstreamed
[13:15] <caribou> So I thought I'd bring it to your attention. So far there is a workaround possible for Jammy but that is still useful to be fixed
[14:54] <sergiodj> apw: thanks
[15:56] <jbicha> didrocks: session-migration seems like a useful thing to have in Debian too
[16:05] <sbraz> juliank: another question about grub: do you know why grub-efi-amd64-signed's postinst script does not honour grub2/update_nvram and always attempts to change the EFI vars? it's really problematic for us
[16:07] <didrocks> jbicha: sure, if someone wants to maintain it there, we can totally push it to Debian
[16:08] <didrocks> happy if someone looks at ensuring that it’s working well with latest debhelper semantics and so on
[17:18] <juliank> sbraz: broken cloud images iirc
[17:19] <juliank> sbraz: ah the unsigned one does that correctly
[17:34] <sbraz> juliank: yup, should i file a bug about that? AFAICT it's a problem debian doesn't have
[19:25] <smoser> anyone have an idea? i'm poking around with sbuild. on one system i'm getting CHROOT_SESSION_PURGE = false . on another it is true.
[19:25] <smoser> man schroot-setup says 'Set to ‘true’ if a session will be purged, otherwise ‘false’.
[19:27] <smoser> but both systems i'm just running sbuild through sbuild-launchpad-chroot.  any idea what that means ?
[19:27] <smoser> its causing me to take the 'exit 0' path at https://git.launchpad.net/~motu/ubuntu/+source/sbuild-launchpad-chroot/tree/etc/schroot/setup.d/90apt-sources#n40
[19:28] <jbicha> do you have anything set in ~/.sbuildrc ?
[19:31] <smoser> no. not on either system. i think i jjust found the difference.  one had 'union-type=overlay' one did not.
[19:32] <smoser> but that doesn't give me any clue as to what it means.
[19:34] <jbicha> that shouldn't make a difference. Are /etc/sbuild/sbuild.conf the same on both systems?
[19:35] <smoser> md5sum says 3d9f80ebf37db6f00583bdb103a5ca21 on both (i think that is stock 20.04 0.79.0-1ubuntu1)
[20:05] <smoser> well, filed https://bugs.launchpad.net/+bugs/1968782
[22:39] <neachdainn> I'm making a personal package for the first time and I've encountered a potential challenge regarding depending on / linking to Python. Is there a way to specify that I want to depend on and link to some available `libpython3 >= 3.8.0` but not be more specific?
[22:41] <neachdainn> I would like this partially because I want to use the most up-to-date version of Python I can but I require _at least_ 3.8, and partially because it would be convenient to not have to make a new package for each Ubuntu version I'm running.