[
https://issues.apache.org/jira/browse/BUILDR-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913068#action_12913068
]
Alex Boisvert commented on BUILDR-502:
--------------------------------------
Perhaps a viable way to debug this would be to instrument the ArchiveTask (and
possibly others) to either output detailed trace of its execution or add some
fairly strict runtime assertions so that it fails at the point where the
corruption happens.
I'm suspecting a similar issue as was fixed previously by Antoine. Maybe
another file/directory confusion in the code.
> tgz packaging produces an incorrect archive
> -------------------------------------------
>
> Key: BUILDR-502
> URL: https://issues.apache.org/jira/browse/BUILDR-502
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.4.1
> Environment: linux ubuntu, ruby 1.8.7 (2010-01-10 patchlevel 249)
> [i486-linux], gem 1.3.5
> Reporter: Jean-Philippe Caruana
> Fix For: 1.4.3
>
> Attachments: archive.tgz
>
>
> we switched recently to buidlr 1.4.1 and we encounter problems with tgz
> packaging. We didn't change our buildfile and the generated tgz now produce
> errors with "tar xzf" command :
> tar: batch: Cannot open: File exists
> tar: Exiting with failure status due to previous errors
> here is my (sample) buildfile :
> define 'archive' do
> lib = package :jar
> my_tgz = package :tgz
> my_tgz.include _('src/main/batch'), :as=>'batch'
> my_tgz.path('batch/lib').include lib
> end
> here are my files :
> archive
> |-- buildfile
> `-- src
> `-- main
> |-- batch
> | |-- bin
> | | `-- start_script.sh
> | `-- etc
> | |-- file1
> | |-- file2
> | `-- file3
> `-- java
> `-- Empty.java
> In fact, the archive is strange. When I look inside it (see the 3rd line wit
> tar tvzf archive-1.0.0.tgz
> tar: Record size = 10 blocks
> -rw-r--r-- 1000/1000 607 2010-09-01 11:13 batch/lib/archive-1.0.0.jar
> -rw-r--r-- 1000/1000 0 2010-09-01 11:00 batch/etc/file1
> -rw-r--r-- 1000/1000 0 2010-09-01 11:00 batch
> -rw-r--r-- 1000/1000 0 2010-09-01 11:00 batch/bin/start_script.sh
> -rw-r--r-- 1000/1000 0 2010-09-01 11:00 batch/etc/file2
> -rw-r--r-- 1000/1000 0 2010-09-01 11:00 batch/etc/file3
> if the archive is generated with buildr 1.3.5, output is different :
> tar tvzf archive-1.0.0.tgz
> tar: Record size = 9 blocks
> -rw-r--r-- 1000/1000 618 2010-09-01 11:10 batch/lib/archive-1.0.0.jar
> -rw-r--r-- 1000/1000 0 2010-09-01 11:00 batch/etc/file1
> -rw-r--r-- 1000/1000 0 2010-09-01 11:00 batch/etc/file2
> -rw-r--r-- 1000/1000 0 2010-09-01 11:00 batch/bin/start_script.sh
> -rw-r--r-- 1000/1000 0 2010-09-01 11:00 batch/etc/file3
> It happens on all computers here (team of 10).
> Here is my gem list (on linux ubuntu)
> *** LOCAL GEMS ***
> Antwrap (0.7.0)
> archive-tar-minitar (0.5.2)
> builder (2.1.2)
> buildr (1.4.1)
> highline (1.5.1)
> hoe (2.3.3)
> json_pure (1.4.3)
> net-sftp (2.0.2)
> net-ssh (2.0.15)
> rake (0.8.7)
> rjb (1.2.5)
> rspec (1.3.0)
> rubyforge (2.0.3)
> rubyzip (0.9.1)
> xml-simple (1.0.12)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
