Bug#666844: advice on backporting libembperl-perl

[Ondřej Surý]

Just fix the transition bug and make the package buildable with both Apache 2.2 and 2.4.

The Apache 2.4 have some hints how to accomplish that.

Ondřej Surý

On 26. 5. 2013, at 18:22, Florian Schlichting <fsfs at debian.org> wrote:

> Hi Arno,
> 
> On Sun, May 26, 2013 at 05:33:47PM +0200 on debian-backports, Micha 
> Lenk wrote:
>> Couldn't you also explain your situation in #666844, and (with consent
>> of Arno and who else might have a say) lower the severity of #666844
>> until libembperl-perl hits testing, and then raise its severity back to RC?
> 
> so here we go:
> 
> libembperl-perl was removed from wheezy in 2011 because it failed to
> build with current versions of Perl and mod_perl for a long time. This
> was eventually fixed upstream late last year, but of course couldn't be
> included in the wheezy release any more. I promised to provide a
> backport once wheezy is released.
> 
> However, before the first dinstall after the wheezy release, you
> upgraded #666844 (sourceful transition towards Apache 2.4) to RC, and
> thus libembperl-perl won't migrate to testing.
> 
> In order to provide users of libembperl-perl in squeeze with an upgrade
> path to wheezy, and considering that the Apache 2.4 transition is not
> going to affect wheezy, would it be acceptable from the point of view of
> the Apache maintainers planning the 2.4 transition to lower the severity
> of #666844 for a day or so until libembperl-perl has entered testing?
> 
> Florian
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-backports-request at lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster at lists.debian.org
> Archive: http://lists.debian.org/20130526162230.GI831733@ZEDAT.FU-Berlin.DE
>