Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-12-06 Thread Robert J. Clay
Neil,

As a reminder;  the title of the bug you opened was changed to the
following to better reflect the issue with the sql-ledger package:

sql-ledger: Can't locate bin/mozilla/login.pl in @INC


On Sun, Jul 30, 2017 at 4:09 AM, Neil Redgate  wrote:
> 
> I have contacted the developer of sql-ledger and he has given me a couple of
> suggestions - which I hope to look into later today.

   And did any of those suggestions help?

   Since there is going to be the same issue with any of the more
recent versions of Perl, I've been wondering if he was going to
release a new version that fixed the issue...


> If I have success, I will certainly post my findings.

   Should it be assumed, then, that you did not have any success?
I've not seen any follow up messages from you about it...



-- 
Robert J. Clay
rjc...@gmail.com



Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-08-04 Thread gregor herrmann
On Fri, 04 Aug 2017 04:09:21 -0400, Robert J. Clay wrote:

> On Tue, Aug 1, 2017 at 5:21 AM, Neil Redgate  wrote:
> >
> > Hi Gregor,
> >
> > While investigating this problem, I came across bug #865020 (message
> > #1524985) concerning postgresql9.6, perl5.26 and postgresql-plperl?
> 
>   Perhaps gregor can correct me If I'm wrong but that bug does not look to
> be related to the bug that you reported.  (The title for which, btw, has
> been changed to be "sql-ledger: Can't locate bin/mozilla/login.pl in @INC".)

I agree, this looks like an unrelated issue.
 
Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature


Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-08-04 Thread Robert J. Clay
Neil,

Neil,


On Tue, Aug 1, 2017 at 5:21 AM, Neil Redgate  wrote:
>
> Hi Gregor,
>
> While investigating this problem, I came across bug #865020 (message
> #1524985) concerning postgresql9.6, perl5.26 and postgresql-plperl?
>

  Perhaps gregor can correct me If I'm wrong but that bug does not look to
be related to the bug that you reported.  (The title for which, btw, has
been changed to be "sql-ledger: Can't locate bin/mozilla/login.pl in @INC".)



> It looks like an upgrade is forthcoming sometime this month
>
>   Actually; the bug looks to have been closed already and the version that
closed it made it to Testing on 26 July...



-- 
Robert J. Clay
rjc...@gmail.com
Debian Maintainer


Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-08-01 Thread Neil Redgate
On Fri, 28 Jul 2017 10:37:38 -0400 gregor herrmann 
wrote:
> On Fri, 28 Jul 2017 14:45:11 +0100, Neil Redgate wrote:
> 
> Thanks for your detailed bug report!
> 
> > I can no longer access my postgressql database using any web
browser for the
> > sql-ledger 3.2.4 package.
> 
> > [Fri Jul 28 13:45:40.995556 2017] [cgi:error] [pid 6345] [client
::1:40496] End
> > of script output before headers: admin.pl
> > [Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231] [client
::1:40500]
> > AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC contains:
/etc/perl
> > /usr/local/lib/x86_64-linux-gnu/perl/5.26.0
/usr/local/share/perl/5.26.0
> > /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5
/usr/lib/x86_64-linux-
> > gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
> > /usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-
ledger/login.pl line
> > 119.: /usr/local/sql-ledger/login.pl
> > [Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231] [client
::1:40500] End
> > of script output before headers: login.pl
> 
> I'm afraid there's not much we can do here.
/etc/perl/sitecustomize.pl
> was a temporary workaround which is gone for good now.
> 
> It seems that you are using sql-ledger 3.2.4 which is not packaged in
> Debian and installed in /usr/local/sql-ledger, and that this version
> is not updated to work with Perl 5.26. (I had a brief look at 3.2.5
> and it looks like it still does the same "do $file").
> 
> https://metacpan.org/pod/release/XSAWYERX/perl-5.26.0/pod/perldelta.p
od#Removal-of-the-current-directory-%28%22.%22%29-from-@INC
> has background information and a couple of suggestions to remedy the
> situation which you can try yourself and/or suggest to the sql-ledger
> upstream authors.
> 
> (Not closing the bug report yet in case the perl maintainers have
> something to add.)
> 
> 
> Cheers,
> gregor
> 
> -- 
>  .''`.  https://info.comodo.priv.at/ - Debian Developer
https://www.debian.org
>  : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801
8649 AA06
>  `. `'  Member of VIBE!AT & SPI, fellow of the Free Software
Foundation Europe
>`-   

Hi Gregor,

While investigating this problem, I came across bug #865020 (message
#1524985) concerning postgresql9.6, perl5.26 and postgresql-plperl?
It looks like an upgrade is forthcoming sometime this month

yours
Neil


-- 

  
  


