Re: Spamassassin 3.1

[Martin Zobel-Helas <zobel@ftbfs.de>]

Hi Alessio,

On Thu, Jun 08, 2006 at 10:09:04AM +0200, Alessio Fattorini <a.fattorini@abanet.it> wrote:

> Hi allz,
> I type:
> 
> radiant:~# apt-get -s install spamassassin
> Lettura della lista dei pacchetti in corso... Fatto
> Generazione dell'albero delle dipendenze in corso... Fatto
> Pacchetti suggeriti:
>   libnet-smtp-perl libmail-spf-query-perl razor libnet-ident-perl
> libio-socket-ssl-perl dcc-client pyzor
> I seguenti pacchetti saranno aggiornati:
>   spamassassin
> 1 aggiornati, 0 installati, 0 da rimuovere e 22 non aggiornati.
> Inst spamassassin [3.0.3-2] (3.0.3-2sarge1 Debian-Security:3.1/stable)
> Conf spamassassin (3.0.3-2sarge1 Debian-Security:3.1/stable)
> 
> why not spamassassin 3.1??
> My repo is deb http://volatile.debian.net/debian-volatile sarge/volatile
> main contrib non-free
> but with sloppy is the same thing

apt-cache policy spamassassin

please also read
http://lists.debian.org/debian-volatile-announce/debian-volatile-announce-2005/msg00011.html
where it  says about /etc/apt/preferences:

> In addition, you need to pin spamassassin and/or spamc in /etc/apt/preferences:
> 
>  Package: spamassassin
>  Pin: release a=sarge-sloppy, version 3.1.0a*
>  Pin-Priority: 500
> 
>  Package: spamc
>  Pin: release a=sarge-sloppy, version 3.1.0a*
>  Pin-Priority: 500

and

> [...]
> For this reasons, this package was accepted into the sloppy section of the
> volatile archiv, means: updates are not installed automatically until the
> package is pinned up accordingly.



Greetings