Re: [Security-Discuss] broken hdlist.cz file for 10.0 i586

Vincent Danen <vdanen-7Aj/b8uzpy6AmYF/[email protected]>
Newsgroups gmane.linux.mandrake.security.general
Message-ID <[email protected]>
On Sep 18, 2004, at 5:13 AM, Michael Riß wrote:

>>> The current hdlist.cz file for 10.0 i586 from 15.09.2004,
>>> md5sum 8e296da50f9fe91fcb5a6b261fdb5e05,
>>> can't be decompressed with gunzip (CRC-error,
>>> length error).
>>> I checked the file on ftp.gwdg.de, ftp.proxad.net
>>> and the Mandrake corporate rsync server.
>>> Please regenerate and re-distribute.
>> A new advisory went out just now so new hdlists from today should be 
>> making their rounds.
>
> Right, the new hdlist.cz works.
> Any idea why the hdlist.cz files go corrupt on their way to the
> distribution server? The same happened to the AMD64 update hdlist.cz
> not even a month ago. This looks like a systematic failure.

To be honest, I really don't know.  I don't know if something is being 
changed somewhere in-transit, if there's a bad script monkeying with 
things occassionally, if there's a harddrive problem or filesystem 
problem somewhere...  it's difficult to track.  I know they're fine on 
my system (which is the "master"), and they're fine to the machine I 
upload to.  From that point, they go through one other machine before 
they hit the "primary mirrors" (IIRC) and it could be something on that 
machine or it could be the primary mirror that is having a problem, 
which would then replicate down to the mirrors that mirror from it.

> But nevertheless, the last week must have been very busy for you with
> all these updates und they all installed flawlessly on my 10.0 
> machines,
> good work!

Yeah...  it was rather time-consuming... =)  Lots of stuff to do.

-- 
*Please note gpg keyid FE6F2AFD has been replaced with keyid FEE30AD4*
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FEE30AD4 : 7F6C A60C 06C2 4811 FA1C  A2BC 2EBC 5E32 FEE3 0AD4}
PGP.sig (application/pgp-signature, 186 B) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.