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

upgrade can not be authenticated [SOLVED]

Post Reply
User avatar
Sparky
Forum Regular
Forum Regular
Posts: 444
Joined: Sun Dec 23, 2018 7:07 pm

upgrade can not be authenticated [SOLVED]

#1

Post by Sparky » Mon May 27, 2019 3:35 pm

Even switched repos but still the same message. Anyone else getting it?

Code: Select all

WARNING: The following packages cannot be authenticated!
   antix-archive-keyring
   antix-libs
   cli-aptix
   cli-installer-antix
   cli-shell-utils
   fbxkb
   fskbsetting
   libgksu2-0
   gksu
   live-kernel-updater
   live-usb-maker
   partition-info
   smxi-inxi-antix
Install these packages without verification? [y/N] 
Last edited by Sparky on Mon May 27, 2019 3:48 pm, edited 1 time in total.
MX Linux Asus F552, 12GB RAM, 1TB HDD

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

Re: upgrade can not be authenticated

#2

Post by asqwerth » Mon May 27, 2019 3:39 pm

This must be an install you haven't upgraded for a long time. The antix repo keyring expired quite some time ago and had to be renewed.


Just install the antix-archive-keyring package first.

Then:

sudo apt update

and sudo apt full-upgrade
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
Sparky
Forum Regular
Forum Regular
Posts: 444
Joined: Sun Dec 23, 2018 7:07 pm

Re: upgrade can not be authenticated

#3

Post by Sparky » Mon May 27, 2019 3:41 pm

ok thanks! I just installed this one today, maybe an older download.
MX Linux Asus F552, 12GB RAM, 1TB HDD

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

Re: upgrade can not be authenticated

#4

Post by asqwerth » Mon May 27, 2019 3:44 pm

Sparky wrote:
Mon May 27, 2019 3:41 pm
ok thanks! I just installed this one today, maybe an older download.
Yes, if you were using a MX18 or 18.1 iso.

I think 18.2 iso was issued in order to incorporate the new updated keyring.

the latest 18.3 iso will of course be fine.

Please mark topic as SOLVED.
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
Sparky
Forum Regular
Forum Regular
Posts: 444
Joined: Sun Dec 23, 2018 7:07 pm

Re: upgrade can not be authenticated

#5

Post by Sparky » Mon May 27, 2019 3:49 pm

asqwerth wrote:
Mon May 27, 2019 3:44 pm
Sparky wrote:
Mon May 27, 2019 3:41 pm
ok thanks! I just installed this one today, maybe an older download.
Yes, if you were using a MX18 or 18.1 iso.

I think 18.2 iso was issued in order to incorporate the new updated keyring.

the latest 18.3 iso will of course be fine.

Please mark topic as SOLVED.
Thank you, I'll re download the latest MX.
MX Linux Asus F552, 12GB RAM, 1TB HDD

User avatar
figueroa
Forum Regular
Forum Regular
Posts: 396
Joined: Fri Dec 21, 2018 12:20 am

Re: upgrade can not be authenticated [SOLVED]

#6

Post by figueroa » Mon May 27, 2019 11:26 pm

After several months, of non-use, I updated MX on my Gateway ec1803, an Acer Aspire 1410 clone, http://www.silentpcreview.com/Gateway_EC1803h_notebook. (I've upgraded RAM to 4G.) The MX install is pretty vanilla. I have only added the sshd server, x2go client, and VirtualBox, and someday intend to also upgrade vim to the full package. Also, everything on this little PC worked perfectly out-of-the-box with MX. This has been my go-to travel PC for the last 10 years.

I ran into the unauthenticaated packages, about 256 total updates, and decided to just pull the trigger. It took about 25 minutes (I forgot to actually time it), and finished without any errors. and /etc/mx-version was updated to read 18.3, leaving the original install date in place.

Why did I just pull the trigger? Because I trust the apt sources, and was feeling a little lazy.
Andy Figueroa
Using Unix from 1984; GNU/Linux from 1993

Post Reply

Return to “General”