I have no clue what the darcs bug is. I thought the testsuite had no conflicts, and hence would not get "commuting_patch" errors.

However, to get you un-wedged I've put an update-to-date tarball of the testsuite at
        http://research.microsoft.com/~simonpj/downloads/testsuite.tar.gz

If you untar that, replacing your current testsuite repo, you should be good to go.

Simon

| -----Original Message-----
| From: cvs-ghc-bounces@haskell.org [mailto:cvs-ghc-bounces@haskell.org] On Behalf Of Norman Ramsey
| Sent: 01 May 2008 21:03
| To: cvs-ghc@haskell.org
| Subject: trouble getting repo up to date
|
| I'm trying to get my copy of the head up to date,
| and I'm tripping over a bug in darcs:
|
| : nr@homedog 9937 ; ./darcs-all pull -av
| == running darcs pull -av
| Pulling from "http://darcs.haskell.org/ghc"...
| This is the GHC darcs repository (HEAD branch)
|
| For more information, visit the GHC developer wiki at
|   http://hackage.haskell.org/trac/ghc
| **********************
| We have the following new (to them) patches:
| They have the following patches to pull:
| No remote changes to pull in!
| == nofib not present or not a repository; skipping
| == running darcs pull -av --repodir testsuite
| Pulling from "http://darcs.haskell.org/ghc"...
| This is the GHC darcs repository (HEAD branch)
|
| For more information, visit the GHC developer wiki at
|   http://hackage.haskell.org/trac/ghc
| **********************
| darcs: bug in get_extra commuting patch:
| Fri Sep  7 04:23:27 EDT 2001  simonmar
|   * [project @ 2001-09-07 08:23:27 by simonmar]
|   Fix some signatures after Ord was removed as a superclass of Ix.
| darcs failed: 256 at ./darcs-all line 59.
| : nr@homedog 9939 ;
|
| Can anyone suggest how I should proceed at this point?
|
|
| Norman
|
| _______________________________________________
| Cvs-ghc mailing list
| Cvs-ghc@haskell.org
| http://www.haskell.org/mailman/listinfo/cvs-ghc

Simon/Norman: what version of darcs was this? I'm hoping this is something that
darcs2 has already fixed. 

More specifically, looking at issue279, I understand that David has fixed a
get_extra commuting patch bug between darcses 1.0.9 and 2.0.0.

Old darcs 1.0.9 I think.

I am reluctant to switch to darcs 2.0 until I am confident that it works right, and without the major slow-downs that Simon reports.

If this is simply a known bug in 1.0.9 we can, I believe, work around it by shipping a tar-ball of a recent repo.  I was puzzled because I didn't think there was a show-stopping bug like this in 1.0.9 in a repo that has no conflicts.

Simon

| -----Original Message-----
| From: Eric Kow [mailto:bugs@darcs.net]
| Sent: 02 May 2008 10:08
| To: beschmi@cloaked.de; cvs-ghc@haskell.org; dagit@codersbase.com; eric.kow@gmail.com;
| nr@eecs.harvard.edu; ptp@lysator.liu.se; Simon Peyton-Jones
| Subject: [issue829] pull => bug in get_extra commuting patch
|
|
|
| Simon/Norman: what version of darcs was this? I'm hoping this is something that
| darcs2 has already fixed.
|
| More specifically, looking at issue279, I understand that David has fixed a
| get_extra commuting patch bug between darcses 1.0.9 and 2.0.0.
|
| ----------
| nosy: +kowey
| priority:  -> bug
| status: unread -> chatting
| title: trouble getting repo up to date -> pull => bug in get_extra commuting patch
|
| __________________________________
| Darcs bug tracker <bugs@darcs.net>
| <http://bugs.darcs.net/issue829>
| __________________________________

Any chance this was a partial repository?

For what it's worth, I now have darcs 1.0.9 as well as darcs 2.0.0 on my
machine, so if there's any specific steps I can take to reproduce this, let me know.

Ah, that is possible  Norman will know.

| -----Original Message-----
| From: Eric Kow [mailto:bugs@darcs.net]
| Sent: 02 May 2008 11:00
| To: beschmi@cloaked.de; cvs-ghc@haskell.org; dagit@codersbase.com; eric.kow@gmail.com;
| nr@eecs.harvard.edu; ptp@lysator.liu.se; Simon Peyton-Jones
| Subject: [issue829] pull => bug in get_extra commuting patch
|
|
|
| Any chance this was a partial repository?
|
| For what it's worth, I now have darcs 1.0.9 as well as darcs 2.0.0 on my
| machine, so if there's any specific steps I can take to reproduce this, let me know.
|
| __________________________________
| Darcs bug tracker <bugs@darcs.net>
| <http://bugs.darcs.net/issue829>
| __________________________________

> 
 > 
 > Simon/Norman: what version of darcs was this? I'm hoping this is something
 > that darcs2 has already fixed.
 > 
 > More specifically, looking at issue279, I understand that David has fixed a
 > get_extra commuting patch bug between darcses 1.0.9 and 2.0.0.

