Re: samba: untrusted packages ???
helices [EMAIL PROTECTED] writes: * Goswin von Brederlow [EMAIL PROTECTED] [2006:06:04:08:22:41+0200] scribed: helices [EMAIL PROTECTED] writes: What do you think? I think you need to read more. Google a bit and read what errors and warnings you get from commands. Since I updated yesterday, and attempted the samba install, the repository went from this: # apt-cache policy samba samba: Installed: (none) Candidate: 3.0.22-1 Version table: 3.0.22-1 0 500 ftp://mirrors.kernel.org unstable/main Packages 3.0.14a-3 0 100 ftp://debian.csail.mit.edu sarge/main Packages 100 ftp://ftp.at.debian.org sarge/main Packages 100 ftp://mirror.espri.arizona.edu sarge/main Packages To this: # apt-cache policy samba samba-common samba-doc samba: Installed: 3.0.22-1 Candidate: 3.0.22-1 Version table: *** 3.0.22-1 0 700 ftp://mirrors.kernel.org etch/main Packages 700 ftp://mirrors.kernel.org testing/main Packages Those two are the same, testing is a link to etch. Having samba in etch makes 0 difference for the trust/untrust issue though. 500 ftp://mirrors.kernel.org unstable/main Packages 100 /var/lib/dpkg/status 3.0.14a-3 0 100 ftp://debian.csail.mit.edu sarge/main Packages 100 ftp://ftp.at.debian.org sarge/main Packages 100 ftp://mirror.espri.arizona.edu sarge/main Packages Better don't mix sarge and etch. That can confuse apt. Now, of course, the installation went without a hitch; and samba is installed and functioning. However, back to my original problem: what caused the original error? untrusted versions of the following packages will be installed Yes, I googled; and I found several indications of issues with gpg key. So, is this really an apt-key issue, again? How can this be? I have been installing from mirrors.kernel.org for a long time; and onto this new amd64 box for at least one week. Maybe the previous apt-get update call just fetched a broken Release.gpg file and thus failed to authenticate the mirror. Believe it or not, that happens far too often. Now, after the next mirror pulse has corrected the problem, you got a working one and the problem disapeared. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: samba: untrusted packages ???
* Goswin von Brederlow [EMAIL PROTECTED] [2006:06:05:09:38:40+0200] scribed: snip / Better don't mix sarge and etch. That can confuse apt. snip / Where can I read up on the ramifications of this? On this very list, I was advised to use sarge to get kde onto my system. My understanding of apt, preferences and pinning -- although a meager understanding -- is that mixing issues can be mitigated. What am I missing? Maybe the previous apt-get update call just fetched a broken Release.gpg file and thus failed to authenticate the mirror. Believe it or not, that happens far too often. Now, after the next mirror pulse has corrected the problem, you got a working one and the problem disapeared. OK. Is it fair to suppose that I am not a lazy moron; and that this is a fair explanation; rather than that I do not fully understand the subject error message? -- Best Regards, helices - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
Re: samba: untrusted packages ???
helices [EMAIL PROTECTED] writes: * Goswin von Brederlow [EMAIL PROTECTED] [2006:06:05:09:38:40+0200] scribed: snip / Better don't mix sarge and etch. That can confuse apt. snip / Where can I read up on the ramifications of this? On this very list, I was advised to use sarge to get kde onto my system. My understanding of apt, preferences and pinning -- although a meager understanding -- is that mixing issues can be mitigated. What am I missing? That sarge and etch/sid have the same package/version but different md5sum because all packages got rebuild. You can end up with apt-get upgrading a package again and again every time you upgrade. Maybe the previous apt-get update call just fetched a broken Release.gpg file and thus failed to authenticate the mirror. Believe it or not, that happens far too often. Now, after the next mirror pulse has corrected the problem, you got a working one and the problem disapeared. OK. Is it fair to suppose that I am not a lazy moron; and that this is a fair explanation; rather than that I do not fully understand the subject error message? You just didn't read the previous error message when you run apt-get update. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: samba: untrusted packages ???
helices [EMAIL PROTECTED] writes: What do you think? I think you need to read more. Google a bit and read what errors and warnings you get from commands. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: samba: untrusted packages ???
* Goswin von Brederlow [EMAIL PROTECTED] [2006:06:04:08:22:41+0200] scribed: helices [EMAIL PROTECTED] writes: What do you think? I think you need to read more. Google a bit and read what errors and warnings you get from commands. Since I updated yesterday, and attempted the samba install, the repository went from this: # apt-cache policy samba samba: Installed: (none) Candidate: 3.0.22-1 Version table: 3.0.22-1 0 500 ftp://mirrors.kernel.org unstable/main Packages 3.0.14a-3 0 100 ftp://debian.csail.mit.edu sarge/main Packages 100 ftp://ftp.at.debian.org sarge/main Packages 100 ftp://mirror.espri.arizona.edu sarge/main Packages To this: # apt-cache policy samba samba-common samba-doc samba: Installed: 3.0.22-1 Candidate: 3.0.22-1 Version table: *** 3.0.22-1 0 700 ftp://mirrors.kernel.org etch/main Packages 700 ftp://mirrors.kernel.org testing/main Packages 500 ftp://mirrors.kernel.org unstable/main Packages 100 /var/lib/dpkg/status 3.0.14a-3 0 100 ftp://debian.csail.mit.edu sarge/main Packages 100 ftp://ftp.at.debian.org sarge/main Packages 100 ftp://mirror.espri.arizona.edu sarge/main Packages Now, of course, the installation went without a hitch; and samba is installed and functioning. However, back to my original problem: what caused the original error? untrusted versions of the following packages will be installed Yes, I googled; and I found several indications of issues with gpg key. So, is this really an apt-key issue, again? How can this be? I have been installing from mirrors.kernel.org for a long time; and onto this new amd64 box for at least one week. The only difference that I see is: unstable/main Packages -- vs -- etch/main Packages So, I have to ask, are there _different_ keys required for etch and unstable? What do you think? Am I on the right track? -- Best Regards, helices - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . -- signature.asc Description: Digital signature
