Postponed (maintainer needs more info)
Project:
Configuration Management
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Feb 2013 at 00:09 UTC
Updated:
10 May 2013 at 16:51 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dagmarCould you attach the tar file you are trying to import? Thanks.
Comment #2
alexverb commentedI was having the same problem. But I haven't been able to replicate it yet. It seems for one reason or another a file named xt',) gets generated and included in the tar. This causes problems on untar.
I've attached a zip of the tar. Looks like DO is not allowing tar as a file extension.
Comment #3
davidpetit commentedI had the same problem and I found that I could not open the tar neither.
So I tryed other exports. I found that when I don't export views settings, the tar is good.
It's only when I put some specific views in the export that the tar does not work.
After many attempts, I can say that the only views making it not work are those using "entity views attachment" module.
Hope this can help.
Comment #4
jorditr commentedI'm not exporting views and I can't open on my desktop the tar neither...
Comment #5
mvwensen commentedSame issue over here, on my local WAMP a tar-file is generated correctly and on a LAMP testing server it will create a corrupt tar-file.
If i open the tar files in a text-editor the corrupt variant is starting with "0a63" and the correct working version "63**" if i remove the first two characters (0a) from the corrupt file, i can open it but it still gives me an archive error. I'm not very skilled in tar's, headers and the php pack() function, I tried to set different headers and changed the buffer sizes but it still won't generate a correct .tar-file.
I personally can bypass it by using WAMP on Windows for now.