Hi,

while I was trying to install TeTeX I encountered a problem with
mismatching digests. So I went on, commented out my favourite mirrors for
downloading and pulled the file directly from Oregonstate after deleting
the first downloaded file. The digest was the same as before: The wrong
one. What to do now? File a bug report?

BTW:
niels 15:00 ~ > gzip -t /usr/portage/distfiles/tetex-texmf-2.0.2.tar.gz
gzip: /usr/portage/distfiles/tetex-texmf-2.0.2.tar.gz: not in gzip format


--
Muskote Nr.: 102
Zweifel muß nichts weiter sein als Wachsamkeit, sonst kann er gefährlich werden.
Lichtenberg

So anyway, it was like, 15:04 CET Jan 20 2004, you know? Oh, and, yeah,
Niels Burmeister was all like, "Dude,

> while I was trying to install TeTeX I encountered a problem with
> mismatching digests. So I went on, commented out my favourite mirrors for
> downloading and pulled the file directly from Oregonstate after deleting
> the first downloaded file. The digest was the same as before: The wrong
> one. What to do now? File a bug report?

You could try fetching the source directly from the.. source, as it were.

<ftp://cam.ctan.org/tex-archive/systems/unix/teTeX/current/distrib/>

fwiw:

d3bdb96f9077e43b2115d3cc471743b3 tetex-texmf-2.0.2.tar.gz

hth.

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
15:37:56 up 11 days, 5:29, 6 users, load average: 2.18, 2.07, 2.01
$ cat /dev/bollocks Registered Linux user #261729
generate sexy architectures

Try running "emerge sync" again. There was a problem like this a few
months back with a font package.

On Tue, 20 Jan 2004 15:04:03 +0100, Niels Burmeister
<n-burmeister@foni.net> wrote:

>Hi,
>
>while I was trying to install TeTeX I encountered a problem with
>mismatching digests. So I went on, commented out my favourite mirrors for
>downloading and pulled the file directly from Oregonstate after deleting
>the first downloaded file. The digest was the same as before: The wrong
>one. What to do now? File a bug report?
>
>BTW:
>niels 15:00 ~ > gzip -t /usr/portage/distfiles/tetex-texmf-2.0.2.tar.gz
>gzip: /usr/portage/distfiles/tetex-texmf-2.0.2.tar.gz: not in gzip format

Am Tue, 20 Jan 2004 15:40:38 +0100 schrieb Johan Lindquist:

> So anyway, it was like, 15:04 CET Jan 20 2004, you know? Oh, and, yeah,
> Niels Burmeister was all like, "Dude,
>
>> while I was trying to install TeTeX I encountered a problem with
>> mismatching digests. So I went on, commented out my favourite mirrors for
>> downloading and pulled the file directly from Oregonstate after deleting
>> the first downloaded file. The digest was the same as before: The wrong
>> one. What to do now? File a bug report?
>
> You could try fetching the source directly from the.. source, as it were.
>
> <ftp://cam.ctan.org/tex-archive/systems/unix/teTeX/current/distrib/>

yeah that helped, should I inform someone in charge that corrupted files
are around?

--
Muskote Nr.: 19
Die Sinne trügen nicht, das Urteil trügt.
J.W. von Goethe

So anyway, it was like, 19:52 CET Jan 20 2004, you know? Oh, and, yeah,
Niels Burmeister was all like, "Dude,

>>> [mismatching digests]

[..]

> should I inform someone in charge that corrupted files are around?

I don't really know, but I guess you should. Right now, however, all
the tetex-2.0.2 files look right to me, 'emerge -fv tetex' yields three
fetched files with the correct md5 sums, all apparently fetched from
gentoo.oregonstate.edu.

#v+
-----8<-----
panther root # emerge -vf tetex
Calculating dependencies ...done!

[..]

Connecting to gentoo.oregonstate.edu[128.193.0.3]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 22,909,537 [application/x-tar]

100%[====================================>] 22,909,537 232.61K/s ETA 00:00

