[01:20] <lubot> [telegram] <teward001> @Leokolb @guiverc we noticed an oddity in cala in the Lubuntu and Studio installers - only because of a critfail in STudio's installer - the Cala chroot towards the end of installation gets dns resolution failures when it tries to apt update, even though the live iso has valid DNS settings and can do DNS reso.  The failure of the chroot to have DNS resulted in the hard fail that Studio was having (they've since pushed a change to th
[01:20] <lubot> [telegram] <teward001> just to make sure I didn't fubar something in my QEMU testings
[01:21] <lubot> [telegram] <teward001> if you happen to get a moment to test and see if you get the same issue, then that'd be good info to know we can open cala / chroot bugs to deep dive next cycle
[01:21] <lubot> [telegram] <teward001> it's a non-breaking problem, but it's something I just want to rule out being *my* system
[01:21] <lubot> [telegram] <teward001> (I had to sudo -E calamares --debug on the CLI to make it get the proper debug log data though)
[01:21] <guiverc> are you talking impish?
[01:21] <lubot> [telegram] <teward001> correct
[01:21] <lubot> [telegram] <teward001> current Impish images
[01:22] <lubot> [telegram] <teward001> i just want to make sure my system isn't the only one seeing the inside-chroot dns resolve problems when Cala runs apt update stuff.
[01:22] <lubot> [telegram] <teward001> not a prioirty issue but if one of you two happens to have a few moments and can do a test run of the installer and see if the issue is repro'd that'd be nice.
[01:23] <lubot> [telegram] <teward001> because it's *odd* the chroot wouldn't have DNS when the installer live OS has DNS
[01:23] <lubot> [telegram] <teward001> (it caused breaking in Studio because they don't ship zram-config but their settings still removed it, they pushed a fix for *that* today that'll fix their hard fail next ISO, but I want to make sure I didn't break something in my env)
[01:24] <lubot> [telegram] <teward001> s/next ISO/next daily ISO build/
[01:24] <lubot> [telegram] <teward001> this DOES, however, explain why post-install Lubuntu does not have updated apt information, because the chroot didn't have DNS resolution.
[01:24] <lubot> [telegram] <teward001> which just irked me a bit
[01:24] <lubot> [telegram] <teward001> (never happens on the other flavors)
[01:25] <guiverc> ack.. will aim for it this arvo or tomorrow
[01:25] <lubot> [telegram] <teward001> yep no rush
[01:25] <lubot> [telegram] <teward001> it's not got a bug attached to it 'cause it's a nonbreaking issue, just something I noticed during my Studio deep debugging and some confirmation of the same in the same QEMU environment with Lubuntu installer.
[01:25] <lubot> [telegram] <teward001> and something to look at into the future why the chroot doesn't have dns / network connectivity when cala's trying to apt update.
[01:35] <Eickmeyer> guiverc: Thanks for doing this. :)
=== genii is now known as genii-core
[06:37] <lubot> [telegram] <Leokolb> will check this later this am (re @teward001: correct)
[07:01] <guiverc> thanks @Leokolb, I'll likely not get to it tomorrow, and more eyes are better
[09:07] <lubot> [telegram] <Leokolb> Just ran a quick test in a VirtualBox - and yes - Temporary failure resolving "...etc etc ..) in the debug log - will run a bare metal test later - hope this helps (re @teward001: yep no rush)
[09:11] <lubot> [telegram] <Leokolb> Yes @teward001 - it is strange as the installer selects correct timezone/location etc..
[09:21] <lubot> [telegram] <Leokolb> Of course @teward001 same result on bare meta box
=== genii-core is now known as genii
[14:52] <lubot> [telegram] <teward001> @Leokolb thanks for confirming.
[14:52] <lubot> [telegram] <teward001> So this seems to be either a chroot or a Cala bug in how it's mounting the chroot I'd assume.
[14:52] <lubot> [telegram] <teward001> well, time ot add that to the JJ series of tasks for us to dig into
[14:53] <lubot> [telegram] <teward001> (since it's not just Lubuntu affected)
[14:53] <lubot> [telegram] <teward001> @Leokolb i think the *installer* uses the standard system resolver libs and such, which as they're run outside the chroot in the live environment it just inherits the networking on ${LIVE_ENV}
[14:54] <lubot> [telegram] <teward001> but that instance in the chroot is interesting.  not sure if a cala or chroot bug.
[14:55] <lubot> [telegram] <teward001> fyi @kc2bez ^^ that looks like a task for us to hunt down in JJ series
[15:25] <lubot> [telegram] <kc2bez> Yup, I agree. I need to dig into it further.
[16:02] <lubot> [telegram] <Leokolb> @teward001 @kc2bez Good to have something to do in future? :)
[16:02] <lubot> [telegram] <kc2bez> I hate it when I get bored 🤣
[16:03] <lubot> [telegram] <Leokolb> Bored?Hope it is not like drilled! (re @kc2bez: I hate it when I get bored 🤣)
[16:06] <lubot> [telegram] <kc2bez> 😂 (re @Leokolb: Bored?Hope it is not like drilled!)
=== genii is now known as genii-core