On Tue, May 17, 2005 at 04:01:18PM +0200, Steinar H. Gunderson wrote: > On Tue, May 17, 2005 at 02:44:09PM +0100, Stephen Quinney wrote: > > Well, this doesn't help you at all but we don't support mod_perl2 in > > Sid/unstable anymore and I'm expecting that Sarge will be the same > > soon. I'm well aware that being forced to go through a mod_perl2 API > > change at the last minute is going to annoy quite a lot of people... > > Hm, that's a bit unfortunate, but OK. (Is this a permanent change for sid, > or something transient during the API change?) >
The mod_perl2 support will return to Sid/unstable in due course when upstream catches up with the new API. Sarge will ship without support for mod_perl2 in request-tracker3.4, I believe. It's all still up in the air since libapache2-mod-perl2 hasn't actually migrated to Sarge yet but I'm told it will. > > Maybe I should tag this as Sarge/important - important seems > > most appropriate to me - "a bug which has a major effect on the > > usability of a package, without rendering it completely unusable to > > everyone". > > Mm, seems right to me. ok, that's now done. Stephen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
