|  | 
 | 
Created on 2008-10-09.09:02:42 by dleuschner, last changed 2009-08-27.14:13:02 by admin. 
 
  
   | msg6288 (view) | Author: dleuschner | Date: 2008-10-09.09:02:38 |  |  
   | $ darcs get  http://happs.org/repos/HAppS-HTTP
Unapplicable patch:                                                         
Mon Oct  9 11:31:52 CEST 2006  Einar Karttunen <einar@vo.com>
  * Remove S3 stuff that was never enabled from the repo
$ darcs -v
2.1.0pre3 (prerelease 3)
I had no problems getting the repository using darcs 1.0.9.
Cheers,  David |  
   | msg6290 (view) | Author: dmitry.kurochkin | Date: 2008-10-09.12:46:50 |  |  
   | I was able to reproduce this with latest unstable 2.1.0 (+ 81 patches), latest
stable 2.1.0 (+ 31 patches) and 2.0.2. Output is always the same:
./unstable/darcs get http://happs.org/repos/HAppS-HTTP
Unapplicable patch:                                              
Mon Oct  9 13:31:52 MSD 2006  Einar Karttunen <einar@vo.com>
  * Remove S3 stuff that was never enabled from the repo
darcs failed:  Cannot remove non-empty file ./src/HAppS/Protocols/S3.hs
So this is not a regression from 2.0.2. But it is regression from 1.0.9 at
least. Perhaps we should look at this before release 2.1.0?
Regards,
  Dmitry |  
   | msg6291 (view) | Author: thorkilnaur | Date: 2008-10-09.13:18:03 |  |  
   | I discussed this with kowey on #darcs. He indicated that the basic problem could 
be a corruption in the source repository that could be darcs repaired with a 
darcs 2. Also, this apparent regression could be a bug in older darcs (maybe 
just 1.0.9) that succeeded when it shouldn't. And, lastly, a workaround could be 
to use get --hashed or get --partial to get the repository.
Thanks for the bug report in any case.
Best regards
Thorkil |  
   | msg6390 (view) | Author: thorkilnaur | Date: 2008-10-22.18:06:34 |  |  
   | Looking into this in more detail, I was able to reproduce exactly the behaviour reported on a case-insensitive file system (Mac OS 
X in the standard setup): Getting with darcs 1.0.9 succeeded, whereas getting with darcs 2.0.2 failed with the reported result. In 
addition, I have verified that the work-around (getting with --hashed) works.
On a case-sensitive file system (Mac OS X with non-standard setup), however, get with darcs 2.0.x succeeded.
This looks very much like issue 1067 and since that is marked as a duplicate of 971, I am marking this as a duplicate of issue 971 
also.
Best regards
Thorkil |  |
 
| Date | User | Action | Args |  | 2008-10-09 09:02:42 | dleuschner | create |  |  | 2008-10-09 12:46:52 | dmitry.kurochkin | set | status: unread -> unknown nosy:
  kowey, dagit, dleuschner, simon, thorkilnaur, dmitry.kurochkin
 messages:
  + msg6290
 |  | 2008-10-09 13:18:04 | thorkilnaur | set | nosy:
  kowey, dagit, dleuschner, simon, thorkilnaur, dmitry.kurochkin messages:
  + msg6291
 |  | 2008-10-22 18:06:37 | thorkilnaur | set | status: unknown -> duplicate nosy:
  kowey, dagit, dleuschner, simon, thorkilnaur, dmitry.kurochkin
 superseder:
  + darcs check fails (case sensitivity on filenames)
 messages:
  + msg6390
 |  | 2009-08-10 23:47:51 | admin | set | nosy:
  - dagit |  | 2009-08-25 17:30:40 | admin | set | nosy:
  + darcs-devel, - simon |  | 2009-08-27 14:13:02 | admin | set | nosy:
  kowey, darcs-devel, dleuschner, thorkilnaur, dmitry.kurochkin | 
 |