Re: [Duplicity-talk] FileobjHooked instance has no attribute 'name'

[edgar . soldin]

On 15.04.2011 10:49, Wolfgang Rohdewald wrote:
> On Freitag 15 April 2011, address@hidden wrote:
>> On 15.04.2011 08:42, Wolfgang Rohdewald wrote:
>>> is there a good reason why you top quoted? I don't so
>>> what you quoted from my mail will not appear here
>>
>> no, i didn't
> 
> your answer was above my text.

observed correctly, and answered correctly as well. no, i did not have a good 
reason.

> 
>> so you actually tried to do a new full and observed if the
>> error persists?
> 
> No.

ok.

> This bug report is not about any problem with saving or
> restoring backups. It is about duplicity not being able
> to correctly show an error message and thusly obscuring
> what really happened.

sorry, didn't understand this from your first mail.

> The problem is that whatever error message duplicity is 
> trying to show at line 891 will never be shown because
> the generation of the error message is broken.
> 
> self.fileobj has no attribute 'name' and using it 
> for generating the error message is wrong.
> 

hmm, can you supply a patched tree on launchpad for this? if not, i could do it 
this weekend.

> so duplicity dies while preparing the actual error
> message - which is lost forever.
> 
> only after fixing this, we will have a chance to
> find out what error really happened. Both in my
> case and in ticket 2743. 

understood.
 
 
> The recipe I gave is a way force the error in
> generating the error message: Force 
> duplicity to take this code path (syncing metadata)
> and print self.fileobj.name - even if there was
> no error.
> 
> That will raise the same exception:
> 
> AttributeError: FileobjHooked instance has no attribute 'name'

ok.


..ede/duply.net