duplicity-talk
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] sftp: "File size can't be validated..." warning

From: edgar . soldin
Subject: Re: [Duplicity-talk] sftp: "File size can't be validated..." warning
Date: Sat, 30 Mar 2024 12:24:19 +0100
User-agent: Mozilla Thunderbird 
hey,

i agree, right now it just unsettles users, albeit all is as it used to be.

@Ken: what do you mean by "Things like sftp and friends manage validation on their 
own." ? i am not awarte of any such functionality.

sunny regards ..ede

On 29.03.2024 15:44, Kenneth Loafman via Duplicity-talk wrote:

Hi Thomas,

I think that warning should be removed completely.  We know that some backends 
do not have full capabilities, except for get, put, delete and list.  Things 
like sftp and friends manage validation on their own.

...Thanks,
...Ken


On Thu, Mar 28, 2024 at 12:55 PM Dummy Schmu <all@schmu.net 
<mailto:all@schmu.net>> wrote:

    __

    Hi Ken,

    I think it is not about the warning message, but the place were we do it. 
The current implementation is kind of out of band, which makes it hard to 
determin what's the best for the selected backend.

    I think each backend on its own should decide, if a validation after upload 
make sense or if the protocol itself has enough logic to raise issues.

    Bye

       Thomas

    Am 21.03.24 um 20:55 schrieb Kenneth Loafman:

    Hi,

    This should only affect program based backends, not the web based backends, 
so when programs like lftp, sftp, scp, ssh, rsync, etc. are accessed they do 
their own validation.

    We probably need to discuss the need for such a message.

    ...Thanks,
    ...Ken


    On Thu, Mar 21, 2024 at 1:26 PM Thomas Laubrock via Duplicity-talk 
<duplicity-talk@nongnu.org <mailto:duplicity-talk@nongnu.org>> wrote:

        Hi Nuno,

        This is by intention, because other back ends validate the size after 
transferring a file. This message doesn't mean it is technically not possible, 
but not implemented in the backend. This is not a change in functionality, but 
as I touched the code part, I thought we should make users aware of. May be the 
wording could be more clear.

        I am open for suggestions.

        Bye
        Thomas


        On 21 March 2024 17:51:13 CET, Nuno Teixeira via Duplicity-talk 
<duplicity-talk@nongnu.org <mailto:duplicity-talk@nongnu.org>> wrote:

            Hello all, Using --progress I'm getting warning bellow. Curious if 
this related to sftp backend or sftp server. Thanks, Nuno
            
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
            File size can't be validated, because of missing capabilities of the 
backend. Please verify the backup separately. 24.2GB 01:16:58 [11.8MB/s] 
[======> ] 15% ETA 4h 7min
            
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
            Duplicity-talk mailing list Duplicity-talk@nongnu.org 
<mailto:Duplicity-talk@nongnu.org> 
https://lists.nongnu.org/mailman/listinfo/duplicity-talk 
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk>

        _______________________________________________
        Duplicity-talk mailing list
        Duplicity-talk@nongnu.org <mailto:Duplicity-talk@nongnu.org>
        https://lists.nongnu.org/mailman/listinfo/duplicity-talk 
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk>



_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
reply via email to
[Prev in Thread] Current Thread [Next in Thread]