Author Topic: WARNING: The following packages cannot be authenticated!  (Read 1558 times)

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
WARNING: The following packages cannot be authenticated!
« on: January 13, 2007, 08:39:07 pm »
Hi,

I have problems on upgrade to 0.43.

I did

DonwloadUpdates.sh

and apt cache was filled with files, but then I get this error on actual update, cause it seems something is wrong with signing of packages....

I get this warrning on ApplyUpdates.sh or apt-get update :

Quote
WARNING: The following packages cannot be authenticated!


and nothing gets installed (I don't want to hack apt to install untrusted packages)...

I have Debian's key :

Quote
apt-key list
/etc/apt/trusted.gpg
--------------------
pub   1024R/1DB114E0 2004-01-15 [expired: 2005-01-27)]
uid                  Debian Archive Automatic Signing Key (2004) < newbielink:mailto:ftpmaster@debian.org [nonactive]>

pub   1024D/4F368D5D 2005-01-31 [expired: 2006-01-31)]
uid                  Debian Archive Automatic Signing Key (2005) < newbielink:mailto:ftpmaster@debian.org [nonactive]>

pub   1024D/B5F5BBED 2005-04-24
uid                  Debian AMD64 Archive Key < newbielink:mailto:debian-amd64@lists.debian.org [nonactive]>
sub   2048g/34FC6FE5 2005-04-24

pub   1024D/2D230C5F 2006-01-03 [expires: 2007-02-07]
uid                  Debian Archive Automatic Signing Key (2006) < newbielink:mailto:ftpmaster@debian.org [nonactive]>


What am I missing ?

Thanks in advance,

regards,

Rob.

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
WARNING: The following packages cannot be authenticated!
« Reply #1 on: January 15, 2007, 11:57:16 am »
I have the same problem. Also, I get a lot of missed package definitions when I run apt-get update:
Code: newbielink:javascript:void(0); [nonactive]
W: Couldn't stat source package list http://deb.plutohome.com replacements/non-free Packages (/var/lib/apt/lists/deb.plutohome.com_debian_dists_replacements_non-free_binary-i386_Packages) - stat (2 No such file or directory)
W: Couldn't stat source package list http://deb.plutohome.com replacements/contrib Packages (/var/lib/apt/lists/deb.plutohome.com_debian_dists_replacements_contrib_binary-i386_Packages) - stat (2 No such file or directory)
W: Couldn't stat source package list http://deb.plutohome.com replacements/non-free Packages (/var/lib/apt/lists/deb.plutohome.com_debian_dists_replacements_non-free_binary-i386_Packages) - stat (2 No such file or directory)
W: Couldn't stat source package list http://deb.plutohome.com replacements/contrib Packages (/var/lib/apt/lists/deb.plutohome.com_debian_dists_replacements_contrib_binary-i386_Packages) - stat (2 No such file or directory)
W: Duplicate sources.list entry http://deb.plutohome.com 20dev/main Packages (/var/lib/apt/lists/deb.plutohome.com_debian_dists_20dev_main_binary-i386_Packages)
W: Duplicate sources.list entry http://deb.plutohome.com replacements/main Packages (/var/lib/apt/lists/deb.plutohome.com_debian_dists_replacements_main_binary-i386_Packages)
W: You may want to run apt-get update to correct these problems
E: Some index files failed to download, they have been ignored, or old ones used instead.                                          

My /ets/apt/sources.list file contains following:
Code: newbielink:javascript:void(0); [nonactive]
# Pluto sources - start
deb file:/usr/pluto/deb-cache/ sarge main
deb http://deb.plutohome.com/debian/ 20dev main
deb http://deb.plutohome.com/debian/ replacements main
deb http://deb.plutohome.com/debian/ sarge main non-free contrib
deb http://deb.plutohome.com/debian/ unstable mythtv
deb http://www.yttron.as.ro/ sarge main
# Pluto sources - end
deb http://deb.plutohome.com/debian/ replacements main non-free contrib
deb http://www.yttron.as.ro/ unstable main
deb http://www.yttron.as.ro/ realextra main
deb http://deb.plutohome.com/debian 20dev main

archived

  • Hello, I'm new here
  • Posts: 0
    • View Profile
WARNING: The following packages cannot be authenticated!
« Reply #2 on: January 15, 2007, 04:54:35 pm »
It seems that this warning is harmful, although it wouldn't be bad to have proper package authentication procedure.

Regards,

Rob.