RE: sarge package transition
> Recently sarge has received a new version of perl but apache
> and mod-perl
> packages in sarge are old. Until the sid packages will not enter sarge
> there is no way for us to "fix" this problem since it is already fixed
> since a while in sid. We have no control over the package
> flow from sid to
> sarge, the only way is to wait.
Would it not be better to make the apache-mod-perl package depend on exactly the version of perl it was built with? That way users should get something that warns them that somethings going on...
Carl--------------------------------------------------------
GMG Regional Digital is part of the Guardian Media Group plc.
CONFIDENTIALITY NOTICE. The information contained in this e-mail is intended only for debian-apache@lists.debian.org. It may contain privileged and confidential information that is exempt from disclosure by law and if you are not an intended recipient, you must not copy, distribute or take any action in reliance on it. If you have received this e-mail in error, you may notify our helpdesk by telephone on 44 (0)161 211 2222. E-mail transmission cannot be guaranteed to be secure or error-free. The sender (carl.johnstone@gmgrd.co.uk) therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
Reply to: