[00:00] <lubot> <lynorian> yes I  have somehoow gotten used to that
[00:00] <lubot> <lynorian> I don't have that in the manual dang it
[00:00] <wxl> if we fix this, it will only be for 19.10
[00:00] <lubot> <kc2bez> @kc2bez [steam], or wine or lutris
[00:01] <lubot> <kc2bez> what will happen for 20.04?
[00:02] <wxl> if we get this fixed, then it will Just Work™
[00:03] <lubot> <kc2bez> I follow you now.
[00:08] <lubot> <HMollerCl> The same command works, at this time, in 20.04
[00:08] <wxl> which command
[00:08] <wxl> ?
[00:09] <lubot> <HMollerCl> sudo dpkg --add-architecture i386
[00:09] <wxl> yeah it works fine, but it needs to be implemented ahead of time
[00:09] <wxl> users shouldn't be required to do it themselves
[00:10] <wxl> to get a feel for the experience, get a fresh install and open discover and install steam
[00:10] <lubot> <kc2bez> what about default settings?
[00:10] <wxl> thing is i want it installed ASAP because maybe someday in the future some package we have in the packageset has an i386 requirement
[00:10] <lubot> <kc2bez> maybe a postinst script?
[00:11] <wxl> at that point we can do it as a pre-inst in packages, but i'd like it earlier than that
[00:12] <lubot> <kc2bez> it would land in live that way (not 19.10 live)
[00:12] <lubot> <kc2bez> there should be a whitelist for all the 386 packages I think.
[00:13] <wxl> i'm hoping @tsimonq2 has a better idea
[00:14] <lubot> <kc2bez> @tsimonq2 is a pretty knowledgeable person
[00:17] <lubot> <tsimonq2> Ubuntu did it in Ubiquity so we should do it in Calamares.
[00:18] <lubot> <tsimonq2> Add a shellprocess module which runs the command enabling it
[00:19] <lubot> <tsimonq2> As for whether it goes before or after the packages module, I'm not sure. Does this command need sudo apt update to be effective? If so, should we assume users know to do that?
[00:19] <lubot> <tsimonq2> Additionally, can this be done without network? Does this command automatically run sudo apt update?
[00:19] <wxl> well if we could get it in the squashfs we'd have a one up on ubuntu, because it'd work in live
[00:21] <lubot> <tsimonq2> In my opinion, in the squashfs is the wrong answer. It doesn't feel right to do that. I'd be in favor of doing it via casper if we REALLY wanted it in live, but I definitely think at minimum we need a Cala module
[00:22] <lubot> <tsimonq2> The squashfs is supposed to be as clean as we can possibly get it. Plus, it'd be really hacky to test
[00:23] <lubot> <tsimonq2> As for how you'd test a casper change, I don't quite remember. cyphermox or TJ- may know
[00:24] <lubot> <tsimonq2> But as wxl may be the only one who knows what casper's role is, casper is the software specific to the live image that e.g. sets up the live user with autologin and such
[00:24] <wxl> my concern is what the future may bring
[00:24] <wxl> i guess for the time being we can just get the shellprocess module and call it good
[00:24] <lubot> <tsimonq2> Is there another angle I'm not addressing here?
[00:25] <lubot> <tsimonq2> We'd have live and install covered by this
[00:25] <wxl> oh casper? well, yeah i guess we could look into that, too
[00:26] <wxl> could you put that in the task with maybe a nudge to TJ-? 
[00:27] <TJ-> I think I missed the start of this was not in channel or AWOL
[00:28] <wxl> @tsimonq2: here's the heavy lifting of the command https://git.dpkg.org/cgit/dpkg/dpkg.git/tree/src/main.c#n452
[00:28] <lubot> <tsimonq2> @TJ- [<TJ-> I think I missed the start of this was not in channel or AWOL], How do you test casper changes wrt an ISO?
[00:29] <wxl> omg their error functions are ohshit or ohshite X''''''''D
[00:32] <TJ-> tsimonq2: very long time since I needed to do that... vaguely... I *think* I had an extracted installer ISO image file-system booted into a virtual machine (since in almost all cases an 'ISO' is actually booted as a regular MBR/GPT image and not ISO9660+El-Torito)
[00:32] <wxl> it doesn't seem like it does any apt update although i'm not sure if it's necessary
[00:33] <TJ-> tsimonq2: so losetup with some 'tweaks' to ensure it correctly presents the MBR/GPT and partitions
[00:33] <TJ-> wxl: what are you referring to? "dpkg --add-architecture" ?
[00:34] <wxl> TJ-: yeah
[00:34] <TJ-> wxl: as far as I know all that does is add to /var/lib/dpkg/arch
[00:34] <TJ-> dpkg doesn't 'know' about apt 
[00:34] <wxl> whether or not it *needs* it, i don't know. my guess is no. 
[00:35] <wxl> there are only different pools/dists, not necessarily separate lists for archs
[00:36] <wxl> if anyone'
[00:36] <wxl> s curious what i mean http://us.archive.ubuntu.com/ubuntu/
[00:37] <wxl> also this is a lot of fun http://us.archive.ubuntu.com/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/
[00:37] <TJ-> yes, it's only relevant for binary packages. As I recall Apt internally uses /var/lib/dpkg/arch to determine the default arch (first line) or verify <package>:otherarch is valid
[00:38] <TJ-> Same as putting arch-limiters/specifiers in sources.list "deb [arch=i386] ..."
[00:38] <lubot> <kc2bez> @wxl [<wxl> also this is a lot of fun http://us.archive.ubuntu.com/ubuntu/ubuntu/ubunt …], You're awfully deep there.
[00:38] <wxl> @kc2bez: you can go to ∞ if you want
[00:39] <lubot> <tsimonq2> @wxl [<wxl> @kc2bez: you can go to ∞ if you want], Actually, that's not true.
[00:39] <lubot> <tsimonq2> Believe me, I know, I've tried. XD
[00:39] <wxl> (an aside: default compose key for ° is compose-oo while ∞ is compose-88 which doesn't seem totally appropriate)
[00:39] <wxl> OOOH YOU"RE RIGHT
[00:39] <wxl> http://us.archive.ubuntu.com/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/ubuntu/
[00:40] <lubot> <kc2bez> When you launch Discover doesn't it do an apt update
[00:40] <TJ-> It's an HTTP server, can't have too many symlinks :)
[00:42] <wxl> right @kc2bez 
[00:44] <wxl> so where would we make this change in casper again? i forgot from last time
[03:07] <theloudspeaker> Why launch discover to test in the firat place ? Just do a fresh install. Don't connect internet. Do the add architecture command.
[03:07] <theloudspeaker> I can try this in a couple of different ways as needed on a fresh install on hardware later today.
[03:09] <theloudspeaker> Also, @guiverc read your latest comment on T30, sad that grub ditched us and works with mate-grub-theme. :/ But hey atleast now we are sure it wasn't a bug. I will just go and place the files to someother place this time. :) Hopefully will work.
[03:11] <guiverc> I could re-install on uefi (without encryption; chose encryption as it was very different options to prior install-test... rather than what was easiest for your grub testing..)
[04:36] <lubot> <The_LoudSpeaker> Probably a uefi install without encryption might work. But I am not so hopeful about it.
[16:35] <wxl> OMG WHY DOES SOURCEFORGE SUCK SO BADDDDDDDDD
[17:04] <theloudspeaker> Lol! What happened?
[17:04] <wxl> you broke
[17:05] <wxl> linux-generic-hwe-18.04 : Depends: linux-image-generic-hwe-18.04 (= 5.3.0.28.96) but it is not going to be installed
[17:05] <wxl> whatever
[17:06] <theloudspeaker> ?
[17:11] <genii> !info linux-image-generic-hwe-18.04
[17:11] <ubot93> linux-image-generic-hwe-18.04 (5.4.0.9.11, focal): Generic Linux kernel image (dummy transitional package). In component main, is optional. Built by linux-meta. Size 2 kB / 16 kB. (Only available for amd64, armhf, arm64, ppc64el, s390x.)
[17:12] <genii> Hm
[17:23] <theloudspeaker> K!