Can anyone suggest why my apt has got volatile-sloppy with a weighting
of 1 rather than the default of 500?
guinness:/etc/apt# apt-cache policy spamassassin
spamassassin:
Installed: 3.0.3-2sarge1
Candidate: 3.0.3-2sarge1
Version Table:
3.1.0a-0volatile3 0
1 ftp://ftp.planetmirror.com sarge/volatile-sloppy/main Packages
1 http://volatile.debian.net sarge/volatile-sloppy/main Packages
*** 3.0.3-2sarge1 0
500 http://ftp.iinet.net.au sarge/updates/main Packages
500 http://security.debian.org sarge/updates/main Packages
100 /var/lib/dpkg/status
3.0.3-2 0
500 http://ftp.iinet.net.au sarge/main Packages
500 http://ftp.uwa.edu.au sarge/main Packages
guinness:/etc/apt#
I read through the "APT not using packages from volatile" from March
this year but the culprit there seemed to be caused by apt/preferences.
There's no /etc/apt/preferences file, and apt.conf contains only my
Acquire::http::Proxy directive. apt.conf.d contains the following:
10apt-listbugs 20listchanges 70debconf 90debsums 99-localepurge
None of them seem to have anything to do with it. I haven't done any
apt pinning on this server.
Would appreciate any suggestions. I could just forcibly install the
package file with dpkg but that'd kinda take the fun out of it. =)
Andrew.
--
Andrew Shugg <andrew@neep.com.au> http://www.neep.com.au/
"Just remember, Mr Fawlty, there's always someone worse off than yourself."
"Is there? Well I'd like to meet him. I could do with a good laugh."
Attachment:
pgp20ExLoal5U.pgp
Description: PGP signature