On 4/21/08, mouss wrote: > >> The following NEW packages will be installed: > >> libcrypt-openssl-bignum-perl libdb4.6 linux-libc-dev > >> The following packages will be upgraded: > >> binutils libc6 libc6-dev libc6-i686 libcrypt-openssl-rsa-perl > >> libmail-dkim-perl libssl0.9.8 locales perl perl-base perl-modules > > I guess the "problem" is that the installation came at the same time as > other updates. It is surprising to see that you are about to update perl > when you only wanted to add a "minor" package. in short, it's a > "psychological" problem :) >
Since etch stable is two years old now, I really was not expecting the newest amavisd-new to continue to work within its boundries (aside from what may happen in backports), but I _was_ concerned that lenny would freeze at Mail::DKIM version 0.30.1. If that were to happen, 2.6.x may not install without issue on the future lenny stable system. This same type of situation happened with 2.4.x and the former sarge stable branch. Amavisd-new 2.4.x needed Compress::Zlib 1.35 or newer, but this package did not make it to sarge stable. As a result, if one were to install 1.35 or newer from testing or unstable in order to satisfy amavisd-new, gross changes to the system would occur (similar to the ones above - only more dramatic). Sure, there were workarounds to prevent this from happening, but it would be nice if workarounds are not required. So, yes, the main issue centered around fear. -- Gary V ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
