From: "H. Peter Anvin" <hpa@transmeta.com>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Andries.Brouwer@cwi.nl, ftpadmin@kernel.org,
jmd@foozle.turbogeek.org, linux-kernel@vger.kernel.org
Subject: Re: kernel.org signer broken?
Date: Fri, 12 Jan 2001 12:36:41 -0800 [thread overview]
Message-ID: <3A5F6AD9.8DAD6ABC@transmeta.com> (raw)
In-Reply-To: <UTC200101121456.PAA105954.aeb@ark.cwi.nl> <3A5F67D4.D096B191@transmeta.com> <20010112223415.J25659@mea-ext.zmailer.org>
Matti Aarnio wrote:
>
> On Fri, Jan 12, 2001 at 12:23:48PM -0800, H. Peter Anvin wrote:
> > Andries.Brouwer@cwi.nl wrote:
> > > > The signature on man-pages-1.34.tar.gz is bad:
> > >
> > > Hmm, thought I had corrected that already.
> > > Is it correct now?
> > >
> > > Andries
> >
> > Because an updated signature has the same timestamp and size, it can take
> > up to 24 hours for it to hit ftp.kernel.org, and even longer to propagate
> > to the mirrors, unfortunately.
>
> Ok, then rsync won't find it either unless driven in
> file CRC verification mode (which is not usual...)
>
Right; kernel.org does that once a day.
> You *must* change its time (e.g. with touch).
>
Unfortunately, you can't -- because the signer relies on the timestamp to
know if the file it is mirroring has changed.
Probably the best solution is to touch the original file.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-12 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 14:56 kernel.org signer broken? Andries.Brouwer
2001-01-12 20:23 ` H. Peter Anvin
2001-01-12 20:34 ` Matti Aarnio
2001-01-12 20:36 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-12 0:08 Jeremy M. Dolan
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=3A5F6AD9.8DAD6ABC@transmeta.com \
--to=hpa@transmeta.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=ftpadmin@kernel.org \
--cc=jmd@foozle.turbogeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
/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