Neil Redgate







Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-30 Thread gregor herrmann
On Sun, 30 Jul 2017 09:09:16 +0100, Neil Redgate wrote:

> Thank you for your calm and considered reply.

You're welcome!
 
> Please accept my apologies for the tone of my message - I hadn't
> realised how much my frustration was exhibited at the situation
> I did not look forward to having to find an alternative to sql-ledger
> (which suited my needs perfectly).

No worries, I know how frustrating it can be when some piece of
software suddenly stops working.
 
> I have contacted the developer of sql-ledger and he has given me a
> couple of suggestions - which I hope to look into later today.
> If I have success, I will certainly post my findings.

Excellent, thank you.
 
> I accept the terms for running testing and, although I am not
> knowledgeable with programming, I like to think I can contribute by
> identifying faults with respect to my particular setup, investigating
> and testing any remedies etc in the anticipation that it may help
> others

That's indeed a valuable contribution to free software.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature


Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-30 Thread Neil Redgate
On Sat, 29 Jul 2017 12:18:48 -0400 gregor herrmann 
wrote:
> On Sat, 29 Jul 2017 08:12:28 +0100, Neil Redgate wrote:
> 
> > Thank you for your quick reply.
> 
> You're welcome.
>  
> > I am disappointed to learn that this problem is not fixable but at
> > least I know what the situation is.
> 
> "not fixable" is a bit too strong IMO; there won't be a "fix" on the
> perl side in Debian but there are other options:
> 
> > I will attempt to let the sql-ledger developer know of the
situation
> > though I am not a subscriber to their forum.
> 
> Having sql-leder work with perl 5.26 by making changes upstream would
> be the best way forward.
> 
> Fixing the code yourself is another option.
> And then it's also possible to fix the packaged (currently rather
> old) version of sql-ledger in debian (which would need a new
> maintainer first as the package is oprhaned -- but I already heard of
> a person interested in the task), then you could switch to the debian
> version.
> 
> > Can you confirm that perl 5.26 is being applied on all OS -
windows,
> > mac & linux?
> 
> It exists on all platforms; if it's installed probably depends on the
> (packaging system of in the absence thereof on the) local admin.
> 
> > Is it possible to have both perl 5.24 and 5.26 running on the same
> > linux system?
> 
> No, at least under Debian and derivatives.
> 
> But debian stable contains 5.24 and will be supported for another
> couple of years; the problems you are facing come from running
> testing where you got all the shiny new developments early :)
>  
> 
> Cheers,
> gregor
> 
> -- 
>  .''`.  https://info.comodo.priv.at/ - Debian Developer
https://www.debian.org
>  : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801
8649 AA06
>  `. `'  Member of VIBE!AT & SPI, fellow of the Free Software
Foundation Europe
>`-   


Hi Gregor,

Thank you for your calm and considered reply.

Please accept my apologies for the tone of my message - I hadn't
realised how much my frustration was exhibited at the situation
I did not look forward to having to find an alternative to sql-ledger
(which suited my needs perfectly).

I have contacted the developer of sql-ledger and he has given me a
couple of suggestions - which I hope to look into later today.
If I have success, I will certainly post my findings.

I accept the terms for running testing and, although I am not
knowledgeable with programming, I like to think I can contribute by
identifying faults with respect to my particular setup, investigating
and testing any remedies etc in the anticipation that it may help
others

with very best wishes
Neil




-- 

  
  


Neil Redgate







Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-29 Thread gregor herrmann
On Sat, 29 Jul 2017 08:12:28 +0100, Neil Redgate wrote:

> Thank you for your quick reply.

You're welcome.
 
> I am disappointed to learn that this problem is not fixable but at
> least I know what the situation is.

"not fixable" is a bit too strong IMO; there won't be a "fix" on the
perl side in Debian but there are other options:

> I will attempt to let the sql-ledger developer know of the situation
> though I am not a subscriber to their forum.

Having sql-leder work with perl 5.26 by making changes upstream would
be the best way forward.

Fixing the code yourself is another option.
And then it's also possible to fix the packaged (currently rather
old) version of sql-ledger in debian (which would need a new
maintainer first as the package is oprhaned -- but I already heard of
a person interested in the task), then you could switch to the debian
version.

> Can you confirm that perl 5.26 is being applied on all OS - windows,
> mac & linux?

It exists on all platforms; if it's installed probably depends on the
(packaging system of in the absence thereof on the) local admin.

> Is it possible to have both perl 5.24 and 5.26 running on the same
> linux system?

No, at least under Debian and derivatives.

