Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

MX16 update problem SOLVED

User avatar
bazzaman
Forum Novice
Forum  Novice
Posts: 12
Joined: Tue May 19, 2009 9:34 pm

MX16 update problem SOLVED

#1

Post by bazzaman » Sun Mar 17, 2019 9:26 pm

I can't upgrade even though updates are available. Is it possible to fix this by changing repositories? This Taiwan one was selected when I installed a few years ago, and seems quirky.
Would appreciate being directed to instructions (like for a 5 yr old) on how to select the best basic repos... not necessarily the fastest.
Here's what I get when reloading synaptic:

W: GPG error: http://www.deb-multimedia.org jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5C808C2B65558117
W: GPG error: http://ftp.yzu.edu.tw jessie InRelease: The following signatures were invalid: KEYEXPIRED 1552432420 KEYEXPIRED 1552432420 KEYEXPIRED 1552432420 KEYEXPIRED 1552432420 KEYEXPIRED 1552432420 KEYEXPIRED 1552432420 KEYEXPIRED 1552432420
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ftp.yzu.edu.tw mx15 InRelease: The following signatures were invalid: KEYEXPIRED 1548008281 KEYEXPIRED 1548008281 KEYEXPIRED 1548008281

W: GPG error: http://ftp.yzu.edu.tw mx16 InRelease: The following signatures were invalid: KEYEXPIRED 1548008281 KEYEXPIRED 1548008281 KEYEXPIRED 1548008281
W: GPG error: https://riot.im artful InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E019645248E8F4A1
W: Failed to fetch http://debian.ipserverone.com/debian/di ... /InRelease

W: Failed to fetch http://ftp.yzu.edu.tw/Linux/mx-workspac ... /InRelease

W: Failed to fetch http://debian.ipserverone.com/debian/di ... elease.gpg Unable to connect to debian.ipserverone.com:http:

W: Some index files failed to download. They have been ignored, or old ones used instead.
Last edited by bazzaman on Mon Mar 18, 2019 9:54 pm, edited 1 time in total.

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 5058
Joined: Wed Jul 12, 2006 4:05 pm

Re: MX16 update problem

#2

Post by timkb4cq » Sun Mar 17, 2019 11:01 pm

Use the Repo Manager in MX-Tools to select a repo close to you (or since you previously mentioned using a VPN, close to the other end of your VPN)
On the debian repo tab is a button that will check which debian mirror has the fastest connection to you machine - but you can always look at the extensive debian mirror list and choose another one close to your connection and enter it manually in Synaptic.

There have been two expired key issues on MX-16 lately, one for the MX repos and one for the antiX repos. You'll keep getting errors on any MX repo you choose until you fix those. Instructions here:
viewtopic.php?p=491429#p491429
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
bazzaman
Forum Novice
Forum  Novice
Posts: 12
Joined: Tue May 19, 2009 9:34 pm

Re: MX16 update problem

#3

Post by bazzaman » Sun Mar 17, 2019 11:46 pm

thanks, I've been lazy and negligent. One question regarding downloading the updated key: instructions say to "open a terminal in the directory you downloaded it into and run:
Code: Select all
sudo apt-key add mx15repo.txt"
How do I know which directory I downloaded it into?

User avatar
bazzaman
Forum Novice
Forum  Novice
Posts: 12
Joined: Tue May 19, 2009 9:34 pm

Re: MX16 update problem

#4

Post by bazzaman » Mon Mar 18, 2019 3:46 am

Apologies for the last dumb question... I thought the instructions were saying to open a terminal in the directory in which the old expired key was download. I plead senility.
Anyway, I downloaded the new key, upgraded the antix-archive-keyring to 200019.3.13, reloaded synaptic, marked and applied all upgrades. But after a long time loading ended up with these errors:


W: GPG error: http://www.deb-multimedia.org jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5C808C2B65558117
W: GPG error: https://riot.im artful InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E019645248E8F4A1
W: Failed to fetch http://debian.ipserverone.com/debian/di ... /InRelease
W: Failed to fetch http://debian.ipserverone.com/debian/di ... elease.gpg Unable to connect to debian.ipserverone.com:http:
W: Some index files failed to download. They have been ignored, or old ones used instead.


