Hi Julian, On Tuesday 11 January 2005 08:25, Julian Mehnle wrote: > > Severity: serious > > Justification: Policy 3.5 > > > > Line 26 of /usr/share/courier-filter-perl/perl5/Courier/Filter.pm is: > > > > use v5.8; > > > > This requirement is not represented in the testing package of > > courier-filter-perl. > > I don't think it has to. courier-filter-perl is only in Debian/testing > (and unstable, but not in older distros), and every version of Perl that > is in testing is absolutely sufficient. > > After all, packages requiring Perl 5.6 don't have to explicitly depend > on it either, do they? Let alone 5.005. At least I can't read that > from policy section 3.5.
The Policy's definition of dependency must include the min. version number required. I can't imagine how else it could work. If a package requires >Perl 5.5, then (I believe) that should be specified in the dependencies. If it does not, I would also consider it a bug. Do you have a specific Sarge package in mind? I would be happy to open this dialog on another front to get more input. :) There maybe something special about packages that depend upon Perl, since it is such a core package. > If you are backporting the package, you are doing so at your own risk > and should adapt the dependencies yourself. What do you think? Here's my take. It is perfectly valid to use testing packages in stable using apt-pinning. My expectation, in this use case, is that apt will tell me if I need dependencies from testing or not. That's where there is a difference between apt-get install -t testing courier-filter-perl and apt-get install courier-filter-perl/testing This is how all other testing packages have behaved when I used apt-pinning. Regards, Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
