severity 418825 normal tag 418825 + etch thanks Hi,
First of all, excuse us for taking so long to answer to this mail. mod_perl2 was sadly undermaintained, and its bugs were left to rot - even when ranked at a high severity. I just adopted this package today. I am downgrading this bug to "normal", as it includes a workaround, and will work on a way to address it for users who have not yet upgraded. However, automatic upgrades will probably just not work - When Sarge was frozen as the stable version back in 2005, mod_perl2 was just about to stabilize its API - It was named libapache2-mod-perl2, and most of the API was in place, but you will understand from the 1.999.21-1 version number something was just about to happen. And it happened - Apache modules written with the previous API will not work with the current one. The changes are simple, however, and documented. Please take a look at Apache's "A Reference to mod_perl 1.0 to mod_perl 2.0 Migration" [1] and (if your modules mix Perl and C code) "Porting Apache:: XS Modules from mod_perl 1.0 to 2.0". For some discussion on the rationale behind the Apache authors for this change, you should also read "mod_perl 2.0 renaming" [3]. Keep in mind that the modules you developed for Sarge are made for an intermediate API - They are no longer compatible with Apache 1.x's mod_perl API, but they are still not 2.0 compliant. Thank you for your understanding, and apologies for not making this known to you in advance. Greetings, [1] http://perl.apache.org/docs/2.0/user/porting/compat.html [2] http://perl.apache.org/docs/2.0/devel/porting/porting.html [3] http://perl.apache.org/docs/2.0/rename.html -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
