** Changed in: rdiff-backup (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/128242
Title:
minorest revision number change breaks network protocol
Yeah, I'll mark this report as "Fix committed". This bug was to a large
part the result of Ubuntu including rdiff-backup versions from its
development branch. This most likely won't happen in the future since
a) We are aware of the problem.
b) Debian Unstable will contain version from the stable b
Well, so long as he's clear as to rdiff-backup's use of early Linux
kernel version number schemes, I'd say that's good enough to mark this
as "fix committed" :)
--
minorest revision number change breaks network protocol
https://bugs.launchpad.net/bugs/128242
You received this bug notification be
Seems like the new Debian Maintainer, Carl Chenet, agrees about sticking
to stable releases of rdiff-backup. To quote him directly: "I'll stick
with the stable branch. I don't have any interest in a development
version."
--
minorest revision number change breaks network protocol
https://bugs.laun
@Nick: Never got any response on my mail to the Debian Maintainer. On
the other hand, rdiff-backup has gotten a new Debain maintainer since
then, so I guess I can send him the same question.
--
minorest revision number change breaks network protocol
https://bugs.launchpad.net/bugs/128242
You rece
How did the Debian maintainer react to this information about revision
numbers? Do we have a commitment to package only stable releases under
the 'rdiff-backup' package name? If so, then perhaps we can mark this
as "Fix Released" in Ubuntu, since imports will never again grab a
development releas
@Andreas,
Worked for me too. Thank you!
--
minorest revision number change breaks network protocol
https://bugs.launchpad.net/bugs/128242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
@Andreas,
Thanks - that should do the trick!
--
minorest revision number change breaks network protocol
https://bugs.launchpad.net/bugs/128242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
@Alan: Well, perhaps this PPA (which I maintain) can be of some use, as
a workaround?
https://launchpad.net/~rdiff-backup-pkgs/+archive/ppa
--
minorest revision number change breaks network protocol
https://bugs.launchpad.net/bugs/128242
You received this bug notification because you are a membe
I tried - albeit quite briefly - installing the Intrepid version of
rdiff-backup using APT-Pinning onto Jaunty but due to it depending on <
Python2.6 it failed.
This is a real headache. It means effectively that you can't use rdiff-
backup between releases of Ubuntu from now on. I guess the minor
Well, not sure what the proper solution is for current/old version of
Ubuntu
But since Jaunty includes a rdiff-backup version from its stable branch
(now 1.2.x) I'd say the strategy for the near future should be to make
sure we don't yet again take in versions from the development branch
(now 1.3.
Would using an APT-Pinning scheme be a good way to work around this?
--
minorest revision number change breaks network protocol
https://bugs.launchpad.net/bugs/128242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
I have just encountered this problem after upgrading a desktop machine
to Jaunty yesterday. My server (which manages the backups and is running
Intrepid 8.10) now fails because the versions are too far out I assume.
Here's the error log when running from the CLI:
back...@vimes:~$ rdiff-backup -v9
I use duplicity as a workaround.
On 1/20/09, Tommy Williams wrote:
> Besides upgrading my production server, or using a earlier version of
> rdiff-backup on other machines, are there any other work arounds for
> getting rdiff-backup 1.1.12 or better onto dapper server.
>
> --
> minorest revision
Besides upgrading my production server, or using a earlier version of
rdiff-backup on other machines, are there any other work arounds for
getting rdiff-backup 1.1.12 or better onto dapper server.
--
minorest revision number change breaks network protocol
https://bugs.launchpad.net/bugs/128242
Yo
I (think) I encountered this (from gusty to hardy), and I did not get a
tidy message, just a traceback.
--
minorest revision number change breaks network protocol
https://bugs.launchpad.net/bugs/128242
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
owsla, I appreciate the need for protocol changes, and appreciate that
the unstable version is meant to be a moving target. The problem as I
see it is that Ubuntu does not package the stable version of rdiff-
backup, and that the unstable versions are not explicitly packaged with
protocol versions
We can't directly backport 1.1.12 to Dapper due to Python policy
changes, but it should be OK for Edgy and Feisty. Alternatively, we
could do something like what unison does and have an rdiff-backup-1.1.5
in Gutsy.
--
minorest revision number change breaks network protocol
https://bugs.launchpad.
** Changed in: rdiff-backup (Debian)
Status: New => Fix Released
--
minorest revision number change breaks network protocol
https://bugs.launchpad.net/bugs/128242
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
Unfortunately, this protocol change was necessary to fix a long-standing
and troublesome bug. These are the kind of changes that can happen in a
development branch, and that is why it is highly recommended that you
run the same version on all machines (rdiff-backup checks for this and
prints a warn
** Changed in: rdiff-backup (Debian)
Status: Unknown => New
--
minorest revision number change breaks network protocol
https://bugs.launchpad.net/bugs/128242
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
I got hit by this when I upgraded this morning. I might try to backport
1.1.12 to Dapper for now, but that's not an ideal fix.
** Changed in: rdiff-backup (Ubuntu)
Importance: Undecided => High
Status: New => Confirmed
** Bug watch added: Debian Bug tracker #434627
http://bugs.debian
22 matches
Mail list logo
