=== RAOF_ is now known as RAOF [06:11] @pilot out === ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A [11:41] RAOF, do you know why bug 2029473 hasn't made it into proposal yet? [11:41] -ubottu:#ubuntu-devel- Bug 2029473 in software-properties (Ubuntu Xenial) "Backport Ubuntu Pro to Xenial" [High, Fix Committed] https://launchpad.net/bugs/2029473 [11:42] s/proposal/proposed [11:45] nteodosio, he's probably eod at this time but maybe other SRU reviewers can help there, unsure if they regularly review the xenial queue [13:27] Ah, so maybe ^bdmurray? [14:01] is the TPM support for FDE in the current mantic installer? I downloaded the daily image yesterday, and only see the usual lvm + passphrase encryption. Or will that use TPM, and leave the passphrase as a backup to get in? [14:16] ahasenack, TPM will only be enable on some hardware, also we had a bug that it was not working with 'minimal' (which is the default), that should be fixed in today's daily [14:17] seb128: what is the indication that it's available, another option under "advanced"? [14:17] I'm trying with a VM, where I did enable TPMv2, which used to satisfy windows 11 [14:17] (and am also using a non-minimal install) [14:19] ahasenack, yes, it should be in the advanced dialog ... any error in journalctl | grep TPM? [14:20] "not encrypting device storage as checking TPM gave: secure boot is disabled" [14:20] I used uefi boot, and UEFI x86_64: /usr/share/OVMF/OVMF_CODE_4M.secboot.fd specifically [14:20] ahasenack, that's probably why you don't see the option [14:21] but mokutil agrees that secure boot is disabled [14:28] ^ was sorted out on another channel but as a follow up, /usr/share/OVMF/OVMF_CODE_4M.ms.fd is the right file to use === sem2peie- is now known as sem2peie [16:45] It seems like libx32lsan0-amd64-cross and lib32lsan0-amd64-cross are still in mantic's Universe repository, they were last built by `gcc-13-cross (9ubuntu3)`. However, they don't appear on the NBS site. Did they slip through the cracks, maybe on account of having a different version from their source package? === bdmurray changed the topic of #ubuntu-devel to: Archive: Mantic Beta Freeze | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A [20:04] UnivrslSuprBox: they haven't entirely slipped through the cracks, in that https://ubuntu-archive-team.ubuntu.com/proposed-migration/mantic_outdate.txt knows about them; it's just that this is the last report to be settled because we normally drive things through the NBS report instead [20:08] vorlon: interesting, thank you. I'll make my code more resilient against this situation (was going to anyway, especially so now that it's an expected state of the archive for a short time)