Hi,

As you can see from the message below, we are considering removing Embperl
from Debian because of concerns about not being actively maintained. We
have had to patch it several times to cope with changes in newer upstream
versions over the past few years, and we don't think it is really being
used much in Debian any more.

Interested if anyone has any thoughts on this from the user or upstream
dev perspective.

Best,
Dominic.

----- Forwarded message from Dominic Hargreaves <d...@earth.li> -----

Date: Fri, 18 May 2018 17:08:38 +0200
From: Dominic Hargreaves <d...@earth.li>
To: sub...@bugs.debian.org
Subject: Bug#899021: libembperl-perl: FTBFS with Perl 5.27, unmaintained
        upstream
Reply-To: Dominic Hargreaves <d...@earth.li>, 899...@bugs.debian.org

Source: libembperl-perl
Version: 2.5.0-11
Severity: serious
Justification: unmaintained upstream, and will shortly break in Debian
X-Debbugs-Cc: debian-p...@lists.debian.org
User: debian-p...@lists.debian.org
Usertags: perl-5.28-transition hh2018

The upstream version of this package has not worked since 5.18, and we
have had to apply several fixes in Debian since. The build has now
broken again with Perl 5.27:

http://perl.debian.net/rebuild-logs/perl-5.27-throwaway/libembperl-perl_2.5.0-11/libembperl-perl_2.5.0-11_amd64-2018-05-18T08:09:28Z.build

The problem in this case might not be that hard to fix, but I have
been consisdering deprecating/removing this for some time, as there is
a limit to how long we can be de facto upstream for this type of
package.

Currently the package has a popcon of inst: 37 / vote: 22 / recent: 1
suggesting that it is barely used anywhere. So I suggest that rather than
spending any more time maintaining it, we remove it from Debian.

CC to debian-perl to get wider exposure of the proposal.

Cheers,
Dominic.



----- End forwarded message -----

---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscr...@perl.apache.org
For additional commands, e-mail: embperl-h...@perl.apache.org

Reply via email to