David Creelman <creelman.da...@gmail.com> writes: > Hi Rob, Robert, > More details. > lsattr on the original file gives > -------------e-- /home/davidc/#.fetchmailrc# > > bup ls -l of the problem file gives > -rwx------ davidc/davidc 833 2015-01-20 23:42 > home-dir/latest/home/davidc/#.fetchmailrc#
> lsattr of the original file is > -------------e-- /home/davidc/#mredauto#1# > > bup ls -l of the file stored in bup is > bup ls -l home-dir/latest/home/davidc/#mredauto#1# > -rw-r--r-- davidc/davidc 7790 2014-01-07 15:43 > home-dir/latest/home/davidc/#mredauto#1# This is all (currently) myterious. I don't see any reason you should be having trouble, but we've had weirdness with attr before. Maybe it's more of the same? What I'm wondering is if someone (maybe us) is getting the attr value handling wrong (again). If you're up for it, you might try adding a print statement like this to metadata.py in _apply_linux_attr_rec(): else: print >> sys.stderr, 'bad chattr', repr((path, self.linux_attr)) raise And then re-run the restore so we can see the linux_attr value when it fails. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org