The current phpmyadmin tar download SHA256 hash does not match the download site value. The published hash for ver 4.9.3 is f75c5e11b076176436653c6138d8185b0351b02a1bf8c5069ec8d0af254911df but I get this :
downloads % shasum -a 256 phpMyAdmin-4.9.3-english.tar
514219cdf85819748e5f89584ccb5e0d181c27262f7da8950918133706d3d8fe.
Unfortunately the tar unpacked automatically. Do I now have a hacked file?
Yes, you have another download,
It looks like you have downloaded this package phpMyAdmin-4.9.3-english.tar.gz when i generate SHA256 i got f75c5e11b076176436653c6138d8185b0351b02a1bf8c5069ec8d0af254911df which is same as published on website.
Even i checked all 4.9.3 versions hash but could not find your package hash 514219cdf85819748e5f89584ccb5e0d181c27262f7da8950918133706d3d8fe
With Jaikey Sarraf's help I found my problem. After the the .tar.gz file is downloaded macOS Catalina immediately unpacked the .tar.gz and trashed it replacing it with just the .tar. I did not notice the switch so did SHA156 on the .tar which created my problem. Dragging the .gz out of trash and running SHA256 gives the correct hash.
We had caching issues with our CDN and now they are solved
Please try again and report if you find that the hash does not match
https://github.com/phpmyadmin/website/issues/84
Related
I'm having some problems when I'm going to unzip this type of file, I've tried several packages,
I'm trying to download a package (my own package manager), I'm trying to download from "registry.npmjs.com" I get the version and download the tarball (tgz.gz)
Example :
DOWNLOAD https://registry.npmjs.com/(package)/-/(package)-(version).tgz.gz (I managed to solve this problem)
UNPACK (package)-(version).tgz.gz (I didn't get this step, how do I solve it?)
The problem is when I'm going to unzip can you help me with this?
I am aware of this page: https://unity3d.com/get-unity/download/archive but the downloads are only for windows and mac and despite having it installed, the "unity hub" button does nothing. I have found places to download even older versions like 2018 but I need version "2019.2.5f1". Can I download and use the mac version? Is there somewhere I can download this compiled for Linux without using unity hub? Thanks for any help.
The UnityHub link will have a version hash in it which is unique across platforms. With that hash, you can build the Linux version download URL yourself.
In your case, you need 2019.2.5f1, which gives you the UnityHub link unityhub://2019.2.5f1/9dace1eed4cc
You can download the tarball at the following URL:
https://download.unity3d.com/download_unity/9dace1eed4cc/LinuxEditorInstaller/Unity.tar.xz
The unity-editor package is a good one to modify the PKGBUILD file for if you'd like to install an arbitrary version as a proper package.
Clone the project
Tweak the PKGBUILD version and hash to the one you want
Run makepkg -g to generate the checksum for the new tarball
Insert the new checksum into the PKGBUILD
Run makepkg -p PKGBUILD to compile the package
Run sudo pacman -U ./unity-editor-${pkgversion}.pkg.tar to install your newly built package.
If anyone is having this issue and want to download older versions from unityhub, there is solution that worked for me :
Go to unity download archive
Copy redirection link from the green button (you can right click it and select "Open Link in new tab", and then copy it from here)
Once you have the link, open up your terminal and go to location in which you have UnityHub.AppImage
Simply use this command : ./UnityHub.AppImage link where link is what you copied (for example ./UnityHub.AppImage unityhub://2019.3.13f1/d4ddf0d95db9 to download 2019.3.13 version of uinity)
I have two of the hashes:
89d6087839c2 Unity 2019.3.1f1
b9898e2d04a4 unity 2019.2.16f1
I want to install scala at here and I'm concerned about which one to download: zip or tgz. What is a difference between these, and what are the use cases?
They are different archive formats. They are used because it saves bandwidth and because they bundle files.
Zip is more common on Windows and there is a decompressor preinstalled.
Tgz is gzip + tar and is common on Linux. There is also a decompressor preinstalled, most of the time. Also known as .tar.gz.
If you're on Windows I'd download the zip or the installer, as you don't have to install a third party program to open it. If you're on Linux I recommend installing scala through your package manager.
I am trying to run some face frontalization code (using Python3 on Windows10), the code uses opencv and dlib and requires a file called shape_predictor_68_face_landmarks.dat. The code tries to automatically download it and then unzip it but it fails to unzip giving an unexpected end of archive error. I tried to use WinRaR to repair the file (which I also tried manualy downloading from http://sourceforge.net/projects/dclib/files/dlib/v18.10/shape_predictor_68_face_landmarks.dat.bz2) but it says it can only repair .zip and .rar files.
Does anyone know where I can download the uncompressed .dat file from? Or alternatively how I can repair a damaged .bz file in Windows?
The file is available at
http://dlib.net/files/shape_predictor_68_face_landmarks.dat.bz2
I downloaded it and verified that extraction works. The file is smaller than the one used in the previous version, but I think that is due to improvements.
In case this does not work, let me (or Davis King, who maintains the dlib blog) know so that you can get the uncompressed version.
Downloading using the CLI is a lot easier.
wget http://dlib.net/files/shape_predictor_68_face_landmarks.dat.bz2
To decompress the compressed file you just downloaded, use the following command
bzip2 -d shape_predictor_68_face_landmarks.dat.bz2
As mentioned above, download shape_predictor_68_face_landmarks.dat
from here. But while downloading, downloads gets failed(i faced this issue). So, if you're also facing the same issue, then i recommend to download it via command-line:
$ wget link
I created a bunch of zip files on my computer (Mac OS X) using a command like this:
zip -r bigdirectory.zip bigdirectory
Then, I saved these zip files somewhere and deleted the original directories.
Now, when I try to extract the zip files, I get this kind of error:
$ unzip -l bigdirectory.zip
Archive: bigdirectory.zip
warning [bigdirectory.zip]: 5162376229 extra bytes at beginning or within zipfile
(attempting to process anyway)
error [bigdirectory.zip]: start of central directory not found;
zipfile corrupt.
(please check that you have transferred or created the zipfile in the
appropriate BINARY mode and that you have compiled UnZip properly)
I have since discovered that this could be because zip can't handle files over a certain size, maybe 4 gigs. At least I read that somewhere.
But why would the zip command let me create these files? The zip file in question is 9457464293 bytes and it let me make many more like this with absolutely no errors.
So clearly it can create these files.
I really hope my files aren't lost. I've learned my lesson and in the future I will check my archives before deleting the original files, and I'll probably also use another file format like tar/gzip.
For now though, what can I do? I really need my files.
Update
Some people have suggested that my unzip tool did not support big enough files (which is weird, because I used the builtin OS X zip and unzip). At any rate, I installed a new unzip from homebrew, and lo and behold, I do get a different error now:
$ unzip -t bigdirectory.zip
testing: bigdirectory/1.JPG OK
testing: bigdirectory/2.JPG OK
testing: bigdiretoryy/3.JPG OK
testing: bigdirectory/4.JPG OK
:
:
file #289: bad zipfile offset (local header sig): 4294967295
(attempting to re-compensate)
file #289: bad zipfile offset (local header sig): 4294967295
file #290: bad zipfile offset (local header sig): 9457343448
file #291: bad zipfile offset (local header sig): 9457343448
file #292: bad zipfile offset (local header sig): 9457343448
file #293: bad zipfile offset (local header sig): 9457343448
:
:
This is really worrisome because I need these files back. And there were definitely no errors upon creation of this zip file using the system zip tool. In fact, I made several of these at the same time and now they are all exhibiting the same problem.
If the file really is corrupt, how do I fix it?
Or, if it is not corrupt, how do I extract it?
Unzip below 6 seemingly fails, use
jar -xf <zipfile>
if you have java installed, or yet another unzip before you write the file off.
See: https://serverfault.com/questions/235139/how-to-unzip-files-bigger-than-4gb
Try 7z x
I had the same issue with unzip %x on Linux for a .zip file larger than 4GB, compounded with a only DEFLATED entries can have EXT descriptor error.
The command 7z x resolved all my issues though.
Be careful though, the command 7z x will extract all files with a path rooted in the current directory. The option -o allows to specify an output directory.
I had a similar problem backing up a 12GB directory before performing a hard disk format. Funnily enough I used the same command as you.
I read around and found suggestions to run:
zip -F
and
zip -FF
to try to fix the file.
Unfortunately these did not work and I still received errors.
After looking around some more, I found the ditto command and it worked perfectly against my original (untouched) zip file:
ditto -x -k original-file.zip dst-directory
-x to extract an archive
-k Specifies it to be a PKZip archive instead of the default CPIO
After using this command, I successfully extracted all of the files.
The built-in macOS Archive Utility (which is the default used when you select something in Finder and go to File -> Compress "<item>") also creates "corrupt" archives when a file in the archive is over 4 gigabytes in size, the size of the archive itself is over 4 gigabytes or you are trying to compress more than 65536 files into a single zip. This happens because it doesn't use the Zip64 extension format.
This is mentioned on https://apple.stackexchange.com/questions/221020/large-zip-files-created-in-os-x-cannot-be-opened-in-windows and is well covered in the "Apple Archive Utility (and ditto) and very large ZIP archives" 2009 blog post for the now defunct Springy utility. You can also see the 7-Zip folks are aware of the Apple tools creating corrupt zips issue too.
But why would the zip command let me create these files?
Strictly speaking, the original zip format only supports archives up to 2^32 bytes (4GiB) and which do not contain files that were originally larger than 4GiB and you there must be less than 65535 files. Because the command line version of the Infozip command tools shipped with OSX up to version OSX 10.11 (El Capitan) was no newer than 5.52, it could only produce non-conformant archives if you forced it to exceed the original zip format limits. Infozip 6.0 and above know how to make Zip64 archives and that standard has much higher limits. The Infozip 6.0 command line tools started shipping with macOS 10.12 (Sierra). In 2014 when the question was originally asked the newest OSX was 10.10 (Yosemite).
As stated above, even in macOS 10.15 (Catalina) the GUI Archive Utility still creates such "corrupt" zips.
If the file really is corrupt, how do I fix it?
It's corrupt in the sense that its non-conformant and will cause a lot of conformant tools to choke. You could extract (it see below) and then compress again with a tool that knows how to make Zip64 files...
Or, if it is not corrupt, how do I extract it?
Technically, all of the data from the files that have been compressed is still in the archive but the headers that allow fast listing of the zip's content are broken. Such zips can be a struggle to work with when using other tools (even testing such a zip with the command line unzip tool on the same version of macOS can indicate issues like invalid compressed data to inflate / bad zipfile offset (local header sig)).
To get at the files of such zips you need to use a program that will quietly just extract whatever was compressed without checking for conformance or trying to check/list the files. Examples of tools that can do this are:
macOS Archive Utility GUI tool
macOS command line tool ditto
7-zip
Java's jar tool
Infozip based tools won't be able to work with or repair such zip files once you've made such a problem zip file.
you can use
zip -FF corrupted.zip --out fixed.zip
replace corrupted.zip by your zip with issues
replace fixed.zip by the name of new .zip file fixed
I have faced exactly the same issue when I tried to unzip zip files of huge sizes (~7GB). I was damn sure that there was no error while copying the zip files to the server. (I double-checked it with rsync).
Depending on your situation, the solution is:
1) If you're doing this in a local machine, right click on the zip file and give Extract Here, this will work for (.zip) files of any size.
2) If your zip files are in a remote server, first load the server filesystem locally using sftp (sftp://username#server.url.address.com). After that just navigate to the directory and again do the same thing as you did in (1). i.e. right click on the zip file and extract it.
Might not be the best solution but that's one way of doing it.