I then, late alas, to do step 2) afterwards, but then the package mx23-archive-keyring was no longer available.
Maybe it belonged to the ORIGINAL MX21 Repo, that had been overwritten
by hand.
Is it still a way (I tried using WGET, failing, as unable to locate the correct package name, which apparently is neither mx23-archive-keyring
nor mx23-archive-key or suilar, and moreover the URL could be wrong too
or both), but well, as I was saying : Is it still a way to install a
single package from a given repo (the original WILDFLOWER 21 Repo) in
the new system, and then repeat the upgrade procedure ?
Sillily (LOL) I tried a Dist Upgrade (Linux MX dist upgrade fromreinstalling/
Wildflower to Libretto) without following exactly the procedure in the
MX 23 Forum
here :
https://mxlinux.org/wiki/system/upgrading-from-mx-21-to-mx-23-without-
I resume the steps below
Upgrade Steps:
1) Upgrade your system to the latest packages with:
sudo apt update; sudo apt full-upgrade
2) Install mx23-archive-keyring:
sudo apt install mx23-archive-keyring
3) Change sources to point to bookworm release (search all .list
files and replace “bullseye” with “bookworm”):
find /etc/apt -name "*.list" -exec sudo sed -i 's/bullseye/bookworm/g'
{} +
4) Add non-free-firmware to debian sources (or by hand:
edit the debian.list and add “non-free-firmware” to each deb line):
grep -qF 'non-free-firmware'
/etc/apt/sources.list.d/debian.list || sudo sed -i 's/non-free/non-free non-free-firmware/g'
/etc/apt/sources.list.d/debian.list
5) Upgrade packages (make sure nothing important is removed at this
step: examine the prompt before you press “y”):
sudo apt update; sudo apt full-upgrade
Now, acting sillily basing on what I recalled, I performed all stages FORGETTING 2) Install mx23-archive-keyring:
The upgrade resulted in PARTIAL success (and failure overall). I dunno exactly what was upgraded and what not.
I then, late alas, to do step 2) afterwards, but then the package mx23-archive-keyring was no longer available.
Maybe it belonged to the ORIGINAL MX21 Repo, that had been overwritten
by hand.
Am I right ?
Is it still a way (I tried using WGET, failing, as unable to locate the correct package name, which apparently is neither mx23-archive-keyring
nor mx23-archive-key or suilar, and moreover the URL could be wrong too
or both), but well, as I was saying : Is it still a way to install a
single package from a given repo (the original WILDFLOWER 21 Repo) in
the new system, and then repeat the upgrade procedure ?
Some core package, resulting NOT SIGNED, refuse to be upgraded, so such
keys are necessary.
I hope I was able to explain sufficiently sth I don't understand myself.
Tnx for any advice for this mess (the system runs, and reports itself as
the OLD one, even if it upgraded many hundreds of packages)
Sillily (LOL) I tried a Dist Upgrade (Linux MX dist upgrade
from Wildflower to Libretto) without following exactly the
procedure in the MX 23 Forum
here : https://mxlinux.org/wiki/system/upgrading-from-mx-21-to-mx-23-without-reinstalling/
I resume the steps below
Upgrade Steps:
1) Upgrade your system to the latest packages with:
sudo apt update; sudo apt full-upgrade
2) Install mx23-archive-keyring:
sudo apt install mx23-archive-keyring
3) Change sources to point to bookworm release (search
all .list files and replace “bullseye” with “bookworm”):
find /etc/apt -name "*.list" -exec sudo sed -i
's/bullseye/bookworm/g' {} +
4) Add non-free-firmware to debian sources (or by hand:
edit the debian.list and add “non-free-firmware” to each deb
line):
grep -qF 'non-free-firmware'
/etc/apt/sources.list.d/debian.list || sudo sed -i
's/non-free/non-free non-free-firmware/g'
/etc/apt/sources.list.d/debian.list
5) Upgrade packages (make sure nothing important is
removed at this step: examine the prompt before you press “y”):
sudo apt update; sudo apt full-upgrade
Now, acting sillily basing on what I recalled, I performed
all stages FORGETTING 2) Install mx23-archive-keyring:
The upgrade resulted in PARTIAL success (and failure
overall). I dunno exactly what was upgraded and what not.
I then, late alas, to do step 2) afterwards, but then the
package mx23-archive-keyring was no longer available.
Maybe it belonged to the ORIGINAL MX21 Repo, that had been
overwritten by hand.
Am I right ?
Is it still a way (I tried using WGET, failing, as unable to
locate the correct package name, which apparently is neither mx23-archive-keyring nor mx23-archive-key or suilar, and
moreover the URL could be wrong too or both), but well, as I
was saying : Is it still a way to install a single package
from a given repo (the original WILDFLOWER 21 Repo) in the
new system, and then repeat the upgrade procedure ?
Some core package, resulting NOT SIGNED, refuse to be
upgraded, so such keys are necessary.
I hope I was able to explain sufficiently sth I don't
understand myself.
Tnx for any advice for this mess (the system runs, and
reports itself as the OLD one, even if it upgraded many
hundreds of packages)
On Sun, 10 Mar 2024 07:58:57 -0400, MarioCCCP <NoliMihiFrangereMentulam@libero.it> wrote:
Sillily (LOL) I tried a Dist Upgrade (Linux MX dist upgrade
from Wildflower to Libretto) without following exactly the
procedure in the MX 23 Forum
here :
https://mxlinux.org/wiki/system/upgrading-from-mx-21-to-mx-23-without-reinstalling/
I resume the steps below
Upgrade Steps:
1) Upgrade your system to the latest packages with:
sudo apt update; sudo apt full-upgrade
2) Install mx23-archive-keyring:
sudo apt install mx23-archive-keyring
3) Change sources to point to bookworm release (search
all .list files and replace “bullseye” with “bookworm”):
find /etc/apt -name "*.list" -exec sudo sed -i
's/bullseye/bookworm/g' {} +
4) Add non-free-firmware to debian sources (or by hand:
edit the debian.list and add “non-free-firmware” to each deb
line):
grep -qF 'non-free-firmware'
/etc/apt/sources.list.d/debian.list || sudo sed -i
's/non-free/non-free non-free-firmware/g'
/etc/apt/sources.list.d/debian.list
5) Upgrade packages (make sure nothing important is
removed at this step: examine the prompt before you press
“y”):
sudo apt update; sudo apt full-upgrade
Now, acting sillily basing on what I recalled, I performed
all stages FORGETTING 2) Install mx23-archive-keyring:
The upgrade resulted in PARTIAL success (and failure
overall). I dunno exactly what was upgraded and what not.
I then, late alas, to do step 2) afterwards, but then the
package mx23-archive-keyring was no longer available.
Maybe it belonged to the ORIGINAL MX21 Repo, that had been
overwritten by hand.
Am I right ?
Is it still a way (I tried using WGET, failing, as unable to
locate the correct package name, which apparently is neither
mx23-archive-keyring nor mx23-archive-key or suilar, and
moreover the URL could be wrong too or both), but well, as I
was saying : Is it still a way to install a single package
from a given repo (the original WILDFLOWER 21 Repo) in the
new system, and then repeat the upgrade procedure ?
Some core package, resulting NOT SIGNED, refuse to be
upgraded, so such keys are necessary.
I hope I was able to explain sufficiently sth I don't
understand myself.
Tnx for any advice for this mess (the system runs, and
reports itself as the OLD one, even if it upgraded many
hundreds of packages)
https://mxrepo.com/mx/repo/pool/main/m/mx23-archive-keyring/
I've never used ubuntu, so don't know how to actually--
install the package.
Regards, Dave Hodgins
On 10/03/2024 12.58, MarioCCCP wrote:
I then, late alas, to do step 2) afterwards, but then the
package mx23-archive-keyring was no longer available.
Maybe it belonged to the ORIGINAL MX21 Repo, that had been
overwritten by hand.
Think step 1 already did some changes, but step 3 will take
care of all 3rd party repositories.
Is it still a way (I tried using WGET, failing, as unable
to locate the correct package name, which apparently is
neither mx23-archive-keyring nor mx23-archive-key or
suilar, and moreover the URL could be wrong too or both),
but well, as I was saying : Is it still a way to install a
single package from a given repo (the original WILDFLOWER
21 Repo) in the new system, and then repeat the upgrade
procedure ?
wget https://mxrepo.com/mx/repo/pool/main/m/mx23-archive-keyring/mx23-archive-keyring_2023.6.6_all.deb
sudo apt install -f ./mx23-archive-keyring_2023.6.6_all.deb
and then continue from step 5 if you are sure you have done
the changes needed for the repo files, cross your fingers
and hope it will work.
On Sun, 10 Mar 2024 12:58:57 +0100, MarioCCCP wrote:
Sillily (LOL) I tried a Dist Upgrade (Linux MX dist upgrade fromreinstalling/
Wildflower to Libretto) without following exactly the procedure in the
MX 23 Forum
here :
https://mxlinux.org/wiki/system/upgrading-from-mx-21-to-mx-23-without-
I resume the steps below
Upgrade Steps:
1) Upgrade your system to the latest packages with:
sudo apt update; sudo apt full-upgrade
2) Install mx23-archive-keyring:
sudo apt install mx23-archive-keyring
3) Change sources to point to bookworm release (search all .list
files and replace “bullseye” with “bookworm”):
find /etc/apt -name "*.list" -exec sudo sed -i 's/bullseye/bookworm/g'
{} +
4) Add non-free-firmware to debian sources (or by hand:
edit the debian.list and add “non-free-firmware” to each deb line):
grep -qF 'non-free-firmware'
/etc/apt/sources.list.d/debian.list || sudo sed -i 's/non-free/non-free
non-free-firmware/g'
/etc/apt/sources.list.d/debian.list
5) Upgrade packages (make sure nothing important is removed at this
step: examine the prompt before you press “y”):
sudo apt update; sudo apt full-upgrade
Now, acting sillily basing on what I recalled, I performed all stages
FORGETTING 2) Install mx23-archive-keyring:
The upgrade resulted in PARTIAL success (and failure overall). I dunno
exactly what was upgraded and what not.
I then, late alas, to do step 2) afterwards, but then the package
mx23-archive-keyring was no longer available.
Maybe it belonged to the ORIGINAL MX21 Repo, that had been overwritten
by hand.
Am I right ?
Is it still a way (I tried using WGET, failing, as unable to locate the
correct package name, which apparently is neither mx23-archive-keyring
nor mx23-archive-key or suilar, and moreover the URL could be wrong too
or both), but well, as I was saying : Is it still a way to install a
single package from a given repo (the original WILDFLOWER 21 Repo) in
the new system, and then repeat the upgrade procedure ?
Some core package, resulting NOT SIGNED, refuse to be upgraded, so such
keys are necessary.
I hope I was able to explain sufficiently sth I don't understand myself.
Tnx for any advice for this mess (the system runs, and reports itself as
the OLD one, even if it upgraded many hundreds of packages)
Mario,
Sorry to hear of your troubles. Hopefully you made a complete backup
BEFORE your tried the upgrade. In your present situation you should do a
full restore.
On 10/03/24 14:20, J.O. Aho wrote:
wget
https://mxrepo.com/mx/repo/pool/main/m/mx23-archive-keyring/mx23-archive-keyring_2023.6.6_all.deb
where exactly WGET puts the downloaded file ? Is it there some standard default location ? Or it saves it in the current directory ? If so,
should I position the terminal on root folder or, ig, some APT related folder ?
sudo apt install -f ./mx23-archive-keyring_2023.6.6_all.deb
I assume I should be positioned in the folder above, or am I wrong ?
On 11/03/2024 00.18, MarioCCCP wrote:
On 10/03/24 14:20, J.O. Aho wrote:
wget
https://mxrepo.com/mx/repo/pool/main/m/mx23-archive-keyring/mx23-archive-keyring_2023.6.6_all.deb
where exactly WGET puts the downloaded file ? Is it there
some standard default location ? Or it saves it in the
current directory ? If so, should I position the terminal
on root folder or, ig, some APT related folder ?
If you don't specify any output location, then it will do
that in the directory where you are at the moment, the same
way as touch will create a file in the directory if you just
provide a filename (please don't just add a path after the
current wget example, as you need to use the -O option, more
information: man wget ).
sudo apt install -f ./mx23-archive-keyring_2023.6.6_all.deb
I assume I should be positioned in the folder above, or am
I wrong ?
No, in current folder, see the difference
./ = current folder
../ = folder one step closer to root (not root user home
directory, but the root directory which is /).
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 915 |
Nodes: | 10 (1 / 9) |
Uptime: | 30:06:09 |
Calls: | 12,169 |
Calls today: | 1 |
Files: | 186,521 |
Messages: | 2,234,226 |