---------- Forwarded message ----------
From: Robert J. Clay <rjc...@gmail.com>
Date: Thu, Dec 7, 2017 at 10:26 AM
Subject: Re: Bug#869994: sql-ledger: Can't locate bin/mozilla/login.pl in @INC
To: Neil Redgate <nredg...@ndres.co.uk>
Hi Neil!
Note that I've changed the subject for these emails back to reflect
the current title of the bug.
On Thu, Dec 7, 2017 at 6:48 AM, Neil Redgate <nredg...@ndres.co.uk> wrote:
>
> Please see my embedded comments below -
>
>
> On Wed, 2017-12-06 at 12:46 -0500, Robert J. Clay wrote:
>
> 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
>
> Thank you for changing the title.
For the email to which you've just replied; I changed it back to
the old subject so that hopefully you would see it more easily,.
The retitle of the bug itself was done by one of he Debian
Developers who were corresponding with on that bug back then.
> On Sun, Jul 30, 2017 at 4:09 AM, Neil Redgate <nredg...@ndres.co.uk> wrote:
>
>
> I contacted the developer, and he offered the following advice -
>
>
> SQL-Ledger code is generic. There is an
>
> eval { require "sql-ledger.conf"; };
>
> which may call @INC.
>
> comment the line and see if it works.
>
> Unfortunately there was no improvement, ....
I wonder if he (the SQL-Ledger author) has looked at that same Perl
v5.26 reference noted earlier in the bug regarding this issue?
https://metacpan.org/pod/release/XSAWYERX/perl-5.26.0/pod/perldelta.pod#Removal-of-the-current-directory-%28%22.%22%29-from-@INC
What I referenced is in that and what I'm going to try is adding the
following code to the scripts, where that path is as it is installed
with the Debian package:
------<cut>------------------------------------------------
BEGIN {
my $dir = "/usr/share/sql-ledger";
chdir $dir or die "Can't chdir to $dir: $!\n";
# safe now
push @INC, '.';
}
------<cut>------------------------------------------------
Note that I say "try" because although I've created a patch that makes
that change in the application scripts, I still need to create a new
LXC container (with Debian Testing or Unstable installed) where I can
test it after building a test version of the SQL-Ledger package with
that patch..
Note also that I'm still working with the existing version of
SQL-Ledger in Debian, which is still only 3.08. Attempting to build a
new package based on the new SQL-Ledger v3.25 results in other errors
(as I noted in the open bug regarding updating the package to that new
version [1]) and I want to see if this patch helps with this issue
before addressing anything else.
I'll follow up further (to you, as well as the bug), later.
Robert J. Clay
rjc...@gmail.com
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862953
--
Robert J. Clay
rjc...@gmail.com
