Bug#666844: advice on backporting libembperl-perl

[Arno Töll]

Hi,

On 26.05.2013 18:24, Ondřej Surý wrote:
> Just fix the transition bug and make the package buildable with both Apache 2.2 and 2.4.

That's easily doable for web-applications only. Modules, are more
complicated. If you really want, I guess we could find some
configuration which pleases Apache 2.2 and 2.4, but frankly I doubt it's
worth the effort.

If you feel the need, you can downgrade this bug's severity, and "cheat"
libembperl-perl into Testing before we're going to actually break Sid. I
do not expect an Apache 2.4 stack in Testing anytime soon so that will
give you some time.

Having that said, keep in mind, that your package may migrate at some
point in a 2.4 enabled version to Testing, which is highly unlikely to
be considered backport material. Thus, a backport of the "last version
before you upload a 2.4 version" would be an isolated backport, which
diverges from the actual package in Testing at some point.


-- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-perl-maintainers/attachments/20130526/3e253a0b/attachment-0001.pgp>