mcrypt seems to have moved as well and is at 2.6.4

[Terry Chan]

I've fixed the mcrypt module in moonbase now.

It uses the planetmirror cache for mcrypt-2.6.4.tar.gz with the correct file
size of 383865 bytes and the md5sum of 5a011846fd0f166428c8d97359aaa6b3.

Until the mcrypt developer gets their act together and uploads a proper tar.gz
file to sourceforge, the lunar module for mcrypt should NOT download the source
from ANY sourceforge mirror.

I'll also make sure that the lunar cache has the correct mcrypt tar.gz file
as a backup location.

Terry Chan
--------------------------------------------------------------
On Sun, Sep 21, 2003 at 02:45:16PM -0400, Dennis Veatch wrote:
> On Sunday 21 September 2003 02:34 pm, Auke Kok wrote:
> 
> > >
> > > Ok I'm dumb as a rock. If I change DETAILS to planetmirror, mcrypt md5sum
> > > for it fails and lin blows up.
> > >
> > > If I use the 1.7MB file it lins fine.
> > >
> > > So ya, I'm stupid.
> >
> > ~ # file /var/spool/lunar/mcrypt-2.6.4.tar.gz
> > /var/spool/lunar/mcrypt-2.6.4.tar.gz: tar archive
> >
> > it should have said GZIP compressed data!
> >
> > sofar
> 
> Well that's the problem. If I used the "correct" file (383865), lin mcrypt 
> fails md5sum. So I cannot do a file  /var/spool/lunar/mcrypt-2.6.4.tar.gz 
> because it does not exist. Doing it manually with wget (the 383865 file), yes 
> it does say gzip compressed data.
> 
> If I use the 1.7MB file, md5sum does not fail and lin is successful. 
> 
> So explain to me how I can successfully lin the "correct file" and avoid the 
> md5sum failure.
> 
>