Backup Central

Version: rdiff-backup 0.13.3

Command line:
rdiff-backup -r 2D backup::/backups/xxx/xxx001/home/acl/.profile
/home/acl/restored-profile

Error (last part of stack):
File
"/home/PUB/debian-ida/pool/sid-jones/rdiff-backup/rdiff-backup-0.13.3.jgoe
rzen/debian/rdiff-backup/usr/lib/python2.2/site-packages/rdiff_backup/conn
ection.py", line 351, in reval AssertionError: (('acl', '.profile',
'Application Data', 'Macromedia', 'Flash Player', 'macromedia.com',
'support', 'flashplayer', 'sys'), ('acl', '.profile', 'Application Data',
'Macromedia', 'Flash Player', 'macromedia.com', 'support', 'flashplayer',
'sys', '#bbc.co.uk', 'settings.sol'))

I don't understand the (very long) path to connection.py:

# which rdiff-backup
/usr/bin/rdiff-backup
# locate connection.py
/usr/lib/python2.2/site-packages/rdiff_backup/connection.py
/usr/lib/python2.2/site-packages/rdiff_backup/connection.pyc
/usr/lib/python2.2/site-packages/rdiff_backup/connection.pyo
#

Can anyone shed any light on this?

Thanks
Keith

On Tue, 1 Jun 2004 22:19:40 +0100
Keith Edmunds <keith < at > midnighthax.com> wrote:

Command line:
rdiff-backup -r 2D backup::/backups/xxx/xxx001/home/acl/.profile
/home/acl/restored-profile

I should add that I managed to restore the directory by logging onto the
backup server and running it locally.

Keith

Keith Edmunds <keith < at > midnighthax.com>
wrote the following on Tue, 1 Jun 2004 22:19:40 +0100
Version: rdiff-backup 0.13.3

Command line:
rdiff-backup -r 2D backup::/backups/xxx/xxx001/home/acl/.profile
/home/acl/restored-profile

Error (last part of stack):
File
"/home/PUB/debian-ida/pool/sid-jones/rdiff-backup/rdiff-backup-0.13.3.jgoe
rzen/debian/rdiff-backup/usr/lib/python2.2/site-packages/rdiff_backup/conn
ection.py", line 351, in reval AssertionError: (('acl', '.profile',
'Application Data', 'Macromedia', 'Flash Player', 'macromedia.com',
'support', 'flashplayer', 'sys'), ('acl', '.profile', 'Application Data',
'Macromedia', 'Flash Player', 'macromedia.com', 'support', 'flashplayer',
'sys', '#bbc.co.uk', 'settings.sol'))

I think this may be the same bug that has just been fixed in CVS and
0.12.7. I hope to release 0.13.5 soon.

I don't understand the (very long) path to connection.py:

# which rdiff-backup
/usr/bin/rdiff-backup
# locate connection.py
/usr/lib/python2.2/site-packages/rdiff_backup/connection.py
/usr/lib/python2.2/site-packages/rdiff_backup/connection.pyc
/usr/lib/python2.2/site-packages/rdiff_backup/connection.pyo
#

Can anyone shed any light on this?

Here's a theory: John Goerzen probably built the binary deb that you
are using, and that was the path to connection.py on his machine, when
it was first compiled to connection.pyo, which is what python executes
from.


--
Ben Escoto

Keith Edmunds <keith < at > midnighthax.com>

I don't understand the (very long) path to connection.py:


Can anyone shed any light on this?

Here's a theory: John Goerzen probably built the binary deb that you
are using, and that was the path to connection.py on his machine, when
it was first compiled to connection.pyo, which is what python executes
from.


--
Ben Escoto

from what I have seen, if you delete the .pyo files, they get rebuilt next
time rdiff-backup is run. Then they have the correct path to your local
.py files. Perhaps the debian package should have no .pyo files, then
everyone would have the correct (shorter) path in their tracebacks :)

dave

"David Kempe" <dave < at > solutionsfirst.com.au>
wrote the following on Wed, 2 Jun 2004 09:31:28 +1000 (EST)

from what I have seen, if you delete the .pyo files, they get
rebuilt next time rdiff-backup is run. Then they have the correct
path to your local .py files. Perhaps the debian package should have
no .pyo files, then everyone would have the correct (shorter) path
in their tracebacks :)

This is only true if you run as root. If no .pyc/.pyo files were
included, then ordinary users would have to wait for rdiff-backup to
"compile" over and over again until root ran it once.


--
Ben Escoto