This is in fact 1.0.9 (Debian testing version).

Norman

> Any chance this was a partial repository?

No chance.

 > For what it's worth, I now have darcs 1.0.9 as well as darcs 2.0.0 on my
 > machine, so if there's any specific steps I can take to reproduce this, let
 > me know.

Pushing a 100+MB tarball up through my ADSL line will knock out
Internet at my house for most of a day, but if it's important, I can
do it.

Norman

On Fri, May 02, 2008 at 20:34:30 -0400, Norman Ramsey wrote:
>  > For what it's worth, I now have darcs 1.0.9 as well as darcs 2.0.0 on my
>  > machine, so if there's any specific steps I can take to reproduce this, let
>  > me know.
> 
> Pushing a 100+MB tarball up through my ADSL line will knock out
> Internet at my house for most of a day, but if it's important, I can
> do it.

Well, since you're on Linux, where installing darcs is relatively easy,
could I ask you to obtain a copy of darcs 2
  http://www.darcs.net/darcs-2.0.0.tar.gz
and being careful to rename the binary to darcs2 (thus keeping your old
darcs within reach), attempt to reproduce the problem?

If you could boil it down to "it breaks on darcs 1.0.9, but works fine
on darcs 2.0.0", I would be happy.  If you can get it so that the same
steps break on both darcs, I would also be happy although less so.

I'm marking this as "wont-fix" for now, since no follow-up example was provided
in the last three months. It also sounds like it could be a Darcs 1.0.9 bug that
was fixed in Darcs 2 anyway. 

Of course, if anyone can trigger this with Darcs 2.0.2 or newer, please re-open
this ticket.

Reopening this bug, as I have one that looks a bit similar. The 
http://zwiki.org/ZWiki and http://zwiki.org/ZWiki-unstable repos have just been 
converted to darcs-2 format, from darcs-1 and hashed formats respectively. 
Pulling between them now gives the error. This is using darcs 2.1.0pre2 (+ 14 
patches) on ubuntu.

$ darcs pull
Pulling from "/repos/ZWiki"...
darcs: bug in get_extra commuting patches:
First patch is:
Sat May 17 10:14:34 PDT 2008  Simon Michael <simon@joyful.com>
  * clean up test rules
Second patch is:
Fri Oct 24 22:22:46 PDT 2008  Simon Michael <simon@joyful.com>
  * update makefile checklists, note new CHANGES.txt suffix

Bad urls; the repos are actually http://zwiki.org/repos/ZWiki and 
http://zwiki.org/repos/ZWiki-unstable . To reproduce, get them and try pulling 
from stable to unstable.

On Fri, Oct 24, 2008 at 11:17 PM, Simon Michael <bugs@darcs.net> wrote:
>
> Simon Michael <simon@joyful.com> added the comment:
>
> Reopening this bug, as I have one that looks a bit similar. The
> http://zwiki.org/ZWiki and http://zwiki.org/ZWiki-unstable repos have just been
> converted to darcs-2 format, from darcs-1 and hashed formats respectively.
> Pulling between them now gives the error. This is using darcs 2.1.0pre2 (+ 14
> patches) on ubuntu.

Did you run 'darcs convert' once for each branch or did you run it
once for the entire project?

If you converted each branch then it is known that they will be
incompatible, and this failure in get_extra is one possible
manifestation.  The only other known/hypothesized cause of this that I
can think of includes patches which have identical meta data but
different contents.  I can tell from the output that is not the case
for you.

Thanks for the report Simon!

Jason

> The only other known/hypothesized cause of this that I
> can think of includes patches which have identical meta data but
> different contents.  I can tell from the output that is not the case
> for you.

I just realized I'm wrong about that.  A proper assessment would
involve looking at the contents of the first and second patch listed
in the output of error message and see if they are identical in both
copies of the repository.  Something like:

cd ZWiki; darcs changes -v -p 'clean up test rules'
cd ../ZWiki-unstable; darcs changes -v p 'clean up test rules'

Do that for both patches.  If either patch is different between the
two repositories then this is just like
http://bugs.darcs.net/issue1026.

Sorry for my silliness.

Jason

On Fri, Oct 24, 2008 at 08:20:59PM +0000, Simon Michael wrote:
> The repos are [...] http://zwiki.org/repos/ZWiki and
> http://zwiki.org/repos/ZWiki-unstable.

The latter does not work for me:

$ darcs get http://zwiki.org/repos/ZWiki
Finished getting.
$ darcs get http://zwiki.org/repos/ZWiki-unstable

darcs failed: Not a repository: http://zwiki.org/repos/ZWiki-unstable
(Failed to download URL
http://zwiki.org/repos/ZWiki-unstable/_darcs/inventory:
HTTP response code said error)
$

I'm restoring this bug to its intended wont-fix status from msg5463.
See issue1537 for Simon's continuation from msg6440.