Ubuntu

Cannot open tgz archive from FreeBSD

Reported by l0b0 on 2007-07-30
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
tar (Ubuntu)
Undecided
Sunny Shin

Bug Description

Binary package hint: tar

I have made a tgz file on FreeBSD 6.2-RELEASE which I'm unable to unpack on Ubuntu. I /am/ able to unpack it on Windows using 7zip.

tar -zxvf gives the following output:

tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
tar: Ignoring unknown extended header keyword `SCHILY.ino'
tar: Ignoring unknown extended header keyword `SCHILY.nlink'
tar: Ignoring unknown extended header keyword `SCHILY.dev'
[...]
tar: Error exit delayed from previous errors

ProblemType: Bug
Architecture: i386
Date: Mon Jul 30 22:25:13 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/file-roller
Package: file-roller 2.18.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: file-roller /home/vengmark/sandboxe.tgz
ProcCwd: /home/vengmark
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: file-roller
Uname: Linux l0b0land 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

l0b0 (victor-engmark) wrote :
l0b0 (victor-engmark) wrote :

Using "bsdtar -xvf" worked. I guess GNU tar should be upgraded...

Sunny Shin (shin-seu) on 2007-07-30
Changed in tar:
status: New → Confirmed
Sunny Shin (shin-seu) on 2007-07-30
Changed in tar:
status: Confirmed → Incomplete
Sunny Shin (shin-seu) wrote :

Thank you for taking the time to report this bug. I have couple of questions regarding this bug. Can I get the version of your BSDtar and GNUtar? Moreover, I wish to know that you try to unpack with real GNUtar or with just file-roller. Finally, I wish to know which version of Ubuntu you are using on. Anyhow, how did you compress the file on BSD? Thanks in advance and sorry for asking too many questions.

Changed in tar:
assignee: nobody → shin-seu
l0b0 (victor-engmark) wrote :

No problem! The reason I reported the bug from file-roller was that I'd tried tar first, and it failed in both.

I'm running Feisty Fawn.

I made the archive some weeks ago, but I'm pretty sure I used the equivalent of `bsdtar -cz`. If it may be of any help, the files in the archive are a set of Subversion repositories.

Here's the relevant shell output:

$ tar --version
tar (GNU tar) 1.16

$ bsdtar --version
bsdtar 1.3.1 - libarchive 1.3.1

$ uname -a
Linux removed 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

Sunny Shin (shin-seu) wrote :

Thank you for your additional information.
I tried what you did with the same version of bsdtar and gnutar as yours and I failed to reproduce your bug.
I wish to know which commands you used exactly.
In addition, if possible, then could you let me have your tarball file? It also would be helpful too.
Thank you in advance.

l0b0 (victor-engmark) wrote :

tgz file no longer available. If anyone wants to pursue this, I have a hunch the problem is related to Norwegian characters in the file names.

koyama (erik) wrote :

I was having exactly this issue when trying to transfer files in a tar archive from FreeBSD to Linux. I had file names in the archive containing Danish characters æøå which were causing the problem.

What worked for me was to create the tar archive on the FreeBSD machine with the --format=ustar option. Example:

>tar cfvz backup.tgz --format=ustar mydir

P.S. I did try to install the bsdtar on the Linux machine as suggested by l0b0 to see if it that utility could sucessfully extract the tar archive. While there were no error messages during extraction, the filenames were instead messed up. For example 'æ' would become 'æ'. Therefore that solution did not work.

Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed that the package version your bugging is updated in Maverick. Please update via www.ubuntu.com repost a detailed error report, and update the bug status. Thanks!

S. D. (akjag) wrote :

Confirmed, this bug exists in Maverick.

In my particular case, it is GNU tar which produces the above stated output, and it is the file-roller GUI which works properly.

My archive file, however, contains un-distributable sources from a colleague, and I cannot post it here.

S. D. (akjag) wrote :

I should mention, I'm running the x86_64 version of 10.10, and it is currently fully updated.

l0b0 (victor-engmark) wrote :

@akjag, could you please submit more details (tar version string, actual tar command) to further this bug? I stopped using FreeBSD years ago, so I won't be able to help anymore.

Toshio Kuratomi (toshio) wrote :

If this is the same bug as I'm experiencing using GNU tar on a different system, this tarfile should reproduce the problem:

http://pypi.python.org/packages/source/n/nose/nose-1.1.2.tar.gz#md5=144f237b615e23f21f6a50b2183aa817

Note that I'm not using Ubuntu -- I just came across this bug report while researching the same error messages and noticed that it lacked a reproducible test file.

crep4ever (romain-goffe) wrote :

Well, I came across this error message too with running ubuntu precise.

I've made a tar.gz archive on kubuntu (precise, 32b) from Dolphin's context menu "Compress as zip/tar" and tried to untar it on ubuntu (precise, 64b) through file-roller, then cli.

The archive is attached.

lanello (marco-lanini) wrote :

I confirm the bug, and i will try to explain what happened (sorry for my english)

A new customer called me to solve their "server" issues, the server was a fujitsu pc with a freenas installation, because of the limitations of freenas i have done the entire backup of data files and changed disks to bring up a ubuntu 12.04 lts x64 installation.

when i have finished to configure everything i got that bug when un-tarring the backup.

exactly same error of first post.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers