[Expired for rdiff-backup (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: rdiff-backup (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Hello!
The new rdiff-backup 2.0 (written in Python 3) has recently been
released. Please check out https://github.com/rdiff-backup/rdiff-backup
and contribute in this open source project.
This bug is unlikely to apply anymore to latest rdiff-backup 2.0, so it
will be closed unless you want to hel
** Changed in: rdiff-backup (Ubuntu)
Status: Incomplete => In Progress
--
rdiff-backup --list-increments does not distinguish between error conditions
https://bugs.launchpad.net/bugs/128244
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Still a problem on Intrepid?
--
rdiff-backup --list-increments does not distinguish between error conditions
https://bugs.launchpad.net/bugs/128244
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
This currently still happens in hardy:
$ rdiff-backup --list-increments /tmp/ttt
Fatal Error: Previous backup to /tmp/ttt seems to have failed.
Rerun rdiff-backup with --check-destination-dir option to revert directory to
state before unsuccessful session.
$ echo $?
1
$ rdiff-backup --list-increm
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
rdiff-backup --l
Nick - have you had an opportunity to test the proposed changes? They
don't seem to have made it into the latest release as far as I can tell
and it sounds like this is something you might want in Hardy.
** Changed in: rdiff-backup (Ubuntu)
Status: Fix Released => Incomplete
--
rdiff-bac
Marking fix released per above comment. Current version is 1.1.14-1.
** Changed in: rdiff-backup (Ubuntu)
Status: Incomplete => Fix Released
--
rdiff-backup --list-increments does not distinguish between error conditions
https://bugs.launchpad.net/bugs/128244
You received this bug notific
This was fixed in version 1.1.14, currently on gutsy ?
** Changed in: rdiff-backup (Ubuntu)
Status: New => Incomplete
--
rdiff-backup --list-increments does not distinguish between error conditions
https://bugs.launchpad.net/bugs/128244
You received this bug notification because you are a
Nick,
Have you gotten a chance to test my fix from the first comment? I am
currently blocking the 1.1.13 release until you confirm.
Thanks,
Andrew
--
rdiff-backup --list-increments does not distinguish between error conditions
https://bugs.launchpad.net/bugs/128244
You received this bug notific
Nick, thanks for testing this.
If I read your comment correctly, you're looking for a wider range of
exit status codes, correct? As far as I can tell, rdiff-backup currently
exits with either 0 for no error or 1 for error occurred. It certainly
seems like getting some more information would be a g
owsla:
> This is a good point about the two different behaviors and I agree
> that --list-increment-sizes is more sensible.
>
> I think the correct fix is to simply remove the call to
> restore_check_backup_dir() in the ListIncrements(rp) function in
> Main.py. If you remove that line, does the bo
Hi Nick,
This is a good point about the two different behaviors and I agree that
--list-increment-sizes is more sensible.
I think the correct fix is to simply remove the call to
restore_check_backup_dir() in the ListIncrements(rp) function in
Main.py. If you remove that line, does the bothersome
13 matches
Mail list logo
