Bjørn Mork <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED]:~$ apt-cache policy spamassassin > spamassassin: > Installed: 3.2.3-0.volatile1 > Candidate: 3.2.3-0.volatile1 > Package pin: (not found) > Version table: > *** 3.2.3-0.volatile1 750 > 100 /var/lib/dpkg/status > 3.2.1-1 750 > 650 http://ftp.no.debian.org lenny/main Packages > 3.1.7-2 750 > 700 http://ftp.no.debian.org etch/main Packages > > > Just in case anyone cares about that upgrade path...
oops, I just read the volatile policy on http://www.debian.org/devel/debian-volatile/ and noticed that this probably violates it: "The upgrade path from volatile to the next stable release needs to be at least as easy as for the stable release; version numbers in volatile must not be higher than those in testing, for instance." I guess the best would be if there were a SA 3.2.3 release in testing with a higher version number before introducing it in volatile. Bjørn -- Why, it's OK to run down Moonie people -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
