sedrosken | So tonight my game plan is to reinstall ASCII on my laptop in a minimal config, dist-upgrade to Beowulf, and then set it up with my choice in software | 03:14 |
---|---|---|
gillb_ | i need to rebuild kernel with scsi (CONFIG_BLK_DEV_SR=y) on the jetson nano. think it's ok to try with stock linux 4.19.0-6-arm64 or is it likely i need something propietary in nvidia's kernel? | 13:00 |
gnarface | good question | 13:05 |
gillb_ | well i can start with zcat /proc/config.gz > jetsonnanokernel.cfg and then just change that one thing, right | 13:42 |
gillb_ | and should be good to go since both are 4.19.x | 13:42 |
gillb_ | that's unsettling - something deleted /usr/binvivaldi-stable | 13:48 |
gillb_ | oh apt did | 14:28 |
gillb_ | is there any reason to keep this Noto font spam | 15:20 |
markizano | https://cloud.docker.com/repository/docker/markizano/devuan | 16:51 |
markizano | not that anyone needs help finding this since I already saw like 7 pulls, LoL | 16:51 |
markizano | but going to attempt to keep a Docker image alive that will have the base install at least. | 16:51 |
systemdlete2 | How can I tell if I have ascii 2.0 or ascii 2.1? Can I simply do an upgrade, or do I need to re-install from ISO? Thanks. | 17:38 |
systemdlete2 | (Also, is there a way to include this info in the /etc/os-release file? That would be convenient) | 17:39 |
furrywolf | systemdlete2: it's an incremental upgrade, apt-get update and apt-get upgrade will get you everything, and you should already have most of it if you've been upgrading regularly. | 17:51 |
systemdlete2 | OK, thanks. Yeah, I've been doing upgrades periodically. Last was about 2 days ago. | 17:52 |
systemdlete2 | As far as updating the os-release file though? Why or why not? | 17:52 |
furrywolf | it's not an entirely seperate version... it's just newer packages. | 17:54 |
furrywolf | it's mostly that a set of new installer isos were built | 17:56 |
golinux | The point release was to include important security updates like the apt bug so a new installation wouldn't be at risk ootb | 18:12 |
systemdlete2 | this apt bug was discovered as early as January 2019. | 18:32 |
systemdlete2 | It is now getting rolled out? | 18:32 |
systemdlete2 | (yipes) | 18:32 |
systemdlete2 | is there a recipe to detect if damage has occurred? | 18:33 |
morroot | what can be reason for hangs on boot at populating /dev stage? | 18:39 |
morroot | ceres at dell 5575 laptop | 18:41 |
morroot | latest kernel | 18:42 |
furrywolf | well, at a first guess, the most likely problem is running ceres. :) | 18:42 |
furrywolf | I have seen engine swaps by people who were not car people. I can make assumptions. :P | 18:42 |
furrywolf | grr, wrong window. | 18:42 |
systemdlete2 | furrywolf: Any way to detect damage from the apt bug? | 18:42 |
furrywolf | I don't know anything at all about the apt bug. | 18:42 |
systemdlete2 | sorry. | 18:43 |
systemdlete2 | golinux: Any way to detect apt bug damage or compromises? | 18:43 |
morroot | furrywolf, ascii can't recognize embedded video on this laptop | 18:46 |
golinux | systemdlete2: I have no idea | 19:13 |
systemdlete2 | googled it, found no such test | 19:14 |
systemdlete2 | ok, thx | 19:14 |
systemdlete | I need help with my apt configuration. Somehow, something I did messed things up. If I try to do apt-get, for instance, I get an avalanche of errors about missing public keys | 22:42 |
systemdlete | I am not sure what happened, what I did, what update attempts did, etc. | 22:42 |
systemdlete | Is there a neat-and-clean way of simply rebuilding whatever is missing? | 22:42 |
systemdlete | I looked at a number of pages about importing public keys, but I can't seem to give it the right keyserver | 22:43 |
systemdlete | this is occurring in an ascii VM which I will be using as a backup appliance | 22:44 |
systemdlete | (what is the keyserver name anyway?) | 22:46 |
golinux | systemdlete: Maybe this? | 23:09 |
golinux | Please make sure you have the latest devuan-keyring package with apt-get install devuan-keyring | 23:09 |
systemdlete | I just re-installed devuan-keyring. I uninstalled it, then installed it. | 23:09 |
sedrosken | You may have to fetch the keyring deb with another machine and dpkg -i it if apt-get won't do it | 23:09 |
sedrosken | Oh | 23:09 |
sedrosken | Oof | 23:09 |
sedrosken | Reinstalling ASCII and dist-upgrading to Beowulf went smoothly and now I have a new enough firefox-esr that my extensions all install | 23:11 |
sedrosken | Took a bit longer than I would have liked but that's more on my internet connection than anything | 23:11 |
systemdlete | sedrosken: oof? | 23:12 |
systemdlete | out of office? | 23:12 |
sedrosken | I'm guessing reinstalling the keyring didn't fix it? | 23:12 |
sedrosken | No, just an expression of sympathy pain | 23:12 |
systemdlete | nope. No help | 23:12 |
sedrosken | Yeah that's about the only thing I could think of | 23:13 |
systemdlete | also when trying to install keys, I get all these errors about invalid packets | 23:13 |
sedrosken | Oh s | 23:13 |
systemdlete | yeah | 23:13 |
systemdlete | it's really a mess now | 23:13 |
sedrosken | Very odd | 23:13 |
systemdlete | golinux, sedrosken: is there a tool to kind of reset/rebuild the apt keys directory area? | 23:14 |
sedrosken | No idea | 23:16 |
systemdlete | ok, thanks | 23:16 |
systemdlete | I guess I need to start a rebuild from scratch. | 23:16 |
sedrosken | I just remembered the snippet about the keyring, that's why I piped up about it | 23:17 |
systemdlete | which sucks, but might be faster than trying to dissect THIS disaster | 23:17 |
sedrosken | Im actually very stupid to be honest | 23:17 |
systemdlete | no, you made a good suggestion. I appreciate it. | 23:17 |
systemdlete | debian's packaging system is one of those mysterious areas I am terrified of | 23:17 |
systemdlete | other people just glide through it without any pain | 23:18 |
systemdlete | ok guys, later | 23:18 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!