Adopting libapache-mod-jk and libapache2-mod-jk2

[Wolfgang Baer]

Michael Koch wrote:
> On Wed, Sep 07, 2005 at 11:24:47AM +0200, Wolfgang Baer wrote:
> 
>>Guus Sliepen wrote:
>>
>>>On Tue, Sep 06, 2005 at 09:40:42PM +0200, Wolfgang Baer wrote:

>>>
>>>AFAIK there is no Supersedes: option for control files, but I wouldn't
>>>Conflict, Provide or Replace libapache2-mod-jk2. There is no technical
>>>reason why the packages couldn't coexist, and since the configuration
>>>files have a different format you can't just replace jk2 with jk.
>>
>>Sure they can coexist - however we want to remove libapache2-mod-jk2
>>from the archive after mod-jk for apache 2 will be availabe. Therefore
>>anything which would inform users to change to the new package would
>>be good ...
> 
> 
> The normal location for this is an entry in the NEWS.Debian file. This
> is what the policy recommends for this. This file is specially handled by
> several tools like apt-listchanges and will prompted to the use on
> install/upgrade once.
> 
> Personally I would add a debconf dialog too but that is seen as abuse from
> many DDs so don't do it.

Well in the NEWS.Debian file of the mod-jk packages is already an entry.
But this file won't see any user of the mod-jk2 (libapache2-mod-jk2)
package.

To upload a new mod-jk2 package with either a debconf message or a NEWS
entry is something which would mean that we have to keep the mod-jk2
package in the archive until after etch releases. Otherwise only the
current etch/sid users would get informed and not the users upgrading
from sarge to etch (when its released).

And as said - I would like to remove the mod-jk2 packages from the
archive.

Wolfgang