Errors trying to upgrade 17.x to 18.x [SOLVED]

[ardee]

Hi. Awhile back I tried several flavors of Linux as VMs under Windows and liked MX best. I installed it and customized it -- but didn't come back for several months. Now I want to update/upgrade from 17.x to 18.x but am getting errors. Perhaps you can help?

Wnen I try to use MX Package Installer, I get "Internet is not available, won't be able to download the list of packages". But the Internet is available as I am able to use Chrome to go anywhere.
When I try to use Synaptic Package Manager, I don't know how to proceed.
When I try to use Terminal, I get errors like "Could not resolve <sitename>" for every site.

I am so confused so I guess I need your help. Thanks!!

[Jerry3904]

General directions on the website are a good place to start: https://mxlinux.org/migration/

[ardee]

Thanks Jerry. I had indeed read that and followed the directions, but still get these errors.

Is there a way to upgrade via Virtual Box (under Windows) but retain or re-obtain all the Linux applications and settings?

Thanks again.

[asqwerth]

Didn't mx17/18 also (that is, it wasn't just mx15/16 that had this issue) have a gpg key issue a few months' ago? That might be the problem since you hadn't used this installation for that same period of time.

If so, use synaptic, reload, search for "keyring". There should be an updatable package. Update just that , then reload package lists again and so full upgrade.

[Jerry3904]

That must be the antix-archive-keyring, forgot about that--thanks. Probably should add that to the migration page now.

[Jerry3904]

That must be the antix-archive-keyring, forgot about that--thanks. Probably should add that to the migration page now.

[Stevo]

Yes, but that didn't generate the errors that the user reports getting. Maybe Vbox in Windows is filtering out something like the repo addresses?

ardee, what do you get with

Code: Select all

sudo apt update

?

That'll show what kind of problems the updates are having.

[ardee]

Hi. When I run

Code: Select all

sudo apt update

I get this result:

Code: Select all

Err:1 http://ftp.us.debian.org/debian stretch-updates InRelease
  Could not resolve 'ftp.us.debian.org'
Err:2 http://ftp.us.debian.org/debian stretch InRelease
  Could not resolve 'ftp.us.debian.org'
Err:3 http://security.debian.org stretch/updates InRelease
  Could not resolve 'security.debian.org'
Err:4 http://dl.google.com/linux/chrome/deb stable InRelease
  Could not resolve 'dl.google.com'
Get:5 file:/var/lib/local-apt-repository ./ InRelease
Ign:5 file:/var/lib/local-apt-repository ./ InRelease
Err:6 http://la.mxrepo.com/mx/repo stretch InRelease
  Could not resolve 'la.mxrepo.com'
Err:7 http://repo.vivaldi.com/stable/deb stable InRelease
  Could not resolve 'repo.vivaldi.com'
Err:8 http://packages.microsoft.com/repos/vscode stable InRelease
  Could not resolve 'packages.microsoft.com'
Err:9 http://repo.antixlinux.com/stretch stretch InRelease                   
  Could not resolve 'repo.antixlinux.com'
Err:10 http://www.deb-multimedia.org stretch InRelease                       
  Could not resolve 'www.deb-multimedia.org'
Get:11 file:/var/lib/local-apt-repository ./ Release [1,279 B]               
Err:12 http://iso.mxrepo.com/antix/stretch stretch InRelease
  Could not resolve 'iso.mxrepo.com'
Err:13 https://deb.opera.com/opera-stable stable InRelease
  Could not resolve host: deb.opera.com
Get:11 file:/var/lib/local-apt-repository ./ Release [1,279 B]
Get:14 file:/var/lib/local-apt-repository ./ Release.gpg
Ign:14 file:/var/lib/local-apt-repository ./ Release.gpg
Reading package lists... Done
Building dependency tree       
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://iso.mxrepo.com/antix/stretch/dists/stretch/InRelease  Could not resolve 'iso.mxrepo.com'
W: Failed to fetch http://repo.antixlinux.com/stretch/dists/stretch/InRelease  Could not resolve 'repo.antixlinux.com'
W: Failed to fetch http://ftp.us.debian.org/debian/dists/stretch-updates/InRelease  Could not resolve 'ftp.us.debian.org'
W: Failed to fetch http://ftp.us.debian.org/debian/dists/stretch/InRelease  Could not resolve 'ftp.us.debian.org'
W: Failed to fetch http://security.debian.org/dists/stretch/updates/InRelease  Could not resolve 'security.debian.org'
W: Failed to fetch http://www.deb-multimedia.org/dists/stretch/InRelease  Could not resolve 'www.deb-multimedia.org'
W: Failed to fetch http://dl.google.com/linux/chrome/deb/dists/stable/InRelease  Could not resolve 'dl.google.com'
W: Failed to fetch http://la.mxrepo.com/mx/repo/dists/stretch/InRelease  Could not resolve 'la.mxrepo.com'
W: Failed to fetch https://deb.opera.com/opera-stable/dists/stable/InRelease  Could not resolve host: deb.opera.com
W: Failed to fetch http://repo.vivaldi.com/stable/deb/dists/stable/InRelease  Could not resolve 'repo.vivaldi.com'
W: Failed to fetch http://packages.microsoft.com/repos/vscode/dists/stable/InRelease  Could not resolve 'packages.microsoft.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.

Seems like there's something going on with Internet access. I can use the web via a browser, but none of these tools seem to see that they're connected.

Advice?

(Thank you!)

[ardee]

Do you know what might cause those "not connected"-type errors?

[Stevo]

In the browser in MX, you should normally be able to surf into the repos, such as this one

http://ftp.us.debian.org/debian

If you can't, something is blocking those kind of connections. If you can surf into the repo in Windows, that points to something in Virtual Box.

BTW, deb-multimedia can break GIMP and other packages if you're not careful... We don't recommend leaving it enabled at all.