[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gNewSense-users] E: Some packages could not be authenticated
From: |
Lars Nooden |
Subject: |
[gNewSense-users] E: Some packages could not be authenticated |
Date: |
Mon, 14 Mar 2011 17:55:20 +0200 (EET) |
User-agent: |
Alpine 1.10 (DEB 962 2008-03-14) |
For about a week, apt-get complains that any new packages cannot be
authenticated. Is this something that will blow over after work is done
on the repositories, or must I update some keys manually first?
# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
libavahi-client3 libavahi-common-data libavahi-common3
libavahi-glib1 libavahi-qt3-1 libcups2 libcupsimage2
libsmbclient libwbclient0
9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1616kB of archives.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]?
WARNING: The following packages cannot be authenticated!
libavahi-common-data libavahi-common3 libavahi-client3
libavahi-glib1 libavahi-qt3-1 libcups2 libcupsimage2
libwbclient0 libsmbclient
Install these packages without verification [y/N]? n
E: Some packages could not be authenticated
Regards,
/Lars
- [gNewSense-users] E: Some packages could not be authenticated,
Lars Nooden <=