On Sat, May 26, 2007 at 01:18:52PM +0200, Daniel Baumann wrote:
> Marc Haber wrote:
> > rdiff-backup being written in pythion does not make backporting and
> > forwardporting any easier.
> 
> I beg to differ.
> 
> Backporting rdiff-backup is easy and was done by me for the
> sarge-backports suite on backports.org in the past.

Backporting python apps is always a terrible pain caused by the
horrible mess the Debian python packages are.

> > I would like to ask to have multiple rdiff-backup packages in Debian
> > so that interoperability between different Debian OSses and even
> > between non-Debian and Debian OSses can be achieved. Not even being
> > compatible between Debian stable and unstable is not acceptable, IMO.
> 
> As you can read in the BTS of rdiff-backup, I went with the development
> version to not have to keep a pile of patches arround which got applied
> in the development tree.

I do not think that is acceptable for a critical application as a
backup app.

>  Once 1.2 branch will be released, I'll stick with that branch on
>  unstable/testing (as said on the BTS too).

Which will make Debian unstable incompatible once more with Debian
stable.

> Unfortunately, upstream did not manage to open stable 1.2 branch in the
> meanwhile.

What is the current status of upstream development?

> > Please advise how you intend to address this issue which comes up
> > repeatedly once in a while.
> 
> As said on the BTS and pointed out above again, my 'advise' is to use
> the same rdiff-backup version on the client and the server; and to use
> backports in case any of the two machines are running stable.

I am unsure whether this is acceptable.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 3221 2323190


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to