Upgrading Debian distribution

dedec0 · 09-04-2021, 04:23 PM

Hello.

I would like to confirm what i should do to upgrade my Debian from Debian 9 (Stretch) to Debian 11 (bullseye). The official guide does not mention, explaining with details, how to do a few things i want to do, like installing it from network.

Somewhere in the Debian pages, a forum is mentioned. I searched the upgrade instructions there, and found a promising result:

https://forums.debian.net/viewtopic....PGRADE#p741091

The first answer, by daftranti, starts by changing the apt sources.list file. It suggests these 4 lines:

Code:

deb http://deb.debian.org/debian bullseye main contrib non-free
deb http://deb.debian.org/debian-security/ bullseye-security main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free
deb http://deb.debian.org/debian bullseye-backports main contrib non-free

My sources.list is:

Code:

deb http://deb.debian.org/debian/ stretch multiverse main universe
deb-src http://deb.debian.org/debian/ stretch main

deb http://security.debian.org/ stretch/updates main
deb-src http://security.debian.org/ stretch/updates main

deb http://deb.debian.org/debian/ stretch-updates main
deb-src http://deb.debian.org/debian/ stretch-updates main

The last arguments are different on each line, and i have deb-src lines too. So, the general answer, for what i should do, is to replace all "stretch" by "bullseye" in the file? Keeping the rest unchanged?

Another question: doing an 'apt update' before 'apt upgrade' is allowed/possible?

One more: what is the difference of 'apt upgrade' and 'apt full-upgrade'? Can i do just the latter one?

The 'apt autoremove' seems clear.

Please, explain everything you answer. Thank you in advance.

Timothy Miller · 09-04-2021, 04:40 PM

So, you're REALLY going to want to move to Buster BEFORE you move to Bullseye, jumping 2 releases will probably result in MASSIVE breakage.

So I'd change all the Strech to Buster, then apt update apt upgrade apt full-upgrade. Then apt autoremove (I'd do with --purge) to get rid of all the orphan libraries and packages that are no longer needed.

Then fix whatever's broken.

Then change Buster to Bullseye (also making sure to adjust the security.debian.org line to the new style), and apt update, apt upgrade, apt full-upgrade again. And then finally of course, 1 more apt autoremove (again, I like with --purge).

Apt upgrade will bring in new versions of package, but if the new version requires a NEW install as a dependency, or requires another currently installed package to be removed, it WILL NOT upgrade it. It's more of a "safe" upgrade.

Apt full upgrade will upgrade everything it can. If necessary, installing new packages as dependencies or uninstalling conflicting packages where necessary.

dedec0 · 09-04-2021, 06:54 PM

Quote:

Originally Posted by Timothy Miller

[...]

Then change Buster to Bullseye (also making sure to adjust the security.debian.org line to the new style), and apt update, apt upgrade, apt full-upgrade again. And then finally of course, 1 more apt autoremove (again, I like with --purge).

[...]

It was a change from a stable version to another. I imagined that, for this reason, it would be safe. Thank you very much for the observation!

What is that "new line style"? Anyway, getting at that point, i will search it, if is not obvious.

The last 2 paragraphs are just to explain and compare 'apt upgrade' and 'apt full-upgrade', right?

Timothy Miller · 09-04-2021, 06:56 PM

old style debian security updates, which will fail if updated to Bullseye:

Code:

deb http://security.debian.org/ buster/updates main

new style debian security updates:

Code:

deb http://deb.debian.org/debian-security/ bullseye-security main

Quote:

Originally Posted by dedec0

The last 2 paragraphs are just to explain and compare 'apt upgrade' and 'apt full-upgrade', right?

Yes.

dedec0 · 09-04-2021, 07:00 PM

Quote:

Originally Posted by Timothy Miller

old style debian security updates, which will fail if updated to Bullseye:

Code:

deb http://security.debian.org/ buster/updates main

new style debian security updates:

Code:

deb http://deb.debian.org/debian-security/ bullseye-security main

Wow! Almost immediate! Thank you again. 😁👍🏾

dedec0 · 09-04-2021, 07:38 PM

I changed /etc/apt/sources.list to be:

Code:

deb http://deb.debian.org/debian/ buster multiverse main universe 
deb-src http://deb.debian.org/debian/ buster main 

deb http://security.debian.org/ buster/updates main 
deb-src http://security.debian.org/ buster/updates main 

# buster-updates, previously known as 'volatile'
deb http://deb.debian.org/debian/ buster-updates main 
deb-src http://deb.debian.org/debian/ buster-updates main

After that, the first 'apt update' failed. Look:

Code:

21:32:20 [  0] root@compo: /

# apt update # atualizando para debian 10

Hit:1 http://deb.debian.org/debian buster InRelease

Hit:2 https://linux.teamviewer.com/deb stable InRelease                        

Get:3 http://security.debian.org buster/updates InRelease [65.4
kB]            

Err:3 http://security.debian.org buster/updates InRelease                

  The following signatures couldn't be verified because the
  public key is not available: NO_PUBKEY 112695A0E562B32A
  NO_PUBKEY 54404762BBB6E853

Get:4 http://deb.debian.org/debian buster-updates InRelease
[51.9 kB]    

Get:5 https://repo.skype.com/deb stable InRelease [4,502 B]

Ign:6 http://repo.vivaldi.com/stable/deb stable InRelease                      

Err:4 http://deb.debian.org/debian buster-updates InRelease

  The following signatures couldn't be verified because the
  public key is not available: NO_PUBKEY 648ACFD622F3D138
  NO_PUBKEY 0E98404D386FA1D9

Err:5 https://repo.skype.com/deb stable InRelease  

  The following signatures were invalid: EXPKEYSIG
  1F3045A5DF7587C3 Skype Linux Client Repository
  <se-um@microsoft.com>

Hit:7 http://repo.vivaldi.com/stable/deb stable Release

Hit:9 https://packagecloud.io/AllToMP3/alltomp3/debian stretch
InRelease

Reading package lists... Done

W: GPG error: http://security.debian.org buster/updates
InRelease: The following signatures couldn't be verified because
the public key is not available: NO_PUBKEY 112695A0E562B32A
NO_PUBKEY 54404762BBB6E853

E: The repository 'http://security.debian.org buster/updates
InRelease' is not signed.

N: Updating from such a repository can't be done securely, and
is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user
configuration details.

W: GPG error: http://deb.debian.org/debian buster-updates
InRelease: The following signatures couldn't be verified because
the public key is not available: NO_PUBKEY 648ACFD622F3D138
NO_PUBKEY 0E98404D386FA1D9

E: The repository 'http://deb.debian.org/debian buster-updates
InRelease' is not signed.

N: Updating from such a repository can't be done securely, and
is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user
configuration details.

W: An error occurred during the signature verification. The
repository is not updated and the previous index files will be
used. GPG error: https://repo.skype.com/deb stable InRelease:
The following signatures were invalid: EXPKEYSIG
1F3045A5DF7587C3 Skype Linux Client Repository
<se-um@microsoft.com>

21:32:30 [  0] root@compo: /

#

I have configured extra repositories using synaptic: vivaldi, teamviewer, skype and https://packagecloud.io/AllToMP3/alltomp3/debian/. I am surprised that 'apt update' looked for them too. Anyway, the problem is in none of them.

What should i do, now?

frankbell · 09-04-2021, 07:42 PM

This article from Debian should be a good reference.

Note the command, apt-get dist-upgrade in section 9.1.2.

Timothy Miller · 09-04-2021, 07:46 PM

So, first thing is disable ANY 3rd party repos. They may be fine, but they may cause issues. You can re-enable after you're up to Bullseye.

As far as the pubkeys, after updating your sources.list what's it look like? I actually ran through these upgrades earlier and it should work without major issues.

dedec0 · 09-04-2021, 07:53 PM

Quote:

Originally Posted by Timothy Miller

So, first thing is disable ANY 3rd party repos. They may be fine, but they may cause issues. You can re-enable after you're up to Bullseye.

As far as the pubkeys, after updating your sources.list what's it look like? I actually ran through these upgrades earlier and it should work without major issues.

I will disable all third party in synaptic, then. Are they in a specific file, since it is not sources.list?

The lines i show in #1 are all the lines of my sources.list. The only lines i removed from the listing here are comments.

Timothy Miller · 09-04-2021, 07:55 PM

They should be configured in various files in /etc/apt/sources.list.d/

Also you may need to make more changes, as multiverse and universe no longer exist.

dedec0 · 09-04-2021, 08:06 PM

After commenting everything in the files inside 'sources.list.d', update still failed:

Code:

22:00:55 [  0] root@compo: /etc/apt/sources.list.d

# apt update # everything outside /etc/apt/sources.list file is
commented

Hit:1 http://deb.debian.org/debian buster InRelease

Get:2 http://security.debian.org buster/updates InRelease [65.4
kB]

Get:3 http://deb.debian.org/debian buster-updates InRelease
[51.9 kB]

Err:2 http://security.debian.org buster/updates InRelease      

  The following signatures couldn't be verified because the
  public key is not available: NO_PUBKEY 112695A0E562B32A
  NO_PUBKEY 54404762BBB6E853

Err:3 http://deb.debian.org/debian buster-updates InRelease

  The following signatures couldn't be verified because the
  public key is not available: NO_PUBKEY 648ACFD622F3D138
  NO_PUBKEY 0E98404D386FA1D9

Reading package lists... Done

W: GPG error: http://security.debian.org buster/updates
InRelease: The following signatures couldn't be verified because
the public key is not available: NO_PUBKEY 112695A0E562B32A
NO_PUBKEY 54404762BBB6E853

E: The repository 'http://security.debian.org buster/updates
InRelease' is not signed.

N: Updating from such a repository can't be done securely, and
is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user
configuration details.

W: GPG error: http://deb.debian.org/debian buster-updates
InRelease: The following signatures couldn't be verified because
the public key is not available: NO_PUBKEY 648ACFD622F3D138
NO_PUBKEY 0E98404D386FA1D9

