Dist upgrade

sverdo · 2021-01-21 20:08:58

Hello, I come back with my distro update issue, I changed my source.list and my bunsen.list, that fixed some issues, but not all. I am attaching the terminal message to you, as I am France, there are some messages in French. Sorry!
Can you help me and thank you all!

Ign:1 http://ftp.debian.org/debian stretch InRelease
Atteint:2 http://deb.debian.org/debian stretch-backports InRelease
Atteint:3 http://ftp.debian.org/debian stretch-backports InRelease
Atteint:5 http://ftp.debian.org/debian stretch-updates InRelease
Atteint:6 http://ftp.debian.org/debian stretch Release
Atteint:8 http://packages.microsoft.com/repos/vscode stable InRelease
Réception de:4 http://eu.pkg.bunsenlabs.org/debian lithium InRelease [6 362 B]
Réception de:7 http://eu.pkg.bunsenlabs.org/debian buster-backports InRelease [5 154 B]
Ign:4 http://eu.pkg.bunsenlabs.org/debian lithium InRelease
Ign:7 http://eu.pkg.bunsenlabs.org/debian buster-backports InRelease
11,5 ko réceptionnés en 0s (13,4 ko/s)
Lecture des listes de paquets... Fait
W: Erreur de GPG : http://eu.pkg.bunsenlabs.org/debian lithium InRelease : Les signatures suivantes ne sont pas valables : EXPKEYSIG A0673F72FE62D9C5 Jens John (BunsenLabs Repository Signing Key) <dev@2ion.de>
W: The repository 'http://pkg.bunsenlabs.org/debian lithium 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: Erreur de GPG : http://eu.pkg.bunsenlabs.org/debian buster-backports InRelease : Les signatures suivantes ne sont pas valables : EXPKEYSIG A0673F72FE62D9C5 Jens John (BunsenLabs Repository Signing Key) <dev@2ion.de>
W: The repository 'http://pkg.bunsenlabs.org/debian buster-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.
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Calcul de la mise à jour... Fait
Les paquets suivants ont été conservés :
bind9-host bunsen-thunar bunsen-utilities tint2 wpasupplicant
0 mis à jour, 0 nouvellement installés, 0 à enlever et 5 non mis à jour.
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Calcul de la mise à jour... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 5 non mis à jour.

Last edited by sverdo (2021-01-21 20:09:56)

rbh · 2021-01-21 20:33:04

sverdo wrote:

Hello, I come back with my distro update issue,

It is better update info in old thread instead of creating a new.

I changed my source.list and my bunsen.list,

You shall never mix sources for different versions of Debian or Bunsenlabs!
Here is a guide how to edit your sourses.
Sources - Lithium sources.list and backports details

Also good for you to read: Upgrading from Helium to Lithium tutorial

I am attaching the terminal message to you, as I am France, there are some messages in French. Sorry!

There is lot of online translation services. Just to copy and paste text and copy the translation.

W: The repository 'http://pkg.bunsenlabs.org/debian lithium InRelease' is not signed.

Your old apt-key was valid until 2020-01-18. You can as root, import the new key:

# wget https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc -O- | apt-key add -

The solutions for you, has been posted several times in the forum.

Edit: edited links to point to right targets

Last edited by rbh (2021-01-21 20:54:29)

phuturism · 2021-01-22 01:00:50

Thou shalt not mix sources!!

ohnonot · 2021-01-22 07:00:34

sverdo wrote:

I am attaching the terminal message to you, as I am France, there are some messages in French.

To make it English, you can prepend "LC_ALL=C" to the command you're using, e.g.:

LC_ALL=C sudo apt update

BTW, please always include the command that produced the output, and always post full output.
And use CODE tags for that, not quote tags. See my signature.

linux_user · 2021-01-22 12:01:54

ohnonot wrote:

To make it English, you can prepend "LC_ALL=C" to the command you're using, e.g.:
LC_ALL=C sudo apt update

Nice

sverdo · 2021-01-22 12:30:18

Hello, I managed to update, but I still have two error messages when I run Synaptic and reload Package information, which I send you:
First

GPG error: https://eu.pkg.bunsenlabs.org/debian buster-backports InRelease: The following signatures were invalid: EXPKEYSIG A0673F72FE62D9C5 Jens John (BunsenLabs Repository Signing Key) <dev@2ion.de>The repository 'https://pkg.bunsenlabs.org/debian buster-backports InRelease' is not signed.Updating from such a repository can't be done securely, and is therefore disabled by default.See apt-secure(8) manpage for repository creation and user configuration details.GPG error: https://eu.pkg.bunsenlabs.org/debian lithium InRelease: The following signatures were invalid: EXPKEYSIG A0673F72FE62D9C5 Jens John (BunsenLabs Repository Signing Key) <dev@2ion.de>The repository 'https://pkg.bunsenlabs.org/debian lithium InRelease' is not signed.

Thank You for all

rbh · 2021-01-22 13:27:24

sverdo wrote:

Hello, I managed to update, but I still have two error messages when I run Synaptic and reload Package information, which I send you:
First

GPG error: https://eu.pkg.bunsenlabs.org/debian buster-backports InRelease: The following signatures were invalid: EXPKEYSIG A0673F72FE62D9C5 Jens John (BunsenLabs Repository Signing Key) <dev@2ion.de>The repository 'https://pkg.bunsenlabs.org/debian buster-backports InRelease' is not signed.Updating from such a repository can't be done securely,[...]

I wrote before that your apt-key is out of date.
I gave you an command to import new key.
If you don't want to import key, you can download latest package with apt-key and install. See the anouncement of outdated apt-key: PSA: bunsen-keyring package refreshes

sverdo · 2021-01-22 13:49:51

But I tried to import the new key with :

# wget https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc -O- | apt-key add -

And here is the message returned by the terminal :

--2021-01-22 14: 42: 29-- https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc
Resolution from ddl.bunsenlabs.org (ddl.bunsenlabs.org)… 78.47.156.207, 2a01: 4f8: c17: 2c09 :: 2
Connection to ddl.bunsenlabs.org (ddl.bunsenlabs.org) | 78.47.156.207 |: 443… connected.
HTTP request transmitted, awaiting response… 302 Moved Temporarily
Location: https://kelaino.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc [next]
--2021-01-22 14: 42: 29-- https://kelaino.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc
Resolution from kelaino.bunsenlabs.org (kelaino.bunsenlabs.org)… 78.47.156.207, 2a01: 4f8: c17: 2c09 :: 2
Connection to kelaino.bunsenlabs.org (kelaino.bunsenlabs.org) | 78.47.156.207 |: 443… connected.
HTTP request transmitted, awaiting response ... 200 OK
Size: 5864 (5.7K) [application / pgp-keys]
Save in: "STDOUT"
Cannot write to "-" (Broken relay (pipe)).

Last edited by sverdo (2021-01-22 13:58:13)

ohnonot · 2021-01-22 19:59:19

sverdo wrote:

wget https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc -O- | apt-key add -

Im pretty sure that should be

wget https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc -O - | apt-key add -

(additional space between -O and -)

sverdo · 2021-01-22 20:25:26

I have try your response but I have the same message returned by terminal

--2021-01-22 14: 42: 29-- https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc
Resolution from ddl.bunsenlabs.org (ddl.bunsenlabs.org)… 78.47.156.207, 2a01: 4f8: c17: 2c09 :: 2
Connection to ddl.bunsenlabs.org (ddl.bunsenlabs.org) | 78.47.156.207 |: 443… connected.
HTTP request transmitted, awaiting response… 302 Moved Temporarily
Location: https://kelaino.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc [next]
--2021-01-22 21: 27: 29-- https://kelaino.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc
Resolution from kelaino.bunsenlabs.org (kelaino.bunsenlabs.org)… 78.47.156.207, 2a01: 4f8: c17: 2c09 :: 2
Connection to kelaino.bunsenlabs.org (kelaino.bunsenlabs.org) | 78.47.156.207 |: 443… connected.
HTTP request transmitted, awaiting response ... 200 OK
Size: 5864 (5.7K) [application / pgp-keys]
Save in: "STDOUT"
Cannot write to "-" (Broken relay (pipe)).

rbh · 2021-01-22 21:01:55

sverdo wrote:

I have try your response but I have the same message returned by terminal
[...]
Cannot write to "-" (Broken relay (pipe)).

You will not get error if you run it as root.
If command is preseeded by "$", it means command can be run by regular user.
If command is preseeded by "#", it means command shall be run by root.
And, i wrote that you shall run it as root.
And, it does not matter if you run mine or ohnonot's version.

Last edited by rbh (2021-01-22 21:02:21)

ohnonot · 2021-01-23 09:31:24

Maybe a better method here:
https://forums.bunsenlabs.org/viewtopic.php?id=7151

rbh · 2021-01-23 10:06:32

ohnonot wrote:

Maybe a better method here:
https://forums.bunsenlabs.org/viewtopic.php?id=7151

Both has advantages and disadvantages. But, not heavyweights in any direction. I can not se that the scales weigh down for any of the methods.
And, I informed of both of them...

rbh · 2021-01-23 11:11:12

If importing from commandline, maybe better to insert sudo after pipe:

$ wget https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc -O- | sudo apt-key add -

sverdo · 2021-01-23 15:50:54

Hello, thank you, the problem is finally solved thanks to you, it was I who made the mistake of not being root, but sudo!
There are still some warning at startup (ACPI)

hhh · 2021-01-23 19:21:22

^ Post the warning(s), please.

ohnonot · 2021-01-24 08:30:32

sverdo wrote:

Hello, thank you, the problem is finally solved thanks to you, it was I who made the mistake of not being root, but sudo!

This means that you didn't post the actual command you entered, but just wrote something up?

sverdo wrote:

# wget https://ddl.bunsenlabs.org/ddl/BunsenLabs-RELEASE.asc -O- | apt-key add -

Please, when sharing code/output, always copy-paste the complete output, including the complete command issued.

#1 2021-01-21 20:08:58

Dist upgrade

#2 2021-01-21 20:33:04

Re: Dist upgrade

#3 2021-01-22 01:00:50

Re: Dist upgrade

#4 2021-01-22 07:00:34

Re: Dist upgrade

#5 2021-01-22 12:01:54

Re: Dist upgrade

#6 2021-01-22 12:30:18

Re: Dist upgrade

#7 2021-01-22 13:27:24

Re: Dist upgrade

#8 2021-01-22 13:49:51

Re: Dist upgrade

#9 2021-01-22 19:59:19

Re: Dist upgrade

#10 2021-01-22 20:25:26

Re: Dist upgrade

#11 2021-01-22 21:01:55

Re: Dist upgrade

#12 2021-01-23 09:31:24

Re: Dist upgrade

#13 2021-01-23 10:06:32

Re: Dist upgrade

#14 2021-01-23 11:11:12

Re: Dist upgrade

#15 2021-01-23 15:50:54

Re: Dist upgrade

#16 2021-01-23 19:21:22

Re: Dist upgrade

#17 2021-01-24 08:30:32

Re: Dist upgrade

Board footer