Hi Eric,
On Thu, April 30, 2020 1:32 pm, EricZolf wrote:
> Hi,
>
> let me perhaps intervene and have everybody calm down a bit.
>
> Frank is only the messenger and doesn't make the rules of Fedora, so
> please don't shoot him.
>
> Derek, you might be correct that we will see Python 2 for decades,
> nothing lives longer than zombies (see IBM and mainframes), but the fact
> that Python 2 will not get anymore security and bug fixes from the
> Python project is also a fact (meaning each distribution is on its own,
> and might or not do its job), so we should all work towards getting
> everybody off it asap _and_ organize a smooth transition for the
> rdiff-users.
>
> If we agree on the objectives, let's come back to the actual topic, on
> how to make this real. I must honestly say that I lost sight of where we
> stand, as the discussion became heated.
>
> If someone could summarize what is already granted as being possible and
> what not, that would help.
Honestly I don't know if we've agreed on any objectives. I can state what
mine is, which I hope is somewhat non-controversial:
* Ensure that someone installing a modern OS can continue to backup
existing servers running older software (e.g. 1.2.8), with the assumption
that the older software cannot be upgraded.
That's my objective. I see two ways to do this:
1) Get an rdiff-backup-{2/3} that can talk to rdiff-backup 1.2.8
2) Supply both rdiff-backup-2 and rdiff-backup1 simultaneously as OS
Packages, possibly with some glue to detect the wire format and
automatically switch between them.
Honestly I'd prefer #1, but can live with #2. Is there another approach
to achieve the objective?
> Thanks, Eric
-derek
--
Derek Atkins 617-623-3745
[email protected] www.ihtfp.com
Computer and Internet Security Consultant
