[Bug 58450] Re: Checksum-file error after purging old backups

2007-09-21 Thread Launchpad Janitor
[Expired for backup2l (Ubuntu) because there has been no activity for 60 days.] -- Checksum-file error after purging old backups https://bugs.launchpad.net/bugs/58450 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs

[Bug 58450] Re: Checksum-file error after purging old backups

2007-05-17 Thread alzheimer
Yes, I just tried it again in Ubuntu Server 7.04 and the Bug is still there. Same setup as above. And as I wrote in my first post, the fix is quite simple. From the manual of "sed" it is clear, that the spaces are wrong. So what is to do to remove the two stupid spaces from the package? -- Check

[Bug 58450] Re: Checksum-file error after purging old backups

2007-05-16 Thread William Grant
Does this still occur in Edgy, Feisty or Gutsy? -- Checksum-file error after purging old backups https://bugs.launchpad.net/bugs/58450 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.u

[Bug 58450] Re: Checksum-file error after purging old backups

2006-09-01 Thread alzheimer
my System is a clean Ubuntu-Server installation with nothing more than backup2l installed in VMWare-machine -- Checksum-file error after purging old backups https://launchpad.net/bugs/58450 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu

[Bug 58450] Re: Checksum-file error after purging old backups

2006-09-01 Thread alzheimer
Hi, here is how I produced the bug: mkdir /home/test#the backup-source touch /home/test/test #so we have something to backup mkdir /home/backup #the backup-dir #then we do some backups: for ((i=0;i<10;i++)); do backup2l -c /etc/backup2l.conf.test -b; done #and ver

[Bug 58450] Re: Checksum-file error after purging old backups

2006-09-01 Thread Andy Price
Thanks for your bug report. I'm having trouble reproducing this bug, please could you give an example of the corrupted checksum file? Also, what backup ID numbers did your backups get to before they started getting corrupted... did it have to go to -> 1 or were they low numbers? Thanks. *