James Mead
2007-Jul-24 19:54 UTC
[mocha-developer] mocha tarballs don''t uncompress cleanly
Hi Antonio, My environment is OS X 10.4.8. Thanks a lot for looking into the problem. Please let me know if I can do anything to help. I have had problems previously with tar including Mac resource fork files. Could this be what is causing your problem? James. On 24 Jul 2007, at 20:42, Antonio Terceiro wrote:> Hi James, > > First of all, thanks for mocha, it''s a really great library and helps > testing a lot. :) > > I downloaded the mocha tarball for versions 0.5.0, 0.5.1 and 0.5.2 > (didn''t test older ones), and when uncompressing all of them I get the > following error: > > -------------------8<---------------------8<----------------------- > terceiro at s219pc02:/tmp/bli$ LANG=C tar xzf ../mocha-0.5.2.tgz > > gzip: stdin: decompression OK, trailing garbage ignored > tar: Child returned status 2 > tar: Error exit delayed from previous errors > -------------------8<---------------------8<----------------------- > > The tarball is uncompressed, but this error message (and the non-zero > exit status) is pretty annoying. > > I tried to reproduce the tarball generation here on my machine, by > entering the mocha-0.5.2 directory and issuing a `rake package` > command, > but the generated tarball is uncompressed cleanly. According to the > message, the problem seems to be in the gzip compression, but I can''t > actually tell what is causing it. > > Can you please tell me which environment you are used to generate the > mocha packages on, so I can try to prepare a fix to this issue? > > Best regards, > > -- > Antonio Terceiro <terceiro at softwarelivre.org> > http://people.softwarelivre.org/~terceiro/ > GnuPG ID: 0F9CB28F > > >
James Mead
2007-Jul-25 14:56 UTC
[mocha-developer] mocha tarballs don''t uncompress cleanly
Many thanks again for looking into this. Here are the answers to your questions... On 25 Jul 2007, at 14:44, Antonio Terceiro wrote:> What''s the versions of gzip and tar in your system? Here I have > gzip 1.3.5 > and tar 1.16 ...$ tar --version tar (GNU tar) 1.14 $ gzip --version gzip 1.3.5 $ gunzip --version gunzip 1.3.5> Could you send me the output of the `rake package` there??> What happens if you try to uncompress the generated tarball??
James Mead
2007-Jul-28 22:58 UTC
[mocha-developer] mocha tarballs don''t uncompress cleanly
I''ve just released a new version of Mocha (0.5.3). I''ve attempted to fix the packaging problems by switching to newer version (1.15.1) of gnutar and setting COPY_EXTENDED_ATTRIBUTES_DISABLE environment variable in my OSX bash environment. This seems to have got rid of the pesky ._*.rb files. Let me know if you are still having the same problem unpacking the new versions of the files. Thanks. On 27 Jul 2007, at 14:12, Antonio Terceiro wrote:> James Mead escreveu isso a?: >> >> On 25 Jul 2007, at 18:28, Antonio Terceiro wrote: >>> This one uncompresses cleanly. I suspect that maybe there can be a >>> problem >>> with that Rake task which uploads the file to rubyforge ... >>> >>> It''s very unlikely, but would you still have the exact tarball you >>> generated just before an upload to rubyforge? I guess any version >>> would >>> be good enough. >> >> Sorry. I overwrote it when I created the one I sent you. > > Ahh, damn ... :) > >> Perhaps I should try re-publishing to rubyforge. I''ll try and do it >> over the weekend. > > Ok, feel free to ping me then. > > Creers, > > -- > Antonio Terceiro <terceiro at softwarelivre.org> > http://people.softwarelivre.org/~terceiro/ > GnuPG ID: 0F9CB28F > > >
James Mead
2007-Sep-03 11:29 UTC
[mocha-developer] mocha tarballs don''t uncompress cleanly
Hi Antonio, Did you ever get any further with this...? I''m sorry - I''ve been busy at work, then ill, then on holiday. I can only assume this means the Rake::GemPackageTask is to blame. I''m using version 0.7.3 of the Rake gem on a PPC Mac with OSX 10.4.10. I wonder if it''s worth trying to set up a dummy (virtually empty) project and trying to create a tarball using Rake::GemPackageTask and see if we can reproduce the problem...? Cheers, James. On 1 Aug 2007, at 22:17, Antonio Terceiro wrote:> James Mead escreveu isso a?: >> I think you''re in luck - I''m pretty sure this is the one! > > Aha, just as I as I suspected: the tarball on rubyforge is different > from the one you have. > > -----------------------------8<------------------------------------ > terceiro at sede:~/tmp$ ls -l > total 36 > -rw------- 1 terceiro terceiro 33766 2007-08-01 17:06 mocha-0.5.3.tgz > terceiro at sede:~/tmp$ wget -O mocha-rubyforge-0.5.3.tgz http:// > rubyforge.org/frs/download.php/23330/mocha-0.5.3.tgz > --17:06:45-- http://rubyforge.org/frs/download.php/23330/ > mocha-0.5.3.tgz > => `mocha-rubyforge-0.5.3.tgz'' > Resolvendo rubyforge.org... 205.234.109.18 > Connecting to rubyforge.org|205.234.109.18|:80... conectado! > HTTP requisi??o enviada, aguardando resposta... 302 Found > Localiza??o: http://rubyforge.rubyuser.de/mocha/mocha-0.5.3.tgz > [seguinte] > --17:06:46-- http://rubyforge.rubyuser.de/mocha/mocha-0.5.3.tgz > => `mocha-rubyforge-0.5.3.tgz'' > Resolvendo rubyforge.rubyuser.de... 80.237.222.133 > Connecting to rubyforge.rubyuser.de|80.237.222.133|:80... conectado! > HTTP requisi??o enviada, aguardando resposta... 200 OK > Tamanho: 33,768 (33K) [application/x-tgz] > > 100%[====================================>] 33,768 34.00K/s > > 17:06:48 (33.94 KB/s) - `mocha-rubyforge-0.5.3.tgz'' saved > [33768/33768] > > terceiro at sede:~/tmp$ hexdump mocha-0.5.3.tgz > mocha-0.5.3.tgz.hex > terceiro at sede:~/tmp$ hexdump mocha-rubyforge-0.5.3.tgz > mocha- > rubyforge-0.5.3.tgz.hex > terceiro at sede:~/tmp$ diff -u mocha-0.5.3.tgz.hex mocha- > rubyforge-0.5.3.tgz.hex > --- mocha-0.5.3.tgz.hex 2007-08-01 17:07:00.000000000 -0300 > +++ mocha-rubyforge-0.5.3.tgz.hex 2007-08-01 > 17:07:08.000000000 -0300 > @@ -2108,5 +2108,5 @@ > 00083b0 ce9a 8e0e b77f fce9 0ef9 e709 6f21 15e6 > 00083c0 c4a8 5444 2a2d 6a59 9695 f2cf 3e59 67cb > 00083d0 2cf9 e59f 7cb3 cf96 99f2 f3ff 03ff 2077 > -00083e0 13ff e800 0003 > -00083e6 > +00083e0 13ff e800 0003 0a0d > +00083e8 > -----------------------------8<------------------------------------ > > They are almost identical, but there is an extra newline byte pair > (0a0d > = "\n\r") at the end of the file ... I checked and all the other files > (*.zip and .gem) and they also have a 0a0d at their ends. > > I don''t know what could be adding this extra newline ... :-( > > -- > Antonio Terceiro <terceiro at softwarelivre.org> > http://people.softwarelivre.org/~terceiro/ > GnuPG ID: 0F9CB28F > > >