After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 680397 - ftpadmin install: gwt-glom cannot avoid "Too much uncompressed tarball data" error
ftpadmin install: gwt-glom cannot avoid "Too much uncompressed tarball data" ...
Status: RESOLVED OBSOLETE
Product: sysadmin
Classification: Infrastructure
Component: Mirrors
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2012-07-22 11:22 UTC by Murray Cumming
Modified: 2013-11-21 14:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Murray Cumming 2012-07-22 11:22:06 UTC 
When trying to use "ftpadmin install" on my gwt-glom tarball, I get this error:

[murrayc@master ~]$ ftpadmin install gwt-glom-1.21.10.tar.bz2 
Gathering information and sorting on version: ., done
Preparing installation of gwt-glom-1.21.10.tar.bz2:
 - Checking consistency: ., failed
ERROR: Too much uncompressed tarball data (expected max 10.00K, found 1.73M); use tar-ustar in AM_INIT_AUTOMAKE!

But gwt-glom uses the maven build system (It's Java) and there doesn't seem to be any way to specify details of the tar format used.

gwt-glom is actually on gitorious right now, but I'd like to move it to git.gnome.org eventually.
Comment 1 Murray Cumming 2012-10-15 11:04:46 UTC 
Do you have any suggestion how I can work around this?
Comment 2 Andrea Veri 2013-11-21 14:55:44 UTC 
The GNOME Infrastructure Team is currently migrating its bug / issue tracker away from Bugzilla to Request Tracker and therefore all the currently open bugs have been closed and marked as OBSOLETE.

The following move will also act as a cleanup for very old and ancient tickets that were still living on Bugzilla. If your issue still hasn't been fixed as of today please report it again on the relevant RT queue.

More details about the available queues you can report the bug against can be found at https://wiki.gnome.org/Sysadmin/RequestTracker.

Thanks for your patience,

the GNOME Infrastructure Team