fsmithred | Migration from debian to devuan can be messy. Better to boot one of the live isos, wget the new key and install it in the live session, then install the live system or do a debootstrap install and just add what you want. | 00:05 |
---|---|---|
xisop | Are there any special instructions if I wanted to install libgl1-mesa-dri:i386 libgl1:i386 from a 64 bit install? | 00:13 |
xisop | I'm trying to install steam, though it seems those 386 packages aren't readily available | 00:43 |
xisop | hmm. might be easier to install wine+steam | 00:44 |
debdog | xisop: it's been a long time ago for my last attempt on wine. but a good starting point, for i386 progs and libs is https://wiki.debian.org/Multiarch/HOWTO | 00:48 |
xisop | debdog: will take a look at that | 00:53 |
aitor | xisop: basically you need to add the new architecture to apt | 00:53 |
aitor | dpkg --add-architecture i386 | 00:54 |
aitor | an then install the packages: | 00:54 |
aitor | apt-get install package1:i386 package2:i386... | 00:54 |
aitor | after that, you can remove the architecture: | 00:55 |
aitor | dpkg --remove-architecture i386 | 00:55 |
aitor | Ops, I think you cannot remove the architecture without removing the installed packages previously... | 00:59 |
aitor | as the howto explains: | 00:59 |
aitor | apt-get purge ".*:i386" | 01:00 |
tgoyen | Thanks to all for updating the channel header with the keyring errors. Have a good day/night! | 01:01 |
xisop | so i'm having issues with doing apt update | 01:04 |
xisop | W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.devuan.org/merged chimaera InRelease: The following signatures were invalid: EXPKEYSIG BB23C00C61FC752C Devuan Repository (Amprolla3 on Nemesis) <repository@devuan.org> | 01:04 |
xisop | i ran the dpkg --add-architecture i386 then i get messages like that ^ from apt update | 01:05 |
debdog | xisop: see https://dev1galaxy.org/viewtopic.php?id=5213 | 01:06 |
xisop | oh wow | 01:07 |
debdog | sorry, shit happens | 01:07 |
xisop | nah, you're good! | 01:07 |
xisop | there wasn't really any way of me knowing this had i not dropped in here | 01:07 |
debdog | I have nothing to do do with that. just an ordinary user reading the topic here (after I received a swift kick in the a... from others in here | 01:09 |
xisop | this solved everything | 01:09 |
debdog | just relaing | 01:09 |
xisop | so what was the initial problem? | 01:09 |
debdog | relaying | 01:09 |
debdog | the key exired? | 01:09 |
debdog | p | 01:09 |
debdog | dang, better I have dognap... | 01:10 |
aitor | the same happened to me in april with the repo of gnuinos: http://reisenweber.net/irclogs/libera/_devuan/_devuan.2022-05-04.log.html | 01:14 |
aitor | bye :) | 01:17 |
* joerg hands debdog catnip | 04:04 | |
chomwitt | hi. i trying to do 'sudo apt-get update' i get 'The following signatures were invalid: EXPKEYSIG BB23C00C61FC752C Devuan Repository (Amprolla3 on Nemesis) <repository@devuan.org> | 12:41 |
chomwitt | ' | 12:41 |
NeonLicht | Look at the topic, chomwitt | 12:42 |
chomwitt | NeonLicht, thanks!! | 12:42 |
NeonLicht | No problem, someone told me the exact same before. LOL | 12:43 |
NeonLicht | same thing | 12:43 |
chomwitt | ok . it worked | 12:55 |
NeonLicht | It does. :-) | 13:01 |
Wonka | E: Release file for http://deb.devuan.org/merged/dists/chimaera/InRelease is expired (invalid since 437d 6h 49min 55s). Updates for this repository will not be applied. | 16:00 |
Wonka | got the InRelease file with wget | 16:01 |
Wonka | gpgv --keyring /etc/apt/trusted.gpg.d/devuan-keyring-2022-archive.gpg ./InRelease | 16:01 |
Wonka | all clear... | 16:01 |
Wonka | only "apt update" keeps complaining | 16:01 |
Wonka | one of those days... | 16:03 |
djph | Wonka: read the /topic ;) | 16:04 |
Wonka | djph: I already had the 2022.09.04 keyring installed | 16:04 |
Wonka | I even tested the wget-ed file against it! | 16:04 |
Wizzup | what is your system time set to? | 16:05 |
Wonka | Tue Sep 6 14:05:13 UTC 2022 | 16:05 |
Wonka | just now | 16:05 |
Wonka | looks fine to me | 16:05 |
Wizzup | invalid since 437d seems a bit odd | 16:05 |
Wonka | jop... | 16:05 |
Wonka | cat InRelease > /var/lib/apt/lists/deb.devuan.org_merged_dists_chimaera_InRelease | 16:05 |
Wonka | that's what "solved" it for now | 16:06 |
Wonka | the wgotten file... which was correct... | 16:06 |
Wonka | I think that VM is not even 437 days old | 16:07 |
djph | Wonka: ... and you remembered to dpkg -i the updated keyring file, right? | 16:07 |
djph | (because I might've forgotten that on 2 VM's... :/) | 16:07 |
Wonka | djph: actually, I used "apt install ./..." | 16:08 |
Wonka | djph: I wouldn't know where /etc/apt/trusted.gpg.d/devuan-keyring-2022-archive.gpg should have come from if not that package... | 16:08 |
djph | no idea if that actually works wiht *deb files. I'm far too used to dpkg / apt-get | 16:08 |
Wonka | it dows | 16:09 |
Wonka | does | 16:09 |
Wonka | I think "dpkg -i" actually nags you to use "apt install" now? | 16:09 |
Wonka | because for some reason I switched from dpkg -i to apt install | 16:09 |
Wonka | you need to use ./ for local files though, which is a minor annoyance | 16:10 |
djph | nope | 16:12 |
djph | apt does nag ou if you're using trusted.gpg though | 16:12 |
djph | anyway, yeah, it is in that package (for some reason I expected it to be in /usr... ( | 16:12 |
djph | oh, wait yeah, it's complaining about the repo's InRealease file, no t... *sigh* I need to actually process what I read better :( time for more coffee | 16:14 |
rrq | Wonka: I suggest remove /var/lib/apt/lists/deb.devuan.org_merged_dists_chimaera_InRelease and run "apt-get update" | 16:17 |
Wonka | rrq: well, I replaced it with the known good one, and that made the problem go away | 16:22 |
pon | What does this mean when I go to apt-get update Daedalus? "The following signatures were invalid: EXPKEYSIG BB23C00C61FC752C Devuan Repository (Amprolla3 on Nemesis) <repository@devuan.org> / W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used." | 17:00 |
rrq | pon: go to https://dev1galaxy.org/viewtopic.php?id=5213 | 17:04 |
Guest7436 | Hi. Is there already available and fixed keyrings ISO for download? | 17:04 |
rrq | Guest7436: go to https://dev1galaxy.org/viewtopic.php?id=5213 | 17:04 |
pon | Oh thanks rrq. | 17:05 |
Guest7436 | Thanks but I'd prefer clear install with mirror selection during install. | 17:06 |
rrq | Guest7436: my mistake. some isos are available for testing/confirmation | 17:06 |
rrq | at https://ido.rrq.id.au/download | 17:06 |
Guest7436 | Thank you. | 17:06 |
rrq | feedback about success or issues would be useful | 17:07 |
Guest7436 | I will download and test. Then will reply about my success. | 17:09 |
Guest9059 | Hallo, I can't seem to update my distro. Whenever I enter the _apt update_ command, I get "Signatures were Invalid" error. Please help | 18:21 |
lts | Guest9059: topic has the fix | 18:21 |
Xenguy | .oO( Better to train users to check the /topic than to directly provide the forum URL IMHO ) | 18:49 |
hakerdefo | What's the best and recommended method to fix recent keyring errors in apt? | 19:19 |
rwp | hakerdefo, Please see /topic for fix. | 19:20 |
Guest61 | Hi. I installed the new ISO and it seems keyrings issues are solved. Amd64. Thanks.Can I use new installation permanently or shall I wait for official image? | 19:21 |
fsmithred | Guest61, what you have should be the same as whatever we put up on files.devuan.org when all the isos get built. | 19:23 |
rwp | Guest61, Where did you get the ISO from? Is it already one of the official images? | 19:23 |
hakerdefo | @rwp They have described a couple of methods there. First removes the InRelease file and install the devuan-keyring package while the second method suggests to manually install devuan-keyring packaging. Which one is recommended? | 19:23 |
Guest61 | https://ido.rrq.id.au/download/ | 19:24 |
fsmithred | rwp https://ido.rrq.id.au/download | 19:24 |
fsmithred | that's rrq's server | 19:24 |
Guest61 | Yes from there i downloaded. | 19:24 |
fsmithred | hakerdefo, the second method is a little less confusing | 19:24 |
fsmithred | and easier to do | 19:25 |
rwp | I don't see where this is described I would also recommend the second method of simply installing the devuan-keyring package as that is very straight forward. | 19:26 |
hakerdefo | @fsmithred Second one it'll be then. Thank you and have a nice day ahead! | 19:26 |
fsmithred | :) | 19:27 |
rwp | fsmithred would know! :-) | 19:27 |
hakerdefo | @rwp Thank you for the help dear! I hope @fsmithred knows ;-) | 19:28 |
fsmithred | rwp, instructions are in the forum thread linked in this channel's topic | 19:28 |
fsmithred | yw hakerdefo | 19:28 |
fsmithred | I'm about to upload a fixed desktop-live iso | 19:29 |
fsmithred | if I can remember how to access my own site | 19:29 |
hakerdefo | Cheers & peace guys! Keep up the great work with Devuan guys! Bye for now! | 19:29 |
fsmithred | HA! I got in. | 19:30 |
fsmithred | Here's a devuan desktop-live iso with the new keyring, temporarily on my own site: https://get.refracta.org/files/experimental/devuan_chimaera_4.0_20220906_amd64_desktop-live.iso | 19:33 |
lts | Will there be a postmortem report about the expiration incident? | 19:33 |
fsmithred | not sure what there is to report about what happened. Whoever made the last key gave it a year to expire and didn't set up (or ignored) a reminder. | 19:35 |
fsmithred | we've decided that keys should last the lifetime of the release, so going forward, that will be the policy. I don't know what automatic reminders will be set up. There are a few possibilities. | 19:36 |
fsmithred | I need to go out. Back in about an hour. | 19:36 |
fsmithred | there's about 10 minutes left on my upload (linked a few lines above this.) | 19:38 |
lts | It would be positive PR to have a postmortem report with a summary of changes done to prevent a major incident from happening again. It shows the root cause was identified and that there is a mature management culture driving things. Such a report will help people not to have "someone did something and they fixed it, but who knows will it happen again" thoughts, which many will if they don't drop | 19:45 |
lts | by IRC and ask themselves | 19:45 |
lts | I'm not saying you should say yes or no here, but it would be good to give such a report a thought | 19:45 |
golinux | lts: Perhaps you would like to submit this idea and a draft of such a document to the devuan-dev mail list? | 19:52 |
golinux | I think it is a great idea! | 19:52 |
golinux | We could use more hands on deck though. :D | 19:53 |
lts | I'll type a quick draft (can share via pastebin for example), but I'm afraid some of the details are only known by the devs involved, especially about the changes you describe above. | 20:08 |
golinux | Great and thanks! Don't be shy! There is also #devuan-dev. Probably a better place to post a draft. | 20:17 |
fsmithred | good idea and thanks. A fill-in-the-blanks doc with some good text would be helpful. | 20:21 |
djph | ugh, I hate filling those out at work. Still have no idea how I became the maintainer of those docs | 20:30 |
drdozer | Hi - I'm running latest released devuan and kde, and in kde the alt-f2 runner doesn't seem to want to use my path | 20:34 |
drdozer | it isn't searching the same path as as I have in consoles | 20:36 |
fsmithred | drdozer, I'm seeing the same in xfce. Run xterm -hold -e 'echo $PATH' and it doesn't pick up ~/bin | 20:55 |
fsmithred | I don't know the reason | 20:55 |
drdozer | fsmithred, exactly - I put a ton of stuff in ~/bin that I definitely under no circumstances want system-wide | 20:56 |
drdozer | so for me xterm is using the correct path but krunner isn't | 20:57 |
fsmithred | there might be a setting for it hidden in some of the kde config files in your home | 20:57 |
rwp | fsmithred, That thread just keeps getting longer and longer... | 21:27 |
fsmithred | I deleted the iso I had uploaded because it doesn't have the new version of refractainstaller that has a bug fix that's been waiting to get in. | 22:51 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!