[Slackbuilds-users] Desmume md5 mismatch
larryhaja at gmail.com
Wed Jan 20 02:01:40 UTC 2010
Yes, the md5sum should be aca40a8507d4104626da7086d451037b. It looks
like I forgot to change the md5sum before I repackaged the tarball.
But the weird thing is that I have a different md5sum that I pulled
off of sourceforge for version 0.9.5. The tarball that I initially
pulled didn't build the locale's or the libglade client. With this
different packaging of version 0.9.5 it now builds the libglade
client. They must have repackaged it after I uploaded the update to
SBo without changing the version number. Also, looking at the
creation date of the one I pulled it was 11/27/09 and the one now
available is 12/6/09.
Could one of the SBo admins please change the md5sum for desmume to
On Tue, Jan 19, 2010 at 7:04 AM, Manuel Mantilla
<mannynix at megared.net.mx> wrote:
> On 01/19/2010 05:09 AM, Marco Bonetti wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> Hello all,
>> I just got a Desmume md5 mismatch:
>> Expected: 0e877fe4b99d99502173efa6efae05b1
>> Found: aca40a8507d4104626da7086d451037b
>> I've manually downloaded and verified the tarball from
>> ovh.dl.sourceforge.net: the "Found" md5 corresponds, so they probably
>> repackaged the source code or it was just a small overlook or the ovh
>> mirror is out of sync (argh!). Is anyone experiencing similar issues?
> Yes, similar issues here.
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
More information about the SlackBuilds-users