You are not logged in.
Hello.
I just installed BunsnLabs Helium, and now I need to edit my /etc/sources.list so I can update packages. The present state of the file is:
#deb cdrom:[Debian GNU/Linux 9.6 _Helium_ - Snapshot i386 LIVE/INSTALL Binary 20181113-15:45]/ stretch contrib main non-free
Does anyone have any idea how to edit it?
Thanks in advance.
Offline
The very first sticky thread at the beginning of this forum section (^ look up ) is Sources - sources.list and backports details
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
The very first sticky thread at the beginning of this forum section (^ look up
) is Sources - sources.list and backports details
I followed your instructions and I got this:
luiz@bunsen:/etc/apt/sources.list.d$ sudo apt-get update
Ign:1 https://deb.debian.org/debian stretch InRelease
Hit:2 https://deb.debian.org/debian-security stretch/updates InRelease
Hit:3 https://deb.debian.org/debian stretch-updates InRelease
Hit:4 https://deb.debian.org/debian stretch-backports InRelease
Hit:5 https://deb.debian.org/debian stretch Release
Get:6 https://eu.pkg.bunsenlabs.org/debian stretch-backports InRelease [5,183 B]
Ign:6 https://eu.pkg.bunsenlabs.org/debian stretch-backports InRelease
Get:7 https://eu.pkg.bunsenlabs.org/debian helium InRelease [5,197 B]
Ign:7 https://eu.pkg.bunsenlabs.org/debian helium InRelease
Fetched 10.4 kB in 2s (4,214 B/s)
Reading package lists... Done
W: GPG error: https://eu.pkg.bunsenlabs.org/debian stretch-backports InRelease: The following signatures were invalid: EXPKEYSIG A0673F72FE62D9C5 (BunsenLabs Repository Signing Key) <>
W: The repository 'https://pkg.bunsenlabs.org/debian stretch-backports InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: https://eu.pkg.bunsenlabs.org/debian helium InRelease: The following signatures were invalid: EXPKEYSIG A0673F72FE62D9C5 (BunsenLabs Repository Signing Key) <>
W: The repository 'https://pkg.bunsenlabs.org/debian helium InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Is it OK? Did I do the right thing?
Offline
hello! look here to see if this guide will help you.
"Kaum macht [Mensch]* es richtig, funktioniert es sofort!"
BL-Kitchen Codeberg
Offline
hello! look here to see if this guide will help you.
Yes, try:
sudo apt-key adv --keyserver keys.gnupg.net --recv-keys A0673F72FE62D9C5
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
Naik wrote:hello! look here to see if this guide will help you.
Yes, try:
sudo apt-key adv --keyserver keys.gnupg.net --recv-keys A0673F72FE62D9C5
I tried it, and I got
luiz@bunsen:~$ sudo apt-key adv --keyserver keys.gnupg.net --recv-keys A0673F72FE62D9C5
Executing: /tmp/apt-key-gpghome.KZT2CILvmf/gpg.1.sh --keyserver keys.gnupg.net --recv-keys A0673F72FE62D9C5
gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory
gpg: connecting dirmngr at '/tmp/apt-key-gpghome.KZT2CILvmf/S.dirmngr' failed: No such file or directory
gpg: keyserver receive failed: No dirmngr
Should I really worry about this? I ran Debian for several years, always getting this type of messages about expired keys when I ran apt-get update, and apparently never had any serious problems caused by that.
Offline
Should I really worry about this? I ran Debian for several years, always getting this type of messages about expired keys when I ran apt-get update, and apparently never had any serious problems caused by that.
You can not install from repo that has expired key! So, you can not install from BunsenLab repo. I think that to be a problem...
When I import key on an Lithium system, I get:
# apt-key adv --keyserver keys.gnupg.net --recv-keys A0673F72FE62D9C5
Executing: /tmp/apt-key-gpghome.j1Q0wEEyRN/gpg.1.sh --keyserver keys.gnupg.net --recv-keys A0673F72FE62D9C5
gpg: key A0673F72FE62D9C5: " (BunsenLabs Repository Signing Key) <>" 1 new signature
gpg: Total number processed: 1
gpg: new signatures: 1
I do not know why your system cant import key.
Maybe you can run:
$ sudo gpg --import <(wget -qO- https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc)
Else, consider reinstalling.
// Regards rbh
Please read before requesting help: "Guide to getting help", "Introduction to the Bunsenlabs Lithium Desktop" and other help topics under "Help & Resources" on the BunsenLabs menu
Offline