Bug#913249: lighttpd: Can't locate Term/ReadLine.pm in @INC

[Olaf van der Spek]

Package: lighttpd
Version: 1.4.49-1.1+b1
Severity: normal

Dear Maintainer,

# lighty-enable-mod ssl

Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.0 /usr/local/share/perl/5.28.0 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/sbin/lighty-enable-mod line 17.
BEGIN failed--compilation aborted at /usr/sbin/lighty-enable-mod line 17.

Gr,

Olaf

-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lighttpd depends on:
ii libattr1 1:2.4.47-2+b2
ii libbz2-1.0 1.0.6-9
ii libc6 2.27-8
ii libfam0 2.7.0-17.2+b1
ii libldap-2.4-2 2.4.46+dfsg-5+b1
ii libmariadbclient18 1:10.1.37-1
ii libpcre3 2:8.39-11
ii libssl1.1 1.1.1-2
ii lsb-base 9.20170808
ii mime-support 3.61
ii zlib1g 1:1.2.11.dfsg-1

Versions of packages lighttpd recommends:
ii spawn-fcgi 1.6.4-2

Versions of packages lighttpd suggests:
pn apache2-utils <none>
pn lighttpd-doc <none>
ii openssl 1.1.1-2
pn php-cgi <none>
pn rrdtool <none>

-- no debconf information

[Adam Borowski]

Fix: Depends: perl

Term/ReadLine.pm lives in perl-modules-5.28, but its description wants
packages to depend on "perl". Let's do so.

[Debian Bug Tracking System]

Your message dated Mon, 03 Dec 2018 03:49:23 +0000
with message-id <E1gTfEZ-000Hcr-***@fasolo.debian.org>
and subject line Bug#913249: fixed in lighttpd 1.4.49-2
has caused the Debian Bug report #913249,
regarding lighttpd: Can't locate Term/ReadLine.pm in @INC
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)