You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Heather Stephens (JIRA)" <be...@incubator.apache.org> on 2004/11/12 20:22:23 UTC
[jira] Created: (BEEHIVE-86) tar.gz file probs from build.dist.archives
tar.gz file probs from build.dist.archives
------------------------------------------
Key: BEEHIVE-86
URL: http://nagoya.apache.org/jira/browse/BEEHIVE-86
Project: Beehive
Type: Bug
Components: Build
Versions: V1Alpha, V1Beta, V1
Environment: Windows, DOS shell
Reporter: Heather Stephens
Fix For: V1Beta
Cannot get complete extracted dist from generated tar.gz file generated by build.dist.archives target.
Two repros:
tar -xvzf <filename>
or
tar -vxf <filename>
gunzip <filename>
Results:
Don't get a complete dist laid down from archives where pathnames are long ... checkout the depths of a WS sample in the WEB-INF/src tree
The problem seems to be in the generated archive. Don't have time to dig into it today but wanted to get the bug filed.
(Thanks to Michael for helping with this this morning...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (BEEHIVE-86) tar.gz file probs from build.dist.archives
Posted by "Kenneth Tam (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-86?page=history ]
Kenneth Tam reassigned BEEHIVE-86:
----------------------------------
Assign To: Kenneth Tam
It's not clear to me that anything's changed here (ie, whether the <tar> task under Windows handles long paths correctly), but I'll investigate.
> tar.gz file probs from build.dist.archives
> ------------------------------------------
>
> Key: BEEHIVE-86
> URL: http://issues.apache.org/jira/browse/BEEHIVE-86
> Project: Beehive
> Type: Bug
> Components: Build
> Versions: V1Alpha, V1Beta, V1
> Environment: Windows, DOS shell
> Reporter: Heather Stephens
> Assignee: Kenneth Tam
> Fix For: V1Beta
>
> Cannot get complete extracted dist from generated tar.gz file generated by build.dist.archives target.
> Two repros:
> tar -xvzf <filename>
> or
> tar -vxf <filename>
> gunzip <filename>
> Results:
> Don't get a complete dist laid down from archives where pathnames are long ... checkout the depths of a WS sample in the WEB-INF/src tree
> The problem seems to be in the generated archive. Don't have time to dig into it today but wanted to get the bug filed.
> (Thanks to Michael for helping with this this morning...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (BEEHIVE-86) tar.gz file probs from build.dist.archives
Posted by "bob mcwhirter (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-86?page=comments#action_55409 ]
bob mcwhirter commented on BEEHIVE-86:
--------------------------------------
Sun tar has problem with long paths. Probably other non-GNU OSes have the same problem.
Grab GNU-tar and it has no problems with them.
> tar.gz file probs from build.dist.archives
> ------------------------------------------
>
> Key: BEEHIVE-86
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-86
> Project: Beehive
> Type: Bug
> Components: Build
> Versions: V1Alpha, V1Beta, V1
> Environment: Windows, DOS shell
> Reporter: Heather Stephens
> Fix For: V1Beta
>
> Cannot get complete extracted dist from generated tar.gz file generated by build.dist.archives target.
> Two repros:
> tar -xvzf <filename>
> or
> tar -vxf <filename>
> gunzip <filename>
> Results:
> Don't get a complete dist laid down from archives where pathnames are long ... checkout the depths of a WS sample in the WEB-INF/src tree
> The problem seems to be in the generated archive. Don't have time to dig into it today but wanted to get the bug filed.
> (Thanks to Michael for helping with this this morning...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (BEEHIVE-86) tar.gz file probs from build.dist.archives
Posted by "Julie Zhuo (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-86?page=all ]
Julie Zhuo closed BEEHIVE-86:
-----------------------------
Assign To: Julie Zhuo (was: Kenneth Tam)
This issue is related to
http://issues.apache.org/jira/browse/BEEHIVE-91
http://issues.apache.org/jira/browse/BEEHIVE-403.
We now use ant tar task to create the tar file and have document to tell customers use only gnu compatible tar utilities to decompress the tar.gz. Close.
> tar.gz file probs from build.dist.archives
> ------------------------------------------
>
> Key: BEEHIVE-86
> URL: http://issues.apache.org/jira/browse/BEEHIVE-86
> Project: Beehive
> Type: Bug
> Components: Build
> Versions: V1Alpha, V1Beta, V1
> Environment: Windows, DOS shell
> Reporter: Heather Stephens
> Assignee: Julie Zhuo
> Fix For: V1Beta
>
> Cannot get complete extracted dist from generated tar.gz file generated by build.dist.archives target.
> Two repros:
> tar -xvzf <filename>
> or
> tar -vxf <filename>
> gunzip <filename>
> Results:
> Don't get a complete dist laid down from archives where pathnames are long ... checkout the depths of a WS sample in the WEB-INF/src tree
> The problem seems to be in the generated archive. Don't have time to dig into it today but wanted to get the bug filed.
> (Thanks to Michael for helping with this this morning...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-86) tar.gz file probs from build.dist.archives
Posted by "Kenneth Tam (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-86?page=history ]
Kenneth Tam resolved BEEHIVE-86:
--------------------------------
Resolution: Fixed
Delegate to an external tar program when building archives under Windows, svn #155753.
> tar.gz file probs from build.dist.archives
> ------------------------------------------
>
> Key: BEEHIVE-86
> URL: http://issues.apache.org/jira/browse/BEEHIVE-86
> Project: Beehive
> Type: Bug
> Components: Build
> Versions: V1Alpha, V1Beta, V1
> Environment: Windows, DOS shell
> Reporter: Heather Stephens
> Assignee: Kenneth Tam
> Fix For: V1Beta
>
> Cannot get complete extracted dist from generated tar.gz file generated by build.dist.archives target.
> Two repros:
> tar -xvzf <filename>
> or
> tar -vxf <filename>
> gunzip <filename>
> Results:
> Don't get a complete dist laid down from archives where pathnames are long ... checkout the depths of a WS sample in the WEB-INF/src tree
> The problem seems to be in the generated archive. Don't have time to dig into it today but wanted to get the bug filed.
> (Thanks to Michael for helping with this this morning...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (BEEHIVE-86) tar.gz file probs from build.dist.archives
Posted by "Heather Stephens (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-86?page=comments#action_55410 ]
Heather Stephens commented on BEEHIVE-86:
-----------------------------------------
More info that may be useful.
When I create a tar.gz using build.dist.archives target in a DOS prompt, I get this issue.
If I manually create it, I don't have this problem. (So we will ship today. *grin*)
> tar.gz file probs from build.dist.archives
> ------------------------------------------
>
> Key: BEEHIVE-86
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-86
> Project: Beehive
> Type: Bug
> Components: Build
> Versions: V1Alpha, V1Beta, V1
> Environment: Windows, DOS shell
> Reporter: Heather Stephens
> Fix For: V1Beta
>
> Cannot get complete extracted dist from generated tar.gz file generated by build.dist.archives target.
> Two repros:
> tar -xvzf <filename>
> or
> tar -vxf <filename>
> gunzip <filename>
> Results:
> Don't get a complete dist laid down from archives where pathnames are long ... checkout the depths of a WS sample in the WEB-INF/src tree
> The problem seems to be in the generated archive. Don't have time to dig into it today but wanted to get the bug filed.
> (Thanks to Michael for helping with this this morning...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (BEEHIVE-86) tar.gz file probs from build.dist.archives
Posted by "Kenneth Tam (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-86?page=comments#action_59654 ]
Kenneth Tam commented on BEEHIVE-86:
------------------------------------
Looks like this is still broken under Windows. Fix is probably to use an <exec> when building under windows and require the presence of a Win32 tar.exe/gzip.exe.
> tar.gz file probs from build.dist.archives
> ------------------------------------------
>
> Key: BEEHIVE-86
> URL: http://issues.apache.org/jira/browse/BEEHIVE-86
> Project: Beehive
> Type: Bug
> Components: Build
> Versions: V1Alpha, V1Beta, V1
> Environment: Windows, DOS shell
> Reporter: Heather Stephens
> Assignee: Kenneth Tam
> Fix For: V1Beta
>
> Cannot get complete extracted dist from generated tar.gz file generated by build.dist.archives target.
> Two repros:
> tar -xvzf <filename>
> or
> tar -vxf <filename>
> gunzip <filename>
> Results:
> Don't get a complete dist laid down from archives where pathnames are long ... checkout the depths of a WS sample in the WEB-INF/src tree
> The problem seems to be in the generated archive. Don't have time to dig into it today but wanted to get the bug filed.
> (Thanks to Michael for helping with this this morning...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (BEEHIVE-86) tar.gz file probs from build.dist.archives
Posted by "Kenneth Tam (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-86?page=comments#action_59924 ]
Kenneth Tam commented on BEEHIVE-86:
------------------------------------
I believe the ant bug that's behind this issue is:
http://issues.apache.org/bugzilla/show_bug.cgi?id=31093
> tar.gz file probs from build.dist.archives
> ------------------------------------------
>
> Key: BEEHIVE-86
> URL: http://issues.apache.org/jira/browse/BEEHIVE-86
> Project: Beehive
> Type: Bug
> Components: Build
> Versions: V1Alpha, V1Beta, V1
> Environment: Windows, DOS shell
> Reporter: Heather Stephens
> Assignee: Kenneth Tam
> Fix For: V1Beta
>
> Cannot get complete extracted dist from generated tar.gz file generated by build.dist.archives target.
> Two repros:
> tar -xvzf <filename>
> or
> tar -vxf <filename>
> gunzip <filename>
> Results:
> Don't get a complete dist laid down from archives where pathnames are long ... checkout the depths of a WS sample in the WEB-INF/src tree
> The problem seems to be in the generated archive. Don't have time to dig into it today but wanted to get the bug filed.
> (Thanks to Michael for helping with this this morning...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira