Upgrade from MX-21 to MX23

[wwd]

Hi,

I'm upgrading from MX-21 but run into troubles

$ sudo apt-get update
OK:1 http://deb.debian.org/debian bookworm-updates InRelease
Ign:2 http://security.debian.org/debian-security bookwormsecurity InRelease
OK:3 http://deb.debian.org/debian bookworm InRelease
OK:4 http://ftp.halifax.rwth-aachen.de/mxlin ... es/mx/repo bookworm InRelease
Ign:5 http://security.debian.org stable/updates InRelease
Fehl:6 http://security.debian.org/debian-security bookwormsecurity Release
404 Not Found [IP: 146.75.118.132 80]
Ign:7 http://deb.debian.org/debian-security bookworm/updates InRelease
Fehl:8 http://security.debian.org stable/updates Release
404 Not Found [IP: 146.75.118.132 80]
Holen:9 https://download.docker.com/linux/debian bookworm InRelease [43,3 kB]
Fehl:10 http://deb.debian.org/debian-security bookworm/updates Release
404 Not Found [IP: 146.75.118.132 80]
OK:11 https://packages.microsoft.com/repos/vscode stable InRelease
OK:12 http://de.mirrors.clouvider.net/debian stable InRelease
Paketlisten werden gelesen… Fertig

It seems that there is a problem with Debians Loadbalancer suppying wrong adresses.

Any help? Thanks.

[chrispop99]

Welcome to the forum.

Are you following the information in the MX Wiki to carry out this upgrade? If so, did you read and accept the first sentence?

It's just my personal experience, and that of others on our Facebook group, that this only goes smoothly about 50% of the time.

Chris

[Adrian]

bookwormsecurity should be bookworm-security

It works 0% of time for people who don't follow instructions...

[Redacted]

It works 0% of time for people who don't follow instructions...

This is the kind of answer that would keep my 70 year old wife - who has seen a marked deterioration in her ability to follow detailed instructions - from ever posting on a forum.
You don't have any idea what someone may be struggling through. Hope it never happens to you.

[j2mcgreg]

It works 0% of time for people who don't follow instructions...

This is the kind of answer that would keep my 70 year old wife - who has seen a marked deterioration in her ability to follow detailed instructions - from ever posting on a forum.
You don't have any idea what someone may be struggling through. Hope it never happens to you.

On the contrary, we do. It's why our recommended method to upgrade to a new version is to perform a fresh install and then restore your data from a backup. We know that an upgrade in place is a one shot deal and that only the most experienced users will correctly accomplish the task.

[wwd]

Welcome to the forum.

Are you following the information in the MX Wiki to carry out this upgrade? If so, did you read and accept the first sentence?

It's just my personal experience, and that of others on our Facebook group, that this only goes smoothly about 50% of the time.

Chris

The problem is that I followed the MX Wiki exactly. And the Wiki isn't correct.

[wwd]

bookwormsecurity should be bookworm-security

It works 0% of time for people who don't follow instructions...

Wow I haven't expected so dump comments. Great. This makes this forum a place never to ask anything in the future. Thanks for nothing.

[MXRobo]

I thought his remark was a rather jocular facetiousness attempt at humor, and if viewed as half-full, could be construed as a warning since it's risky to try anyway, e.g this is risky, and it definitely won't work if you don't follow the instructions and in no way intended as an insult, nor should one have to tiptoe when expressing themselves for fear that others view the comment as a lack of sympathy or empathy for those in need of such.

But don't listen to me because I'm a misogynistic bigot – "his".

And kudos j2mcgreg.

[CharlesV]

I have gone over and over the update instructions and I do not see any point where there is anything about -security in the instructions The change from 'bullseye' to 'bookworm' and then adding 'non-free-firmware' seem to be the only real places that there are mods to repo's .

This leads me to think that either the repo's should have already had this, or it should have been brought in automatically from the process. ( MX21 DOES have bullseye-security in the repo set )

If the OP manually edited the repos, then there was a mistake. If the OP ONLY ran the process as outlined in the update instructions wiki, then either there as an existing issue with the OP's repos, or something else went very wrong.

MX21 Repos

Code: Select all

$ sudo apt-get update
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease       
Hit:3 http://repo.mysql.com/apt/debian bullseye InRelease           
Hit:4 http://deb.debian.org/debian bullseye InRelease               
Hit:5 https://mxrepo.com/mx/repo bullseye InRelease
Reading package lists... Done

MX23 Repos

Code: Select all

Hit:1 http://la.mxrepo.com/mx/repo bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease                                     
Hit:3 http://deb.debian.org/debian bookworm InRelease                                              
Hit:4 http://security.debian.org/debian-security bookworm-security InRelease                       
Hit:5 https://brave-browser-apt-release.s3.brave.com stable InRelease                          
Reading package lists... Done

Slightly different machines, but you get the drift.

Is it possible that the repo lists were not fully updated?

[Adrian]

bookwormsecurity should be bookworm-security

It works 0% of time for people who don't follow instructions...

Wow I haven't expected so dump comments. Great. This makes this forum a place never to ask anything in the future. Thanks for nothing.

Wow, such thin skinned, what did I say? It was not even directed at you, it was at the funny (I thought) comment to that "it works 50% of the time"...