12 Jan
2009
12 Jan
'09
12:05 a.m.
On Sun, Jan 11, 2009 at 3:37 PM, Aaron Schaefer <aaron@elasticdog.com> wrote:
At the request of the upstream developer, I was attempting to change the md5sums in my tarsnap PKGBUILD (http://aur.archlinux.org/packages.php?ID=22963) to use sha256 instead, and ran across a couple of issues. The way makepkg works, when you set INTEGRITY_CHECK in makepkg.conf, those values effect BOTH the generation of the checksums and also the verification upon package compilation.
I addressed this "upstream" in an earlier patch, so this will be fixed in pacman 3.3.0: http://projects.archlinux.org/?p=pacman.git;a=commitdiff;h=496b687c3d4a56641... -Dan