----- Forwarded message from  -----

Date: Sun, 23 Apr 2006 07:14:16 -0700
To: martin f krafft <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#358431: wrong programme outcome when source and destination 
don't exist
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.11+cvs20060126
Status: RO

On Wed, Mar 22, 2006 at 07:31:51PM +0100, martin f krafft wrote:
> Package: unison
> Version: 2.13.16-5
> Severity: normal
> 
>   piper:/tmp> ls foo bar
>   ls: foo: No such file or directory
>   ls: bar: No such file or directory
> 
>   piper:/tmp> unison foo bar
>   Contacting server...
>   Looking for changes
>   Warning: No archive files were found for these roots.  This can
>   happen either because this is the first time you have synchronized
>   these roots, or because you have upgraded Unison to a new version
>   with a different archive format.  
> 
>   Update detection may take a while on this run if the replicas are
>   large.
> 
>   Unison will assume that the 'last synchronized state' of both
>   replicas was completely empty.  This means that any files that are
>   different will be reported as conflicts, and any files that exist
>   only on one replica will be judged as new and propagated to the
>   other replica. If the two replicas are identical, then no changes
>   will be reported.
>   Press return to continue.[<spc>]  Reconciling changes
>   Nothing to do: replicas have not changed since last sync.
> 
> Surely they haven't changed. They don't exist.
> 

Hello,

I am not sure it is a really "normal" bug... It does nothing when
nothing has to be done.... (well, it runs even if nothing has to be
done, but it is not a real bug).

Do you really want to call this "bug" ?

Kind regard
Sylvain Le Gall

ps: i have almost no internet connection at this time, please don't
expect a correction soon.


----- End forwarded message -----



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to