darcs

Message4650

Author simonpj
Recipients Simon, beschmi, dagit, daveroundy, droundy, igloo, kowey, simonmar, simonpj, tommy, zooko
Date 2008-05-14.08:38:38
Issue Issue842 pull => problem gzopening file for write (1.0.9)
Content
PS.  Ah I see that the patch Eric mentions was indeed the one mentioned in my original bug report.

But when I do this
        start from the tar ball I've put up
        darcs pull http://darcs.haskell.org/ghc -av
then I get the error

darcs failed:  problem gzopening file for write: _darcs/patches/20080125161308-e23c7-641f90a729379274c5079732c681bcc47fc3e314.gz-0

Same error, different file.

Simon

| -----Original Message-----
| From: Eric Kow [mailto:bugs@darcs.net]
| Sent: 13 May 2008 19:57
| To: Simon@osuosl.org; beschmi@cloaked.de; dagit@codersbase.com;
| daveroundy@gmail.com; droundy@darcs.net; eric.kow@gmail.com; igloo@earth.li;
| ptp@lysator.liu.se; Simon Marlow; Simon Peyton-Jones
| Subject: [issue842] pull => problem gzopening file for write (1.0.9)
|
|
| Eric Kow <eric.kow@gmail.com> added the comment:
|
| Out of curiosity, I googled the error message and stumbled upon this FAQ from
| gzip.org.  I tried their fixgz program, but the resulting file still gives a
| CRC
| error.
|
| Simon, maybe it would be worthwhile to see what happens if you
|
|  zcat
| _darcs/patches/20080126191939-e23c7-
| efc06647390321527cc18de0e08c017b568b36ae.gz
| > tmp-patch
|  gzip tmp-patch
|  mv tmp-patch.gz
| _darcs/patches/20080126191939-e23c7-
| efc06647390321527cc18de0e08c017b568b36ae.gz
|
| ... and then try the darcs pull.
|
| And here is the FAQ:
|
| ========8<==================
| gunzip complains about corrupted data or a CRC error
|
| 99.9% of the problems with gzip are due to file transfers done in ASCII mode
| instead of BINARY mode. In particular, gopher is known to corrupt binary
| files
| by considering them as ASCII. Make sure that your local copy of the file has
| exactly the same byte size as the original.
|
| If you have transferred a file in ASCII mode and you no longer have access to
| the original, you can try the program fixgz to remove the extra CR (carriage
| return) bytes inserted by the transfer. A Windows 9x/NT/2000/ME/XP binary is
| here. But there is absolutely no guarantee that this will actually fix your
| file. Conclusion: never transfer binary files in ASCII mode. To compile fixgz
| and run it, do:
|
|    cc -o fixgz fixgz.c
|    fixgz  bad.gz  fixed.gz
|    gzip -tv fixed.gz
| ======8<=======================
|
| Ok, I stop here.  Over to David (or somebody else!)
|
| __________________________________
| Darcs bug tracker <bugs@darcs.net>
| <http://bugs.darcs.net/issue842>
| __________________________________
History
Date User Action Args
2008-05-14 08:38:38simonpjcreate
2008-05-14 08:38:40simonpjlinkissue842 messages
2008-05-14 08:38:40simonpjsetrecipients: + simonpj, zooko