darcs check

If a repository passes 'darcs check', does that mean there
is nothing wrong with
it ? By "wrong" I mean anything that could cause
inconsistency.

To put this another way: if darcs shows inconsistent
behaviour on a repo, and
that repo passes 'darcs check', does this mean the problem
lies in darcs itself
(rather than the repo) ? Would this be true even if the repo
had been manually
tinkered with (prior to passing 'darcs check') in an
unwholesome way ?

Tim
_______________________________________________
darcs-users mailing list
darcs-usersdarcs.net

http://lists.osuosl.org/mailman/listinfo/darcs-users

On Thu, Jan 04, 2007 at 14:48:51 -0800, trbcategorical.net wrote:
> If a repository passes 'darcs check', does that mean
there is nothing wrong with
> it ? By "wrong" I mean anything that could
cause inconsistency.

Unless I am mistaken, darcs check merely attempts to apply
all patches
from scratch.  If nothing goes wrong, it is happy.

> To put this another way: if darcs shows inconsistent
behaviour on a repo, and
> that repo passes 'darcs check', does this mean the
problem lies in darcs itself
> (rather than the repo) ? Would this be true even if the
repo had been manually
> tinkered with (prior to passing 'darcs check') in an
unwholesome way ?

That does smell like a bug... but I suppose it depends on
what you mean
by inconsistent.

-- 
Eric Kow                     http://www.loria.fr/~kow
PGP Key ID: 08AC04F9         Merci de corriger mon français.
_______________________________________________
darcs-users mailing list
darcs-usersdarcs.net

http://lists.osuosl.org/mailman/listinfo/darcs-users

> I mean self-inconsistent (e.g. the behaviour I
described in my
> message about Issue365, makes a repository invent
previously
> non-existent pending changes). Suppose a repository had
been
> tampered with in a Byzantine way, but subsequently
passed 'darcs
> check'. It could well have been modified, and might no
longer be
> consistent with other repositories, but I would hope
that it would
> still be self-consistent (by virtue of having passed
'darcs check').

Darcs check verifies that the sequence of patches since the
last
checkpoint can be applied, and that the result matches the
pristine
cache.

Darcs check --complete does the same since the origin of
time (which
is on a Wednesday).

On a --no-pristine-cache repo, the result is of course not
compared
against the pristine cache.

I do see a few contrived ways of making a repository that
passes
check, but behaves incoherently when patches are commutted. 
However,
that's not something that's likely to happen by accident.

                                        Juliusz
_______________________________________________
darcs-users mailing list
darcs-usersdarcs.net

http://lists.osuosl.org/mailman/listinfo/darcs-users

Juliusz Chroboczek writes:
 > > I mean self-inconsistent (e.g. the behaviour I
described in my
 > > message about Issue365, makes a repository invent
previously
 > > non-existent pending changes). Suppose a
repository had been
 > > tampered with in a Byzantine way, but
subsequently passed 'darcs
 > > check'. It could well have been modified, and
might no longer be
 > > consistent with other repositories, but I would
hope that it would
 > > still be self-consistent (by virtue of having
passed 'darcs check').
 > 
 > Darcs check verifies that the sequence of patches
since the last
 > checkpoint can be applied, and that the result matches
the pristine
 > cache.

Perhaps it should also check that the result of applying the
sequence of patches
does not include a non-empty set of pending changes. I have
a repo where pulling
all its patches (into a fresh repo) produces spurious
pending changes, even
though the repos pass 'darcs check'

Tim
_______________________________________________
darcs-users mailing list
darcs-usersdarcs.net

http://lists.osuosl.org/mailman/listinfo/darcs-users

On Mon, Jan 15, 2007 at 04:39:49PM -0800, trbcategorical.net wrote:
> Juliusz Chroboczek writes:
>  > > I mean self-inconsistent (e.g. the behaviour
I described in my
>  > > message about Issue365, makes a repository
invent previously
>  > > non-existent pending changes). Suppose a
repository had been
>  > > tampered with in a Byzantine way, but
subsequently passed 'darcs
>  > > check'. It could well have been modified,
and might no longer be
>  > > consistent with other repositories, but I
would hope that it would
>  > > still be self-consistent (by virtue of
having passed 'darcs check').
>  > 
>  > Darcs check verifies that the sequence of patches
since the last
>  > checkpoint can be applied, and that the result
matches the pristine
>  > cache.
> 
> Perhaps it should also check that the result of
applying the sequence of patches
> does not include a non-empty set of pending changes. I
have a repo where pulling
> all its patches (into a fresh repo) produces spurious
pending changes, even
> though the repos pass 'darcs check'

Oh, most likely that just means that you've got a conflict. 
You could
verify this by running darcs revert -a (assuming you've got
no interesting
unrecorded changes) followed by darcs resolve.  
-- 
David Roundy
http://www.darcs.net
_______________________________________________
darcs-users mailing list
darcs-usersdarcs.net

http://lists.osuosl.org/mailman/listinfo/darcs-users

On Sat, Jan 13, 2007 at 11:51:58AM -0800, trbcategorical.net wrote:
> BTW, I subscribed to this list before sending my two
messages to it, but have
> not received any messages from the list, except for a
"welcome to the list"
> message on 2007-1-4. I only received your message
because you CC'ed it to me.
> Neither can I follow the discussion (if any) in the
list archives, since there
> is no archive yet for January.

Almost certainly the trouble is that we moved the mailing
list server, but
didn't update the link on the webpage.  Follow the link at
the bottom of
this email, and sign up again.  Sorry about that! (And I've
sent in a patch
to the web page...)
-- 
David Roundy
http://www.darcs.net
_______________________________________________
darcs-users mailing list
darcs-usersdarcs.net

http://lists.osuosl.org/mailman/listinfo/darcs-users