[Duplicity-talk] Error 30 TypeError: bad operand type for unary +: 'str'

[Bonvicini, Alessandro]

Hi all, can someone explain me what kind of error is the following and what can 
I do to correct?

Duplicity clean on the archive does not report any error or problem that need 
to be fixed.

My windows client use the --archive-dir directive.

Let me know if you need more infoes

Thank a lot in advance
Alex 



WARNING 2
. Warning, found the following orphaned signature files:
. duplicity-new-signatures.20090403T070116Z.to.20090403T235115Z.sigtar.gz
. duplicity-new-signatures.20090403T235115Z.to.20090408T070551Z.sigtar.gz

INFO 1
. Using temporary directory /tmp/duplicity-Y9ftDC-tempdir

ERROR 30 TypeError
. Traceback (most recent call last):
.   File "/usr/bin/duplicity", line 743, in <module>
.     with_tempdir(main)
.   File "/usr/bin/duplicity", line 736, in with_tempdir
.     fn()
.   File "/usr/bin/duplicity", line 655, in main
.     globals.archive_dir).set_values()
.   File "/usr/lib/python2.5/site-packages/duplicity/collections.py", line 557, 
in set_values
.     self.warn(sig_chain_warning)
.   File "/usr/lib/python2.5/site-packages/duplicity/collections.py", line 626, 
in warn
.     + "\n" + "\n".join(self.other_sig_names),
. TypeError: bad operand type for unary +: 'str'
.

-----Messaggio originale-----
Da: address@hidden [mailto:address@hidden Per conto di Kenneth Loafman
Inviato: mercoledì 8 aprile 2009 19.30
A: Discussion of the backup program duplicity
Oggetto: Re: [Duplicity-talk] Duplicity crashes on locked files (windows)

Georg Lutz wrote:
>> I'll agree with that.  Do they block all OSS sites, or just some?
>>
> 
> They don't block especially OSS sites. They block sites where 
> "software can be downloaded". And because downloaded software can 
> cause harm it is evil to do so. Interestingly sourceforge.net is not 
> blocked, so its not very consistent...
> 
> At one of my former working places internet ("WWW" in manager speak) 
> was cut off completely as default setting and one have to argue why he 
> would need internet access at all. This was the company wide IT 
> policy. For 1 MB traffic my departement had to pay 0,5 EUR to the IT 
> departement. The same guys also completely blocked zip files in emails for 
> "security reasons"
> but let through powerpoint presentations. As you can imagine it was 
> not funny to work there... Compared to that the current situation is 
> like in paradise...

Been there, done that.  One of the places I was at was paying my base rate plus 
a couple of extras (Windows, at their site), but the security there was so 
strict I had to ask permission for everything, even when the job I was tasked 
with had to access everything.  I figure I made at least 30 percent more on 
that job just because of security delays.

>> I'm going to have to dig into this a bit further.  It looks like 
>> Windows will let you open the file, but then not access it, not good.  
>> I'll have to apply the same checks further into the process.  I'll 
>> open a bug report on this.  For now, just --exclude=**.pst and back 
>> it up to a different file extension before duplicity.
>>
> 
> I just reproduced it and attached a logfile which comes out of 
> processmon, a tool like strace on windows, formerly developed by 
> sysinternals (now M$). I attached both - CVS text file and the native PML 
> format.
> 
> It seems like you explained - one can open the file but not access it. 
> BTW the crash can also be reproduced with opened Excel or OOWrite files.

This patch seems to work for me with OOWrite files.  Care to give it a try with 
Outlook files?

...Ken


Nessun virus nel messaggio in arrivo.
Controllato da AVG - www.avg.com
Versione: 8.0.238 / Database dei virus: 270.11.46/2046 -  Data di rilascio: 
04/08/09 05:53:00