Le 02/09/2010 16:28, Jean-Philippe Caruana a écrit :
Le 01/09/2010 20:24, Alex Boisvert a écrit :
Hi Jean-Philipe,

I tried your project and I can't reproduce your issue on Buildr 1.4.1 or
trunk. I suggest you open an issue and attach the output of "gem list".
I suspect some kind of system configuration issue, maybe with one of
the tar
dependency.

alex

Thanks Alex : I oppened https://issues.apache.org/jira/browse/BUILDR-502
with more details (sample project, gem list, ruby version and so on)

Hi all,

thanks for the 1.4.2 release : you've done a great job !

I stil have my tgz packaging problem. The 1.4.2 release is working fine with the example project I gave in https://issues.apache.org/jira/browse/BUILDR-502 but it is stil not working good with my real project. Here is what I got when I untar (tar xzf blabla.tgz) :
tar: Skipping to next header
tar: Skipping to next header
tar: Exiting with failure status due to previous errors

echo $?
2

I reopened the BUILDR-502 issue, but I don't know how to isolate the differences between my project and the example one I gave.

Any idea ?

thanks

-- Jean-Philippe Caruana
********************************
Ce message et toutes les pieces jointes (ci-apres le "message") sont
confidentiels et etablis a l'attention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration. Multimedia Business 
Services decline
toute responsabilite au titre de ce message s'il a ete altere, deforme
ou falsifie.
Si vous n'etes pas destinataire de ce message, merci de le detruire
immediatement et d'avertir l'expediteur.
*********************************
This message and any attachments (the "message") are confidential and
intended solely for the addressees. Any unauthorised use or
dissemination is prohibited.
Messages are susceptible to alteration. Multimedia Business Services shall not 
be liable for the
message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it
immediately and inform the sender..
********************************

Reply via email to