[00:24] <SpaceBass> Hey yall,  I'm hitting an error trying to upgrade a ubuntu server https://paste.debian.net/1252362/
[00:25] <SpaceBass> Going from 20.04 to 22.04 LTS
[00:26] <sarnold> weird, I can't say I've seen that one before; you don't need the -d any more, though, try it without that?
[00:26] <SpaceBass> Tried with and without :/ 
[00:27] <sarnold> :(
[00:28] <mwhudson> do you have PYTHONPATH set to anything unusual?
[00:28] <SpaceBass> Leme check
[00:28] <mwhudson> or is the python or python3 on your path not the one from the archive package?
[00:29] <SpaceBass> It does seem to be in the path, or at least that envar is empty 
[00:29] <SpaceBass> https://paste.debian.net/1252365/
[00:30] <SpaceBass> (I know... root... it is a VM, with snapshots, on an isolated network) 
[00:31] <sarnold> this is grasping at straws, but maybe apt install --reinstall python3-apt  ? 
[00:31] <SpaceBass> That gave me a useful error... my sources are messed up :/ 
[00:32] <sarnold> hah, not what I expected :)
[00:32] <sarnold> if you've got part-way through an upgrade and it failed, it can leave your sources in a *really* unhappy state
[00:33] <SpaceBass> Ok... fixed sources to canonical, re-installed python3-apt, no joy on the do-release-upgrade
[00:34] <SpaceBass> I can always create a new machine and sync everything over... not my favorite plan, but this all started chasing a kerberos key tab goal 
[00:35] <sarnold> :(
[00:35] <SpaceBass> I know, right? :( 
[00:37] <sarnold> maybe sudo debsums -ca  ?  that'll try to point out changed files .. it might report a *lot* depending upon how many config files you've fiddled with
[00:37]  * SpaceBass has fiddled a lot 
[00:37] <SpaceBass> :) 
[00:49] <JanC> python3-apt depends on libapt-pkg6.0 (or whatever the version for that is in 20.04)
[00:49] <SpaceBass> Ill check
[00:51] <JanC> based on the error name it looks like it might happen when loading that library fails (but that's just a guess, I didn't go read the source)
[00:51] <sarnold> yeah, I was hoping debsums would point out something accidentally overwritten or something..
[00:52] <SpaceBass> I have a massive python3 app installed in an env and I'm quite sure I probably did something stupid on the initial install or an upgrade at some point 
[00:53] <SpaceBass> Its a production server so I'll just make a new one with 22.04 and test and then migrate over 
[00:53] <sarnold> not a bad approach
[07:16] <ExeciN> Hi people. I'm trying to install ubuntu server 22.04 on a vps but something goes wrong with the installer right after I confirm the ssh keys fetched from my github account and I get prompted to report this to canonical. Is there a workaround besides moving on without imported keys?
[07:16] <ExeciN> I can set up key authentication later but doing it through vnc is a PitA. I have to somehow aquire the keys (I can maybe post each one on termbin), create/populate .ssh/authorized_keys, change permissions for .ssh and authorized_keys, modify /etc/ssh/sshd_config, reload sshd
[09:15] <tomreyn> ExeciN: i guess i would spawen a shell from the help menu and inspect the logs, and configure /target/etc/ssh/sshd_config to temporarily allow for non Root password authentication - and pick a good password.
[09:20] <ExeciN> At this point is easier to continue without key authentication and set it up later. This can be done using the installer's TUI.
[09:47] <frickler> ExeciN: it would be interesting to see some more details for the "something goes wrong" part. It does work pretty well for me, although I only tested on baremetal so far.
[09:48] <frickler> ExeciN: also regarding the fixup later, you can simply do "curl https://github.com/username.keys > .ssh/authorized_keys"
[11:43] <ExeciN> franksmcb: yeah but I would still have to fix permissions, modify sshd_config and reload sshd
[13:01] <tomreyn> ExeciN: i dont think any of this should be needed, as long as it's owned by the right user.
[13:01] <tomreyn> ExeciN: and indeed, more details would be nice to have.
[16:33] <alireza> I have many ubuntu servers (more than 100), and it is hard for me to update them manually. Is there any automatic solution?
[16:34] <tomreyn> unattended-upgrades
[16:34] <tomreyn> landscape