| Summary: | Ark do not pack something with *.tar.* | ||
|---|---|---|---|
| Product: | [Applications] ark | Reporter: | FabiB <plusfabi> |
| Component: | general | Assignee: | Raphael Kubo da Costa <rakuco> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | adaptee |
| Priority: | NOR | ||
| Version: | 0.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
brokan files made by ark
same file made with terminal $ tar --create |
||
|
Description
FabiB
2011-12-30 19:47:25 UTC
Does it happen to any file you try to compress? What if you try to use another format? kompress to *.zip and *.rar works finde. all formats with .tar fails. for example *.tar.lzma, tar.gz, tar.bz Hmm. You are using the 4.8-RC1 packages from Kubuntu, right? What if you just try to open a tar archive which was not created by Ark? Are they also shown as empty? And if you create one a tar archive with Ark, does using `tar -tf` in the terminal also does not show any files? Created attachment 67278 [details]
brokan files made by ark
yep from kubuntu
no problems to open and extraxt files, not created from ark
no, will displayd correctly
tar files created with ark will shown this:
tar: Ignoriere unbekanntes Schlüsselwort „SCHILY.dev“ für erweiterten Kopfteil
tar: Ignoriere unbekanntes Schlüsselwort „SCHILY.ino“ für erweiterten Kopfteil
tar: Ignoriere unbekanntes Schlüsselwort „SCHILY.nlink“ für erweiterten Kopfteil
DSC00102.JPG
tar: Unerwartetes Dateiende im Archiv.
tar: Error is not recoverable: exiting now
well its mostly german, so here i will attach the archive packed by ark
Created attachment 67279 [details]
same file made with terminal $ tar --create
Interesting. Does Ark create archives like these with any file you pass to it (short text files, etc)? Can you also try creating an archive with bsdtar (bsdtar -cvzf foo.tar somefile) and see if it presents the same problem? all files i tested with are empty, yes. (*.jpeg, 300MiB *.mkv, a *.exe and *.odf) but if i choose a folder it works. i can extract files from bsdtar and without a single problem. like the the ones from normal tar ohh and btw happy new year :) (In reply to comment #7) > all files i tested with are empty, yes. (*.jpeg, 300MiB *.mkv, a *.exe and > *.odf) but if i choose a folder it works. Weird, I was able to create a .tar archive with that picture in the second attachment with Ark with no problems. > i can extract files from bsdtar and without a single problem. like the the ones > from normal tar What if you try to create an archive with bsdtar? Both Ark and bsdtar use libarchive and they both seem to extract files just fine; I'm trying to figure out if it is actually a problem with libarchive itself. What package version are you using? > ohh and btw happy new year :) Thanks, for you too :) (In reply to comment #8) > What if you try to create an archive with bsdtar? Both Ark and bsdtar use > libarchive and they both seem to extract files just fine; I'm trying to figure > out if it is actually a problem with libarchive itself. What package version > are you using? no problems to create a archive with bsdtar. libarchive is Version 2.8.5-5 Hmm, there has been no change in this part of the code between 4.7 and 4.8. Do you know if there has been any update to libarchive in Ubuntu lately too? I'd appreciate if you could contact your distro's folks and check if somebody else can reproduce the issue (it all works fine here on FreeBSD). (In reply to comment #4) When trying to unpack this archive using tar from terminal, I get error messages similar to what I have posted in bug 289307. Hope that helps. Hmm, this bug looks like a duplicate of the one you mentioned. Let's keep track of it there. *** This bug has been marked as a duplicate of bug 289307 *** |