12:46:45 (162.24 KB/s) - `/usr/portage/distfiles/tetex-texmfsrc-2.0.2.tar.gz' saved [22909537/22909537]

>>> tetex-texmfsrc-2.0.2.tar.gz MD5 ;-)
>>> md5 src_uri ;-) tetex-src-2.0.2.tar.gz
>>> md5 src_uri ;-) tetex-texmfsrc-2.0.2.tar.gz
>>> md5 src_uri ;-) tetex-texmf-2.0.2.tar.gz
----->8-----
#v-

*shrugs*

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
12:44:59 up 12 days, 2:36, 6 users, load average: 2.00, 2.07, 2.04
$ cat /dev/bollocks Registered Linux user #261729
morph web-enabled bandwidth

Captains log; stardate Wednesday 21 January 2004 06:50 am, Lieutenant Johan Lindquist
reported that.......

> So anyway, it was like, 19:52 CET Jan 20 2004, you know? Oh, and, yeah,
> Niels Burmeister was all like, "Dude,
>
>>>> [mismatching digests]
>
> [..]
>
>> should I inform someone in charge that corrupted files are around?
>
> I don't really know, but I guess you should. Right now, however, all
> the tetex-2.0.2 files look right to me, 'emerge -fv tetex' yields three
> fetched files with the correct md5 sums, all apparently fetched from
> gentoo.oregonstate.edu.
<snip>

I wouldn't bother sending anything anywhere, this is usually just a hickup with your
ISP or that of the server dishing up the files. Theres nothing wron with the copy
on the server end, just an error in the transfer to you.

If your still having issues downloading it, check the file size against the reported
size. If it regularly kills at the same spot in the download, its possible your ISP
has capped your download limit
--
Shan Destromp
---
OS: GNU/Linux 2.4.22-gentoo-r5
Processor: AuthenticAMD i686
----
BOFH Excuse #188: ..disk or the processor is on fire.

So anyway, it was like, 16:51 CET Jan 21 2004, you know? Oh, and, yeah,
Shan Destromp was all like, "Dude,

> I wouldn't bother sending anything anywhere, this is usually just a hickup with your

Would you mind terribly setting your line length to something sensible?

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
17:10:18 up 12 days, 7:01, 6 users, load average: 2.28, 2.16, 2.11
$ cat /dev/bollocks Registered Linux user #261729
utilize seamless action-items

Captains log; stardate Wednesday 21 January 2004 11:11 am, Lieutenant Johan Lindquist
reported that.......

> So anyway, it was like, 16:51 CET Jan 21 2004, you know? Oh, and, yeah,
> Shan Destromp was all like, "Dude,
>
>> I wouldn't bother sending anything anywhere, this is usually just a hickup with
>> your
>
> Would you mind terribly setting your line length to something sensible?
>

And just what do you consider sensible to be? Its at the default length that knode
chose......
--
Shan Destromp
---
OS: GNU/Linux 2.4.22-gentoo-r5
Processor: AuthenticAMD i686
----
BOFH Excuse #283: Lawn mower blade in your fan need sharpening

So anyway, it was like, 17:32 CET Jan 21 2004, you know? Oh, and, yeah,
Shan Destromp was all like, "Dude,
> Captains log; stardate Wednesday 21 January 2004 11:11 am, Lieutenant Johan Lindquist
> reported that.......

>> Would you mind terribly setting your line length to something
>> sensible?
>
> And just what do you consider sensible to be? Its at the default
> length that knode chose......

Sensible as in what usenet guidelines suggest. I'd go with 72, that
allows for a few levels of quoting even by braindead nntp clients
while still allowing for terminal-based readers to render without
imposed wrapping.

Feel free to google for trivia, it's pretty well covered.

--
Time flies like an arrow, fruit flies like a banana. Perth ---> *
17:41:47 up 12 days, 7:32, 6 users, load average: 2.07, 2.13, 2.13
$ cat /dev/bollocks Registered Linux user #261729
disintermediate dynamic portals