Re: Version weirdness

[Robert Nichols]

OK, I found a directory
    /usr/lib64/python3.6/site-packages/rdiff_backup-2.2.0-py3.6.egg-info
that apparently got left over from the multiple reinstalls/downgrades/upgrades 
I've been doing trying to track down issues. Getting rid of that directory 
fixes the problem.

Apparently Python isn't particular about whether it finds the 2.2.0 or 2.2.2 
version of that directory and just uses whichever it runs across first.

--
Bob Nichols     "NOSPAM" is really part of my email address.
                Do NOT delete it.

On 1/3/23 3:24 PM, EricZolf wrote:
> Hi,
>
> it might make sense to check what 'pip list' tells you, once called as root, 
> once as normal user. Calling 'pip remove rdiff-backup' (without pressing y) 
> would even tell you where the files are. Also, calling 'hash -r' makes sure 
> that you're not using the wrong binary.
>
> KR. Eric
>
> On January 3, 2023 6:53:22 PM UTC, Alvin Starr via Any discussion of rdiff-backup 
> <rdiff-backup-users@nongnu.org> wrote:
> > On 2023-01-03 13:49, Robert Nichols wrote:
> > > On 1/3/23 11:44 AM, Robert Nichols wrote:
> > > > I have one rdiff-backup installation for which "rdiff-backup --version" reports "rdiff-backup 
> > > > 2.2.0" and another which reports "rdiff-backup 2.2.2". The problem:
> > > >
> > > >       1. On both systems, "rpm -q rdiff-backup" reports 
> > > > "rdiff-backup-2.2.2-1.el8.x86_64".
> > > >       2. On both systems, "rpm -V rdiff-backup" does not detect any changes in 
> > > > the installed files.
> > > >       3. The md5sum checksums for all of the files listed by "rpm -ql 
> > > > rdiff-backup" match between systems.
> > > >       4. Both systems are running Rocky Linux 8.7, fully updated.
> > > >
> > > > The system reporting "2.2.2" is a virtual machine. The one reporting "2.2.0" is 
> > > > a new installation running on the bare iron.
> > > >
> > > > If you have any idea about what might be happening, I'd like to hear about it. 
> > > > If you have no clue, welcome to the club.
> > >
> > > Ahh yes, I neglected to mention that on both systems "which rdiff-backup" reports 
> > > "/usr/bin/rdiff-backup", and explicitly running "/usr/bin/rdiff-backup --version" reports 
> > > the same as what I posted above.
> > Well if rdiff-backup --version responds with a result different from 
> > /usr/bin/rdiff-backup --version then there is another rdiff-backup installed 
> > somewhere.
> > Check your bash aliases.