[darcs-users] Strange error with darcs mv and add

[S. Günther]

Hi,

yes, I did receive the response, I just didn't have time to
try to reproduce the error during the weekend.
I tried today and wasn't able to. As I explained before
pulling into a fresh repository fixed the error. Even worse,
creating a tarball and working in a copy of the old repository
didn't reproduce the error, too. That made me suspicious and
it turns out that I don't even get the error in the repo which
was the offending one to start with. And I swear I didn't touch
it.
So I think there really must have been something messed up
on my box and I'm incredibly sorry for the unnecessary noise.

Cheers and Apologies
Stephan


On Mon, Jan 5, 2009 at 4:04 AM, Eric Kow <kowey at darcs.net> wrote:
> Hi,
>
> Did you receive Trent's form-response below?  Adding to his comment,
> your darcs show files output may be interesting to have.
>
> Thanks!
>
> Eric
>
> On Sat, Jan 03, 2009 at 13:29:34 +1100, Trent W. Buck wrote:
>> "S. Günther" <h8spawn at googlemail.com> writes:
>>
>> > $ darcs mv ./gsom/lattice.hs ./gsom/node.hs generic/
>> > darcs failed:  There is no file or dir named Gsom/lattice.hs in the
>> > working directory.
>> > although the file is there, as a 'darcs show files' shows [...]
>>
>> What follows is a form response.
>>
>> Thanks for your bug report!  To fix a bug, we need to be able to
>> reproduce it reliably.  That means we need a set of instructions that
>> will, at least for you, ALWAYS cause the bug to appear.
>>
>> Often the easiest way to do this is simply to make the buggy repository
>> publicly available.  That is, so we can "darcs get URL" to get it.  Is
>> there such a URL?
>>
>> It might be that if you "darcs get" the repository, the problem goes
>> away.  In that case, we need an exact copy of the buggy repository
>> (i.e. a tarball or zip file) somewhere we can download.
>>
>> Best of all is if you can reproduce the problem in a brand new
>> repository.  So instead of us having to go through your whole
>> repository, we can just use a set of instructions like
>>
>>     darcs init
>>     touch foo
>>     darcs add foo
>>     darcs record --all --message 'Added foo.' foo
>>     ...
>>
>> that will cause the problem to appear.  This allows us to add those
>> instructions almost verbatim into the bugs/ or tests/ directories in
>> Darcs' source, making our work much easier.
>>
>> Any of this will give us a huge head start on fixing your bug.  It's
>> also helpful if you can send the details to bugs at darcs.net, which will
>> create a bug ticket on http://bugs.darcs.net/ which we (and you!) can
>> use to track the status of the bug.
>>
>> _______________________________________________
>> darcs-users mailing list
>> darcs-users at darcs.net
>> http://lists.osuosl.org/mailman/listinfo/darcs-users
>
> --
> Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
> PGP Key ID: 08AC04F9
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAklg7AsACgkQBUrOwgisBPnyhQCggOV7f2f9cNgzTQvr//tEESP7
> 7agAoO9s+ee2d7zpBAdUG9HrpurEqeyp
> =Nybp
> -----END PGP SIGNATURE-----
>
>