E: Unable to correct problems, you have held broken packages.
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies


I tried to fix the broken packages (Edit>fix broken packages) but got this notification:
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies


When I attempt to Mark All Upgrades or Apply all marked changes I get: "Could not apply changes. Fix broken packages first".
It looks like I probably didn't succeed in downloading the required keys.
Any suggestions as to how to fix this?

User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 4791
Joined: Sun May 27, 2007 5:37 am

Re: MX16 update problem

#5

Post by asqwerth » Mon Mar 18, 2019 3:55 am

deb-multimedia and riot.im are 3rd party repos. You will have to check with them.

riot also appears to be Ubuntu-based ("artful"). Is it compatible with Debian Stretch Jessie when:

1. the packages are not pure Debian
2. Artful Aardvark is so much newer than Debian Jessie?

I don't know what ipserverone is.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
bazzaman
Forum Novice
Forum  Novice
Posts: 12
Joined: Tue May 19, 2009 9:34 pm

Re: MX16 update problem

#6

Post by bazzaman » Mon Mar 18, 2019 4:03 am

A follow up to the last post. There were unapplied changes left in synaptic package manager but I closed it anyway. I then clicked on the upgrade notification icon in the panel, clicked on 'upgrade' and the icon switched off. I then went back to synaptic, and found '0 broken, 0 to install/upgrade, 0 to remove.
But doing a reload results in this notice:
W: GPG error: https://riot.im artful InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E019645248E8F4A1
W: GPG error: http://www.deb-multimedia.org jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 5C808C2B65558117
W: Failed to fetch http://debian.ipserverone.com/debian/di ... /InRelease

W: Failed to fetch http://debian.ipserverone.com/debian/di ... elease.gpg Unable to connect to debian.ipserverone.com:http:

W: Some index files failed to download. They have been ignored, or old ones used instead.

Any suggestions on how to fix this?

User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 4791
Joined: Sun May 27, 2007 5:37 am

Re: MX16 update problem

#7

Post by asqwerth » Mon Mar 18, 2019 4:07 am

I can't help you beyond asking if you have tried running the MX tool "checkaptgpg"?

If yes and it doesn't work, then you'll have to wait for the experts to wake up in their timezone.

Caveat: as I don't know anything about riot and ipserverone, I don't know if those will bork your system.

deb-multimedia - there have been many warnings that it's not 100% compatible with MX systems.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 5058
Joined: Wed Jul 12, 2006 4:05 pm

Re: MX16 update problem

#8

Post by timkb4cq » Mon Mar 18, 2019 9:02 am

debian.ipserverone/debian used to be a debian mirror in Malaysia. There don't seem to be any debian mirrors in Malaysia anymore, but there several on the debian list in nearby Thailand.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
asqwerth
Forum Veteran
Forum Veteran
Posts: 4791
Joined: Sun May 27, 2007 5:37 am

Re: MX16 update problem

#9

Post by asqwerth » Mon Mar 18, 2019 9:23 am

timkb4cq wrote:
Mon Mar 18, 2019 9:02 am
debian.ipserverone/debian used to be a debian mirror in Malaysia. There don't seem to be any debian mirrors in Malaysia anymore, but there several on the debian list in nearby Thailand.
No, we blacklisted the Thai Debian mirror from around MX16, because it never worked. Initially in MX14 and 15, Debian would default to Thai mirrors for that general region, but it would never connect for updates and the first step for me after installing MX used to be to change the Debian mirror. For the region, Hong Kong Debian mirror works well, but I also used Germany at times.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 5058
Joined: Wed Jul 12, 2006 4:05 pm

Re: MX16 update problem

#10

Post by timkb4cq » Mon Mar 18, 2019 9:36 am

IIRC, that was ftp.th.debian.org that we blacklisted.
Debian no longer lists that one but there are three others in Thailand.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

Post Reply

Return to “Older Versions”