Skip to Content.
Sympa Menu

sm-grimoire - Re: [SM-Grimoire] (no subject)

sm-grimoire AT lists.ibiblio.org

Subject: Discussion of Spells and Grimoire items

List archive

Chronological Thread  
  • From: Seth Woolley <seth AT tautology.org>
  • To: "Julian v. Bock" <julian AT openit.de>
  • Cc: sm-grimoire AT lists.ibiblio.org
  • Subject: Re: [SM-Grimoire] (no subject)
  • Date: Fri, 31 Jan 2003 03:05:59 -0800 (PST)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 31 Jan 2003, Julian v. Bock wrote:

> Hi
>
> >>>>> "SW" == Seth Woolley <seth AT tautology.org> writes:
>
> SW> I updated a whole bunch of md5s in devel and test. p4 sync up
> SW> everybody (developers) and make sure I didn't royally screw
> SW> anything up.
>
> I hope you didn't just update without checking if they didn't match.
> if the yare just updated they don't make any sense.

I only touched those that differed from my local cache.

I also manually added MD5s to all spells missing one. So at this point in
time, we should have all the spells with "documented" md5s, even if their
PRE_BUILDs mess up the process, which I'll be fixing real soon on all
those affected.

Ewomack (KDE section maintainer) and I were the only ones to have a
substantial disagreement on whether mine was right or wrong. And it was
on the arts tarball, which Arwed diffed and saw some security
improvements, so it looks like the arts people changed the source on
their arts-1.1 tarball without bumping the version (bad, bad people).

Since I had summonned mine a long time ago, it hadn't updated. As a
result of this, I have setup weekly re-forced summoning to double-check
everything.

I doubt that one was malicious, since the newer one had improvements.

>
> BTW: I had a compromised arts tarball lately which I would have
> installed without md5 checks.
>

So it did work... good. I'm doing weekly audits of the grimoire as a
whole, and in some files (non-versioned ones) daily, as they are more
likely to have an md5 change. New spells should get picked up on my
mirror and checker within eight hours. It takes 1.5 hours to run the
process on my XP 2100+ / 512 DDR server.

I'm currently noticing that my crons overlap each other sometimes and do
strange things, like breaking the process after a certain amount of time
(only sometimes it seems. so I'm going to have to edit my crons a bit
more and read the cron source to see why it's doing that.

Anybody have experience with long crons?

Seth

- --
Seth Alan Woolley <seth at tautology.org>, SPAM/UCE is unauthorized
Key id 7BEACC7D = 2978 0BD1 BA48 B671 C1EB 93F7 EDF4 3CDF 7BEA CC7D
Full Key at seth.tautology.org, see www.gnupg.org www.keyserver.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)

iD8DBQE+Olib7fQ833vqzH0RAknUAKCzv4dPX8qqO7ZPzwqLDQzvR7yTGwCeOUBs
5c1qhKJbGVT/UqHkWZScu3U=
=His2
-----END PGP SIGNATURE-----





Archive powered by MHonArc 2.6.24.

Top of Page