But debian stable contains 5.24 and will be supported for another
couple of years; the problems you are facing come from running
testing where you got all the shiny new developments early :)
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature


Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-29 Thread Neil Redgate
On Fri, 28 Jul 2017 14:03:29 -0400 gregor herrmann 
wrote:
> Control: reassign -1 sql-ledger 3.0.8-1
> Control: tag -1 + upstream buster sid
> 
> On Fri, 28 Jul 2017 16:05:11 +0100, Dominic Hargreaves wrote:
> 
> > > > [Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231]
[client ::1:40500]
> > > > AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC
contains: /etc/perl
> > > > /usr/local/lib/x86_64-linux-gnu/perl/5.26.0
/usr/local/share/perl/5.26.0
> > > > /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5
/usr/lib/x86_64-linux-
> > > > gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
> > > > /usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-
ledger/login.pl line
> > > > 119.: /usr/local/sql-ledger/login.pl
> > > > [Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231]
[client ::1:40500] End
> > > > of script output before headers: login.pl
> 
> [..]
> 
> > I noticed that we do have an sql-ledger package in Debian, but that
> > hasn't been updated since before the @INC fix was made, so it's
quite
> > likely to also be completely broken there.
> 
> Sorry for missing the (not used by the reporter) packaged version;
> and yes, AFAICS it has the same problem:
> 
> https://sources.debian.net/src/sql-ledger/3.0.8-1/login.pl/
> line 120
> 
> Reassigning the bug now.
>  
> Cheers,
> gregor
> 
> -- 
>  .''`.  https://info.comodo.priv.at/ - Debian Developer
https://www.debian.org
>  : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801
8649 AA06
>  `. `'  Member of VIBE!AT & SPI, fellow of the Free Software
Foundation Europe
>`-   

Gregor / Dominic

Thank you for your quick reply.

I am disappointed to learn that this problem is not fixable but at
least I know what the situation is.
I will attempt to let the sql-ledger developer know of the situation
though I am not a subscriber to their forum.
The alternative is to try and find an equal alternative to sql-ledger
(not very hopeful)

Can you confirm that perl 5.26 is being applied on all OS - windows,
mac & linux?
Is it possible to have both perl 5.24 and 5.26 running on the same
linux system?

very many thanks for all your help
Neil


-- 

  
  


Neil Redgate







Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-28 Thread gregor herrmann
Control: reassign -1 sql-ledger 3.0.8-1
Control: tag -1 + upstream buster sid

On Fri, 28 Jul 2017 16:05:11 +0100, Dominic Hargreaves wrote:

> > > [Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231] [client 
> > > ::1:40500]
> > > AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC contains: 
> > > /etc/perl
> > > /usr/local/lib/x86_64-linux-gnu/perl/5.26.0 /usr/local/share/perl/5.26.0
> > > /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
> > > /usr/lib/x86_64-linux-
> > > gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
> > > /usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-ledger/login.pl 
> > > line
> > > 119.: /usr/local/sql-ledger/login.pl
> > > [Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231] [client 
> > > ::1:40500] End
> > > of script output before headers: login.pl

[..]

> I noticed that we do have an sql-ledger package in Debian, but that
> hasn't been updated since before the @INC fix was made, so it's quite
> likely to also be completely broken there.

Sorry for missing the (not used by the reporter) packaged version;
and yes, AFAICS it has the same problem:

https://sources.debian.net/src/sql-ledger/3.0.8-1/login.pl/
line 120

Reassigning the bug now.
 
Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature


Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-28 Thread Dominic Hargreaves
Control: retitle -1 sql-ledger: Can't locate bin/mozilla/login.pl in @INC

On Fri, Jul 28, 2017 at 10:37:38AM -0400, gregor herrmann wrote:
> On Fri, 28 Jul 2017 14:45:11 +0100, Neil Redgate wrote:
> 
> Thanks for your detailed bug report!
> 
> > I can no longer access my postgressql database using any web browser for the
> > sql-ledger 3.2.4 package.
> 
> > [Fri Jul 28 13:45:40.995556 2017] [cgi:error] [pid 6345] [client ::1:40496] 
> > End
> > of script output before headers: admin.pl
> > [Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231] [client ::1:40500]
> > AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC contains: /etc/perl
> > /usr/local/lib/x86_64-linux-gnu/perl/5.26.0 /usr/local/share/perl/5.26.0
> > /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-
> > gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
> > /usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-ledger/login.pl line
> > 119.: /usr/local/sql-ledger/login.pl
> > [Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231] [client ::1:40500] 
> > End
> > of script output before headers: login.pl
> 
> I'm afraid there's not much we can do here. /etc/perl/sitecustomize.pl
> was a temporary workaround which is gone for good now.
> 
> It seems that you are using sql-ledger 3.2.4 which is not packaged in
> Debian and installed in /usr/local/sql-ledger, and that this version
> is not updated to work with Perl 5.26. (I had a brief look at 3.2.5
> and it looks like it still does the same "do $file").
> 
> https://metacpan.org/pod/release/XSAWYERX/perl-5.26.0/pod/perldelta.pod#Removal-of-the-current-directory-%28%22.%22%29-from-@INC
> has background information and a couple of suggestions to remedy the
> situation which you can try yourself and/or suggest to the sql-ledger
> upstream authors.
> 
> (Not closing the bug report yet in case the perl maintainers have
> something to add.)

