[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] 1.16.0 still no go

To: mint_list <mint@fishpool.com>
Subject: Re: [MiNT] 1.16.0 still no go
From: Frank Naumann <fnaumann@mail.cs.uni-magdeburg.de>
Date: Sat, 7 Aug 2004 08:44:17 +0200 (CEST)
Delivered-to: mint@fishpool.com
Delivered-to: mint@lists.fishpool.fi
In-reply-to: <Pine.NEB.4.60.0408070011001.15339@panix1.panix.com>
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <Pine.NEB.4.60.0408070011001.15339@panix1.panix.com>
Sender: mint-bounce@lists.fishpool.fi

Hello!

What I saw on my screen when trying to unpack these things was:

gzip: freemint-1.16.0-beta.tar.gz: invalid compressed data--format violated

What's why for every file of the 1.16.0 beta release an .md5 file existthat hold the md5 checksum. Just calculate the md5 checksum of thedownload file and compare to see if the files are really identical

(with md5sum <file>, part of textutils package).

So, will somebody please look at those kernel files on the Sparemint site? Ithink there are some problems there.

These files are definitly ok. Are you sure you downloaded them correctlyas binary?



Regards,
Frank

--
ATARI FALCON 060 // MILAN 060
-----------------------------------------
http://www.cs.uni-magdeburg.de/~fnaumann/
e-Mail: fnaumann@freemint.de

Follow-Ups:
- Re: [MiNT] 1.16.0 still no go
  - From: Jim DeClercq <jimd@panix.com>

References:
- [MiNT] 1.16.0 still no go
  - From: Jim DeClercq <jimd@panix.com>

Prev by Date: Re: [MiNT] 1.16.0 still no go
Next by Date: Re: [MiNT] 1.16.0 still no go
Previous by thread: Re: [MiNT] 1.16.0 still no go
Next by thread: Re: [MiNT] 1.16.0 still no go
Index(es):
- Date
- Thread