[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] remove-all-but-n-full needs --force?
From: |
Kenneth Loafman |
Subject: |
Re: [Duplicity-talk] remove-all-but-n-full needs --force? |
Date: |
Thu, 11 Dec 2008 08:48:39 -0600 |
User-agent: |
Thunderbird 2.0.0.18 (X11/20081125) |
Yes, file a support request. I'm leaning more in favor of your 'b'
solution, with the addition that remove- or others will put out a
message to the effect that without --force only a listing will occur.
That plus man page changes should do the trick.
I would hate to change it and have someone that uses the listing aspect
get burned by the change.
...Ken
address@hidden wrote:
> Actually deleting is a serious action and should require an explicit
> 'yes' somewhere.
> I think the general double function (to list only or also to delete) of
> remove-... commands is the real problem here.
>
> 2 solutions possible:
> a) separate the command in two - remove vs. list
> b) document the need to use the --force option (better)
>
> I like b) because it keeps duplicity straight forward and I doublechecked
> http://duplicity.nongnu.org/duplicity.1.html
> where I couldn't find explicit notes on the need of --force for remove &
> cleanup actions. These should be added. Also in the overview at the top
> e.g.
>
> *duplicity cleanup* *[*/options/*]* /target_url [--force]/
>
>
> Also I can't check now but:
> Does duplicity tell the user on listing the obsolete backups of the need
> to use the --force option ?
> I think it did .. but if not it should.
>
> @Ken: want me to file a support request?
>
> .. ede
> --
>> Hi
>>
>> Andrew Kohlsmith (lists) wrote:
>>> Good morning,
>>>
>>> I just noticed that my full backups for the last 6 months aren't
>>> getting deleted, because apparently the remove-all-but-n-full needs
>>> the --force option.
>>>
>>> --force is usually reserved for "you WILL shoot yourself in the foot
>>> if I allow you to do this" type of operations... is it really
>>> necessary to have a "Are you sure [y/N]?" option for this operation?
>>>
>>
>> I stumbled across the same thing a few months ago and had the same
>> question. I agree that it seems odd to have to use a --force flag to
>> delete old backup sets. Having to do so carries the implication that
>> the user is doing something dangerous or wrong and that's generally
>> not the case with routine stale archive removal.
>>
>> Jon
>>
>>
>> _______________________________________________
>> 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