You are not logged in.
when I attempt to create a installable package from the aur md5deep, I get this error:
Validating source files with md5sums...
md5deep-4.3.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
In detail, this is what I did as non root user:
1. downloaded this https://aur.archlinux.org/packages/md/m … eep.tar.gz
2. put it in ~/builds
3. tar xvzf md5deep-4.3.tar.gz in above dir
3. changed into the md5deep dir.
4. makepkg -s
5. got the error above.
I have successfully built other packages using aur.
Anyone see what I am doing wrong?
Maybe someone try to build this and let me know if the problem appears for others?
Any tip or help appreciated.
Steve.
Last edited by stevepa (2013-07-05 22:21:51)
Arch - LVM - ext4 - gnome (T60p 14.1 1400p x86_64), (T60 15 flexview 1400p i686)
Offline
I think the irony attracted me to this one - a checksum failing for a checksum tool
But I just tried it and it worked fine, it looks like you just had a corrupted download. Have you tried downloading it again fresh?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Anyone see what I am doing wrong?
Maybe someone try to build this and let me know if the problem appears for others?Any tip or help appreciated.
Steve.
You are doing nothing wrong. You are being protected as intended.
What has happened is that a source file you have downloaded is not the same file that was downloaded by he who created the PKGBUILD.
One of a few things have happened:
The upstream author has changed something (bug fix) and replaced the original file. In this case, you are trying to build something that is different than that which was tested by the packager.
-or-
There is a man in the middle who is attempting to trick you into running a version of the program with malicious code in it. Either you have to find a real version, or verify by reading the code that it is okay (not recommended)
-or-
The file you downloaded is just corrupted. Try deleting the downloaded source and try again.
What can you do? If you trust the downloaded file, perform a makepkg -g.
It will download the source (if necessary) and will spit out the MD5 checksums for the files. Take those md5sums and edit the PKGBUIKLD; replace the md5sums in the file with the new ones you generated. Then, try a makepkg again to build it this time.
Also, be sure to file a bug report in the AUR.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
@Trilby, I noticed the irony also! See below :-(
@ewaller, i removed all previous work, redownloaded, with same results. I will take a stab atthe makepkg -g option as it might be a good learning opportunity.
To see if my system is suffering some kind of overall issue, I built a high popularity AUR package libjepg6 WITHOUT ISSUE !
Crazy stuff here!
Steve.
Arch - LVM - ext4 - gnome (T60p 14.1 1400p x86_64), (T60 15 flexview 1400p i686)
Offline
first of all, what doe's the maintainer say about it?
second, i do makepkg -g and replace it in PKGBUILD in these cases
just like you.
ezik
Offline
i do makepkg -g and replace it in PKGBUILD in these cases
Or use 'updpkgsums':
$ updpkgsums -h
usage: updpkgsums [buildfile]
-h, --help display this help message and exit
-V, --version display version information and exit
updpkgsums will perform an in place update the checksums in the
path specified by [buildfile], defaulting to PKGBUILD in the current
working directory.
Offline
performed these steps
1. makepkg -g
2. updpkgsums
3. makepkg
4. #pacman -U [pkg name]
and it installed.
Thanks to all.
Steve.
Last edited by stevepa (2013-07-05 22:25:06)
Arch - LVM - ext4 - gnome (T60p 14.1 1400p x86_64), (T60 15 flexview 1400p i686)
Offline
I think it's enough to run either 'makepkg -g' or 'updpkgsums' :-)
Offline
Oh, my curiosity is getting the best of me. Why do I not get an error building this on either my i686 or 64 computer? How can the same checksum for the same tarball work on one computer and fail on another?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I have no issues either:
==> Retrieving sources...
-> Downloading md5deep-4.3.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 1382k 100 1382k 0 0 429k 0 0:00:03 0:00:03 --:--:-- 683k
==> Validating source files with md5sums...
md5deep-4.3.tar.gz ... Passed
==> Validating source files with sha1sums...
md5deep-4.3.tar.gz ... Passed
==> Validating source files with sha256sums...
md5deep-4.3.tar.gz ... Passed
==> Validating source files with sha512sums...
md5deep-4.3.tar.gz ... Passed
==> Extracting sources...
-> Extracting md5deep-4.3.tar.gz with bsdtar
==> Starting build()...
Evey checksum is correct.
Offline
To make a long story short, it finally built normally.
I removed the md5deep build directory.
I uninstalled binary with pacman -R
I un-tar'ed and makepkg -s it, and it ran without error.
I installed it with pacman -U <pkg>
I don't really have a good feeling about all this but things seem ok now.
Thanks for the help on this issue.
Steve.
Arch - LVM - ext4 - gnome (T60p 14.1 1400p x86_64), (T60 15 flexview 1400p i686)
Offline