Re: [Duplicity-talk] Errors during test phase of installation.....

[Scott Hannahs]

> On Feb 5, 2017, at 8:28 AM, edgar.soldin--- via Duplicity-talk 
> <address@hidden> wrote:
> 
> On 04.02.2017 00:23, Scott Hannahs via Duplicity-talk wrote:
>> The other big error was that the un-tar of the test files would set file 
>> permissions and owners so that the test user could not delete them.   I set 
>> a note that the testing phase has to run as root.  It shouldn’t but that 
>> seems to be an issue.  If the no-owner no-group flags were set on the untar 
>> command for the test directories it might work.  But that may mess up some 
>> of the tests.
> 
> Scott,
> 
> can you explain this a little bit more detailed? do you mean that untar-ing 
> the duplicity tarball creates files/folders with improper permissions?
> 
> what do those improper persmissions/owner values look like?

No, not the duplicity tar ball, but the testing tar ball which has all sorts of 
weird permissions and dates just to test the functionality of duplicity.  I am 
not sure exactly what the problem is, if I untar the testing tar ball manually 
all the owners are set to that of the user.  But the permissions may be a 
problem during the cleanup part as mentioned by Ken.  I am not sure of the 
exact tar command switches used in the extraction of testifiles.tar.gz.  Let me 
go grep through the testing sources.

The testing is attempted by the non-login user fink-bld as well as the creation 
of the deb file.  However the testing seems to work when the whole thing is run 
at root privilege.

I am also not sure why the large number of open files is required during the 
testing phase.  I run duplicity on large directories daily with the standard 
limits.  It may be the testing routines are keeping file handles open.

-Scott