With snapshots, this will happen from time to time.

If people start not understanding why the install media does this
check, and that failure is OK, then I will remove the code on the
install media.

Adjust your expectations.  A hash failure can be OK.

Another alternative is that I only do snapshot builds about every
2 weeks.  How's that idea?

As I say, adjust your expectations.

[ message continues ]

OpenBSD-current is most of the times an excellent quality system,
better and more reliable than most other 'stable' systems. This may
alter one's ability to keep his expectations where they should be.

That being out of the way, you got me wondering what good is
any integrity check which failure is OK.

Thanks,
-jc

[ message continues ]

It is only meant to help uptight people having some sort of false sense
of integrity/security.  It really is for release only because snapshots
are a moving target.  In my opinion the whole check is a giant waste of
time because every damn time the snaps are out of sync for a reason or
another people come whining to the list about something that is

[ message continues ]

Understood and noted. I hope this didn't sound like whining. I really
was just reporting on what looked like a problem in the builds.

Forgive the noise.

[ message continues ]

Am I correct in assuming that the code before this integrity check is 
not able to distinguish between release and snapshot?

[ message continues ]

Imagine the fun&games when the snapshots work and the release does not.
Do people bother to think anymore?

[ message continues ]

Okey dokey...now I know. Hmmm...I've followed snaps for years and always check sums...and I can't remember a time that they failed. Well no worries...I'll roll with it, thanks for the reality check.

Theo de Raadt(deraadt@cvs.openbsd.org)@Fri, Oct 15, 2010 at 06:29:52PM -0600:

[ message continues ]

A little off-topic, but now's as good a time as any to ask:

I sometimes see the snaps (or X) haven't been built for a few or more 
days, and I was just wondering why that is?

Is the build automated, or manually run?  I see the times are usually 
~2pm and ~10pm, Mountain time.

If I see a snap hasn't been built for a while, I'll usually hold off on 
updating the source because something major might be only part way 
complete.  I'll wait until a new snap, install (or update) it, then 
update the source and build.  Is this silly?

Don't get me wrong, I'm not complaining, I'm just wondering.

[ message continues ]

plenty of possibilities.
theo (or todd when it comes to X) was gone or had better stuff to do
a problem with copying snaps out
tree horribly broken (ok, doesn't happen, of course)


a bit, yeah

-- 
Henning Brauer, hb@bsws.de, henning@openbsd.org
BS Web Services, http://bsws.de
Full-Service ISP - Secure Hosting, Mail and DNS Services
Dedicated Servers, Rootservers, Application Hosting

[ message continues ]