From: William Josephson <jkw@eecs.harvard.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] invalid md5/sha1 on plan9port.tgz
Date: Wed, 2 Mar 2005 21:00:08 -0500 [thread overview]
Message-ID: <20050303020008.GB27404@mero.morphisms.net> (raw)
In-Reply-To: <422643E8.6060909@maZZoo.de>
On Wed, Mar 02, 2005 at 11:53:28PM +0100, Matthias Wenzel wrote:
> William Josephson wrote:
> >Try _plan9port.tgz. I don't know what the difference is --
> >the mtimes suggest russ changed something today.
>
> still not too convincing:
OK; I assume Russ will clear things up, but it just
looks to me like he's been moving some things around.
In any case, the hash you're using to compare is old:
it is dated Feb. 2 whereas the current plan9port.tgz
is dated Mar. 2. The shell script that updates the
tarball whenever there are changes to be pulled in
from CVS doesn't update the hash. From poking at
the logs it looks as though the newest one just pulled
in some bug fixes for libp9client that went into CVS
yesterday. It isn't as if the hash really helps since
the hash and the distribution are sitting on the same
filesystem in the first place. In any event, the
tarball dated Mar. 2 has the sha1 hash:
5d02e205d88667a6a063fac65111ddbc7b00d20a plan9port.tgz
-WJ
next prev parent reply other threads:[~2005-03-03 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-02 21:27 Matthias Wenzel
2005-03-02 22:23 ` William Josephson
2005-03-02 22:53 ` Matthias Wenzel
2005-03-03 2:00 ` William Josephson [this message]
2005-03-03 2:52 ` Russ Cox
2005-03-03 3:01 ` William K. Josephson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050303020008.GB27404@mero.morphisms.net \
--to=jkw@eecs.harvard.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).