The accepted convention is to suffix the archive file with the compression suffix.įor example, when using the gzip compression (using the -z option), the file should bear the. The tar utility allows you to create archive files using various compression algorithms such as xz, gzip, and bzip2. W: The -w option verifies an archive file. j: Create an archive file using the bzip2 compression z: Creates a tar file using gzip compression r: This updates a file or directory located inside a. u: This archives a file and then adds it to an existing archive file. t: This lists all the files inside an archive file. v: This prints verbose information for any tar operation on the terminal. f: Specifies the filename of the archive file. x: The option extracts the archive file. The tar command provides the following options: Let’s check out some of the options that go along with the tar command. I don't know if it's just an IZArc issue, but as it seems to work with older releases, there might also be some unknown issue in publishing the newer releases.$ tar So this is just to let you know that there is some strange behaviour in some cases. (Note: Additionally I also tried to delete the extractions with the strange files in it, which I made under Windows, now within Linux Mint's data manager, and this also worked fine.)įor my purposes there seems to be a workaround with Linux Mint. So finally I took the extraction back to Windows for testing deleting it, and it worked, so probably there are no files just ending with a dot and without any timestamp like with the extraction with IZArc on Windows. In the end I tried my luck with the extraction manager of Linux Mint 18.2 (updated), extracting mediawiki-1.35.0.tar.gz, and there was no similar error message like on IZArc. (Note: I have not tried it with 1.34.1 to 1.34.3 or any else release new since January 2020 yet.) Which leads me to the conclusion that something could have happened between the release of 1.34.0 and that of 1.34.4 and 1.35.0 which might cause this error. So I tried a new download of the same file mediawiki-1.34.0.tar.gz, and extraction also worked fine. I also tried to extract an older download, mediawiki-1.34.0.tar.gz (downloaded in early 2020), and it worked fine on IZArc. I found out that there were several files just ending with a dot and without any timestamp which I just could delete using the command line on Windows (which is useful, but do it with hundreds of files in different directories. In the end I chose with different extractions both overwriting all and not overwriting anything.īecause this happened the first time ever since I have used IZArc (10 or 15 years?), I was unsure if there was an error either in the origin download files or with the extraction which might cause troubles when making an installation of MediaWiki, so I tried to delete the different extractions - but it did not work. When trying to extract mediawiki-1.35.0.tar.gz and mediawiki-1.34.4.tar.gz with IZArc 4.4 on Windows 10, after about the half of extraction the extracting programme comes with messages to overwrite existing files with files of (of course) the same name, but size 0 and a slightly different timestamp (00:01 instead of 00:01:00, as far the extracting programme indicates).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |