Re: [Duplicity-talk] Duplicity bug report: crash if the system date is wrong

[Kenneth Loafman]

I have to agree there.  Doing a search for 'assert' yields 170 hits in
duplicity sources, and of course another 300 or so in unit test code.
The 170 in the sources should be replaced by real error messages in a
fair number of cases.  A lot are valid asserts.

I've started working on them as I see them, but a more practical
approach would be to fix the ones that are actually hit in use, then
tackle the others.

...Ken

address@hidden wrote:
> overall .. this is something where duplicity can really improve :) ... ede
> -- 
>>> here's the tail of the log (this one would be huge and I would have
>>> had to comb through it to see if propietary info was in there). Let me
>>> know if you need other portions:
>>>     
>>
>> I think it's questionable whether this can even be considered a
>> problem. A backup tool already kind of depends on proper time of day,
>> and in this case Amazon is trying to cause early failure by making
>> these sanity checks and failing the request.
>>
>> I can see that one might want to treat this particular problem and
>> give a much more user friendly error message. However other than that,
>> is there an actual problem? If I'm not misunderstanding anything, the
>> user-friendlyness seems to be the concern here.
>>
>>  
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>   
> 
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>

signature.asc
Description: OpenPGP digital signature