Thanks gregoa for your investigation/response. I can confirm that I don't
think we can do anything here, unfortunately, as (after around a year)
we have indeed removed the workaround to enable potentially unsafe
operation.

I noticed that we do have an sql-ledger package in Debian, but that
hasn't been updated since before the @INC fix was made, so it's quite
likely to also be completely broken there.

The next steps for this bug report are to check whether the sql-ledger
package has the same problem, and if so reassign it. If the answer is
no, then that might at least point the way towards a resolution for the
reporter.

Cheers,
Dominic.



Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-28 Thread gregor herrmann
On Fri, 28 Jul 2017 14:45:11 +0100, Neil Redgate wrote:

Thanks for your detailed bug report!

> I can no longer access my postgressql database using any web browser for the
> sql-ledger 3.2.4 package.

> [Fri Jul 28 13:45:40.995556 2017] [cgi:error] [pid 6345] [client ::1:40496] 
> End
> of script output before headers: admin.pl
> [Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231] [client ::1:40500]
> AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC contains: /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.0 /usr/local/share/perl/5.26.0
> /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-
> gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-ledger/login.pl line
> 119.: /usr/local/sql-ledger/login.pl
> [Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231] [client ::1:40500] 
> End
> of script output before headers: login.pl

I'm afraid there's not much we can do here. /etc/perl/sitecustomize.pl
was a temporary workaround which is gone for good now.

It seems that you are using sql-ledger 3.2.4 which is not packaged in
Debian and installed in /usr/local/sql-ledger, and that this version
is not updated to work with Perl 5.26. (I had a brief look at 3.2.5
and it looks like it still does the same "do $file").

https://metacpan.org/pod/release/XSAWYERX/perl-5.26.0/pod/perldelta.pod#Removal-of-the-current-directory-%28%22.%22%29-from-@INC
has background information and a couple of suggestions to remedy the
situation which you can try yourself and/or suggest to the sql-ledger
upstream authors.

(Not closing the bug report yet in case the perl maintainers have
something to add.)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature


Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-28 Thread Neil Redgate
Package: perl
Version: 5.26.0-4
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

The perl 5.26 update on 26th July disabled the file /etc/perl/sitecustomize.pl
.
There were no problems with perl 5.24.

I can no longer access my postgressql database using any web browser for the
sql-ledger 3.2.4 package.
I just get the Internal Server Error - "The server encountered an internal
error or misconfiguration and was unable to complete your request"
Previous remedies included disabling the only line of command in the
sitecustomize.pl file

I have tried re-enabling the sitecustomize.pl file, followed by restarting the
apache2 and postgresql services (separate commands)  each time after making the
code in the file active or disabled. On all occasions the browser shows the
Internal Server Error message.

I can access postgres using the terminal (command line) and using pgAdmin3,
phpPgAdmin.
Apache2 works as I can access other packages through localhost.

When trying to open my postgres database using my web browser (epiphany-
browser) and see the Internal Server Error - I attach below the relevant part
of the apache2/error.log for this action -


[Fri Jul 28 13:45:40.995556 2017] [cgi:error] [pid 6345] [client ::1:40496] End
of script output before headers: admin.pl
[Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231] [client ::1:40500]
AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.0 /usr/local/share/perl/5.26.0
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-
gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-ledger/login.pl line
119.: /usr/local/sql-ledger/login.pl
[Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231] [client ::1:40500] End
of script output before headers: login.pl

Looking at the above error text, my system (testing with daily updates) does
not have /usr/local/share/perl nor /usr/local/lib/site_perl.
I created a soft link to /usr/share/perl in /usr/local/share - restarted
apache2 & postgresql services = problem not fixed.

There is no directory site_perl on my system, so I cannot create the
appropriate link.


I trust the above is helpful to identify the problem with the @INC feature
Please accept my apologies for any expected information normally submitted with
a bug report (my first time)
If you require any other information, please let me know

Neil




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

Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages perl depends on:
ii  dpkg   1.18.24
ii  libperl5.265.26.0-4
ii  perl-base  5.26.0-4
ii  perl-modules-5.26  5.26.0-4

Versions of packages perl recommends:
ii  netbase  5.4
ii  rename   0.20-4

Versions of packages perl suggests:
ii  libterm-readline-gnu-perl   1.35-1+b2
ii  libterm-readline-perl-perl  1.0303-1
ii  make4.1-9.1
ii  perl-doc5.26.0-4

-- no debconf information