For what it's worth, I was able to resolve this (for now) by updating CPAN
itself. I noticed when running certain commands that it complained that CPAN
was at version 1.x and version 2.28 was available. It suggested running:
install CPAN
reload cpan
But those are clearly not bash commands. They need to be run in the CPAN shell:
# perl -MCPAN -e shell
After completing, I again ran the following as the backuppc user and it
reported the correct version:
$ /usr/bin/perl -e 'use BackupPC::XS; print("$BackupPC::XS::VERSION\n")'
0.62
This is likely not the best way to resolve a mismatched cpan module version but
it does appear to have worked for me, for now. I promise not to complain next
time an update comes through and I end up having to rebuild from .iso 🙂
________________________________
From: Craig Barratt via BackupPC-users <[email protected]>
Sent: Thursday, June 25, 2020 5:43 PM
To: General list for user discussion, questions and support
<[email protected]>
Cc: Craig Barratt <[email protected]>
Subject: Re: [BackupPC-users] [BackupPC-devel] BackupPC 4.4.0 released
You can install the perl module Module::Path to find the path for a module.
After installing, do this:
perl -e 'use Module::Path "module_path";
print(module_path("BackupPC::XS")."\n");'
Example output:
/usr/local/lib/x86_64-linux-gnu/perl/5.26.1/BackupPC/XS.pm
Now try as root and the BackupPC user to see the difference. Does the BackupPC
user have permission to access the version root uses?
You can also print the module search path with:
perl -e 'print join("\n", @INC),"\n"'
Does that differ between root and the BackupPC user?
Craig
On Thu, Jun 25, 2020 at 9:48 AM Les Mikesell
<[email protected]<mailto:[email protected]>> wrote:
> The system got itself into this state from a standard yum update.
That's why you want to stick to all packaged modules whenever
possible. Over time, dependencies can change and the packaged
versions will update together. You can probably update a cpan module
to the correct version manually but you need to track all the version
dependencies yourself. There are some different approaches to
removing modules: https://www.perlmonks.org/?node_id=1134981
_______________________________________________
BackupPC-users mailing list
[email protected]<mailto:[email protected]>
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
