Control: tag -1 -moreinfo

-=| Cyril Brulebois, 12.11.2014 13:32:44 +0100 |=-
> Damyan Ivanov <d...@debian.org> (2014-11-12):
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian....@packages.debian.org
> > Usertags: unblock
> > 
> > Please unblock package libcatalyst-perl.
> > 
> > Version 5.90075-2 removes an obsolete dependency on 
> > libcatalyst-engine-psgi-perl, which will be removed from the archive 
> > because it is obsolete and FTBFS with current libcatalyst-perl.
> > 
> > libcatalyst-perl builds fine without that build-dependency and the 
> > build-time test suite completes successfuly.
> > 
> > The bug against libcatalyst-perl is https://bugs.debian.org/769093 -- 
> > Please stop build-depending on libcatalyst-engine-psgi-perl which will 
> > be removed
> 
> Does this mean users are losing support for psgi (which might have been
> auto-enabled previously but which wouldn't be enabled anymore due to the
> removed build-dep)?
> 
> Just double checking; I'm not sure since the binary doesn't seem to
> depend on or even suggest said package.

Short answer: PSGI support in Catalyst is kept.

From upstream changelog:

   - Removed code related to supporting the long deprecated stand 
     alone PSGI Engine.  If you are still using this you code is now 
     broken. Luckily you can just stop using it and likely everything 
     will work under the new PSGI support built into Catalyst for 
     several years.

So Catalyst still has its internal support for PSGI, which is also the 
recommended one, and they just dropped support for the deprecated 
external PSGI engine in libcatalyst-engine-psgi-perl.

libcatalyst-perl was build-depending on libcatalyst-engine-psgi-perl 
since there were some tests which required it. These tests are gone 
since version 5.90070, but we didn't notice that and kept the 
build-dependency.

Now that we want to drop the deprecated libcatalyst-engine-psgi-perl 
from the archive, the build-dependency stands in the way and needs to 
be removed.


I hope this brings enough light. Sorry for not being clear enough with 
the initial report.


Cheers,
    dam

Attachment: signature.asc
Description: Digital signature

Reply via email to