Can I make a request to please file a bug report about these rather than
just fixing the md5sums. In this case it looks like that package was
recompressed after release without any actual changes (the file creation
date is a month after release...), but I have seen stupid upstream
people make a quick bugfix and replace the tarball hoping no-one has
used the previous tarball. Especially in the later case, it is
important the maintainer checks why the checksum differs from what they
use to build the package.
Allan
-------- Original Message --------
Subject: [arch-commits] Commit in dialog/trunk (PKGBUILD)
Date: Fri, 14 May 2010 19:41:28 -0400 (EDT)
From: Eric Bélanger <[email protected]>
Reply-To: Arch Linux packaging commits <[email protected]>
To: [email protected]
Date: Friday, May 14, 2010 @ 19:41:28
Author: eric
Revision: 80291
fixed md5sums
Modified:
dialog/trunk/PKGBUILD
----------+
PKGBUILD | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Modified: PKGBUILD
===================================================================
--- PKGBUILD 2010-05-14 23:31:05 UTC (rev 80290)
+++ PKGBUILD 2010-05-14 23:41:28 UTC (rev 80291)
@@ -12,7 +12,8 @@
license=('GPL')
depends=('ncurses>=5.6-8')
source=(ftp://invisible-island.net/${pkgname}/${pkgname}-$_pkgver.tgz)
-md5sums=('ada629276646b462aaab1e734f626eb6')
+md5sums=('3d62219658fdddf3c6247fb45831a5d0')
+sha1sums=('ebf5fa7419601425a10446215cc477d92c191c5a')
build() {
cd ${srcdir}/$pkgname-$_pkgver
