The expected result (unarchiving the eclipse package, and being able to successfully start eclipse) was achieved by:
$ tar xvzf eclipse-SDK-3.5RC4-linux-gtk.tar.gz using GNU tar 1.20-1 Does that help? On Mon, Jun 29, 2009 at 10:36 AM, Sebastien Bacher <seb...@ubuntu.com>wrote: > the new comment is still not clear, what command do you use and does it > work or not? > > -- > file-roller fails to complete extract > https://bugs.launchpad.net/bugs/393052 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “file-roller” package in Ubuntu: New > > Bug description: > Binary package hint: file-roller > > file-roller: > Installed: 2.26.1-0ubuntu1 > Candidate: 2.26.1-0ubuntu1 > Version table: > *** 2.26.1-0ubuntu1 0 > 500 http://us.archive.ubuntu.com jaunty/main Packages > 100 /var/lib/dpkg/status > > Target Archive: eclipse-SDK-3.5RC4-linux-gtk.tar.gz > found at: > > > http://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops/S-3.5RC4-200906051444/eclipse-SDK-3.5RC4-linux-gtk.tar.gz > > Expected result (achieved w/ GNU tar 1.20-1): > > unarchive; succesful startup of eclipse from result; > > Actual (with file-roller): > > archive looks partially unpacked, "temp" file (e.g. named .fr-Dicbx3, > .fr-EkDRyl, etc. depending on the run) contains top folder, with > subfolders unpopulated.... > > Remainder of content appears un-allocated to target locations; when run > from the command line, no errors or indicators appear. > > An xml report of the comparison of results from file-roller (.../tmp) to > tar -xvfz (.../eclipse) is attached. > > ProblemType: Bug > Architecture: i386 > DistroRelease: Ubuntu 9.04 > ExecutablePath: /usr/bin/file-roller > NonfreeKernelModules: nvidia > Package: file-roller 2.26.1-0ubuntu1 > ProcEnviron: > PATH=(custom, user) > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: file-roller > Uname: Linux 2.6.28-13-generic i686 > -- file-roller fails to complete extract https://bugs.launchpad.net/bugs/393052 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