E: The repository 'http://deb.debian.org/debian buster-updates
InRelease' is not signed.

N: Updating from such a repository can't be done securely, and
is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user
configuration details.

22:00:59 [  0] root@compo: /etc/apt/sources.list.d

#

/-:

dedec0 · 09-04-2021, 08:33 PM

Quote:

Originally Posted by frankbell

This article from Debian should be a good reference.

Note the command, apt-get dist-upgrade in section 9.1.2.

But before doing that 'dist-upgrade', 'apt-get update' also fails with signatures:

Code:

22:27:11 [  0] root@compo: /etc/apt/sources.list.d

# apt-get update 

Hit:1 http://deb.debian.org/debian buster InRelease

Get:2 http://security.debian.org buster/updates InRelease [65.4
kB]     

Get:3 http://deb.debian.org/debian buster-updates InRelease
[51.9 kB]          

Ign:2 http://security.debian.org buster/updates InRelease      

Get:4 http://security.debian.org buster/updates/main Sources
[199 kB]

Ign:3 http://deb.debian.org/debian buster-updates InRelease

Get:5 http://deb.debian.org/debian buster-updates/main Sources
[16.6 kB]

Get:6 http://security.debian.org buster/updates/main i386
Packages [302 kB]

Get:7 http://deb.debian.org/debian buster-updates/main i386
Packages [15.2 kB] 

Get:8 http://deb.debian.org/debian buster-updates/main amd64
Packages [15.2 kB]

Get:9 http://security.debian.org buster/updates/main amd64
Packages [302 kB]   

Get:10 http://deb.debian.org/debian buster-updates/main
Translation-en [13.9 kB]

Get:11 http://deb.debian.org/debian buster-updates/main i386
Contents (deb) [487 kB]

Get:12 http://security.debian.org buster/updates/main
Translation-en [159 kB]  

Get:13 http://deb.debian.org/debian buster-updates/main amd64
Contents (deb) [422 kB]

Fetched 1,932 kB in 0s (2,446 kB/s)                                   

Reading package lists... Done

W: GPG error: http://security.debian.org buster/updates
InRelease: The following signatures couldn't be verified because
the public key is not available: NO_PUBKEY 112695A0E562B32A
NO_PUBKEY 54404762BBB6E853

W: The repository 'http://security.debian.org buster/updates
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: http://deb.debian.org/debian buster-updates
InRelease: The following signatures couldn't be verified because
the public key is not available: NO_PUBKEY 648ACFD622F3D138
NO_PUBKEY 0E98404D386FA1D9

W: The repository 'http://deb.debian.org/debian buster-updates
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.

22:27:32 [  0] root@compo: /etc/apt/sources.list.d

#

/-:

ondoho · 09-04-2021, 11:54 PM

Again?

As I wrote elsewhere:

Quote:

Originally Posted by ondoho

The first stop to obtain this information should always be the distro's website, i.e. debian.org.

I found this (and I remember using something very similar last time I upgraded):
https://www.debian.org/releases/bull...rading.en.html
Strangely, it is architecture-specific, you might need to replace "amd64" in the link with sth else.
Also see this page: https://www.debian.org/releases/bullseye/

And yes, you should dist-upgrade from one release to the next, not skipping any.

So, in your case, you'd be needing this document first:
https://www.debian.org/releases/bust...rading.en.html

Also, this topic (upgrading across major releases) has been covered multiple times both here and on forums.debian.net.
You do search before you start a new thread, don't you?

dedec0 · 09-05-2021, 12:06 AM

Quote:

Originally Posted by ondoho

Again?

As I wrote elsewhere:

And yes, you should dist-upgrade from one release to the next, not skipping any.

So, in your case, you'd be needing this document first:
https://www.debian.org/releases/bust...rading.en.html

Also, this topic (upgrading across major releases) has been covered multiple times both here and on forums.debian.net.
You do search before you start a new thread, don't you?

ondoho, i have searched the documentation on debian.org before i started the first thread. i spent more than 2 hours just trying to find the "obvious" steps to install/upgrade the newer stable release, in the way i wanted it to be. And the forum with the solution i found, and showed here, is recommended by debian.org itself. I found that solution, it seemed right. Why would i search other? But i had a few doubts, and then, as i said in #1, i decided to open a thread here.

If i am not as efficient as you to finding answers, that is another kind of issue, hard, although subtle.

ondoho · 09-05-2021, 12:40 AM

Quote:

Originally Posted by dedec0

ondoho, i have searched the documentation on debian.org before i started the first thread. i spent more than 2 hours just trying to find the "obvious" steps to install/upgrade the newer stable release, in the way i wanted it to be. And the forum with the solution i found, and showed here, is recommended by debian.org itself. I found that solution, it seemed right. Why would i search other? But i had a few doubts, and then, as i said in #1, i decided to open a thread here.

If i am not as efficient as you to finding answers, that is another kind of issue, hard, although subtle.

I'm seriously curious how exactly you search the web and LQ forums?