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.