freebsd stable - Oct 2007 - 7.0-BETA1.5 Available...

Sorry, I had a bit of a false start with 7.0-BETA1.  I've got sets of
build machines used for the Monthly Snapshots and procedures in place to
try and minimize the mistakes I could make while doing those Snapshots
(previously one set for HEAD, one set for RELENG_6).  The set of
machines I'll be using for the 7.0-RELEASE build are the ones that had
previously been doing the HEAD snapshots and I missed doing one very
important adjustment to the build routine while doing the BETA1 builds,
which resulted in the builds being based on HEAD.  I didn't notice
during the tests I do before uploading it because the build procedure
makes most things (e.g. uname) say what you told it to build, you need
to look harder to discover that sort of mistake.  So, 7.0-BETA1 actually
should have been called something more like 8.0-SURPRISE...  :-(

Sorry for the screw-up.

Note you will not have been impacted at all if you updated an older
machine using cvsup to RELENG_7.  This issue only impacts people who had
done an install using the 7.0-BETA1 ISOs.

The scripts are adjusted and fresh builds have been done, named
7.0-BETA1.5 and they are making their way out to the FTP mirror sites.
The MD5/SHA256s are:

MD5 (7.0-BETA1.5-amd64-bootonly.iso) = 26947a3b33b8bf7daa30b89084debba6
MD5 (7.0-BETA1.5-amd64-disc1.iso) = 0825f468e2d45a028dde2511aca5d246
MD5 (7.0-BETA1.5-amd64-disc2.iso) = faa2b758d343b694b7e030da0eb14fa3
MD5 (7.0-BETA1.5-amd64-docs.iso) = 33afcc3a746f28233c84a872232e3ff4
MD5 (7.0-BETA1.5-amd64-livefs.iso) = 4cd3edb15a1b66b2d8cf3de6a8405681

MD5 (7.0-BETA1.5-i386-bootonly.iso) = df2d4130152afe6efd24c7d34153e319
MD5 (7.0-BETA1.5-i386-disc1.iso) = 211bfe5a5b7554e0623015fb05da9d84
MD5 (7.0-BETA1.5-i386-disc2.iso) = 0eda8b4364313de1b95432bb816ff165
MD5 (7.0-BETA1.5-i386-docs.iso) = ba3ab2c93b1c0258750903955ebc10a6

MD5 (7.0-BETA1.5-sparc64-bootonly.iso) = be05c1d6e2684874c6d95ab581def6ca
MD5 (7.0-BETA1.5-sparc64-disc1.iso) = 9a9f2252d0478884abd3470ed526b68f
MD5 (7.0-BETA1.5-sparc64-disc2.iso) = efa0e1788e861e47ff30e84c6bd6f2fb

SHA256 (7.0-BETA1.5-amd64-bootonly.iso) =
9cd5089a9c0607e4aef1b4f656d8ce890fbfd9bf49a5f9da9ffeee16e60a8eb9
SHA256 (7.0-BETA1.5-amd64-disc1.iso) =
31cdb5f7fcde13e8193cdff235a14cc21902174e7e37fa99c34d779070807004
SHA256 (7.0-BETA1.5-amd64-disc2.iso) =
24324f062917281241e09ae6acb7524db1d3ff378af52e0ac71fcb17dfc8fb01
SHA256 (7.0-BETA1.5-amd64-docs.iso) =
5ba2380116981f3ae767a853d0eef6eff5d6ec614b879e68974a214842cb0645
SHA256 (7.0-BETA1.5-amd64-livefs.iso) =
ceea6b3d4e6211ff5d928de63ea12d464d49405ad6b4391fad595f77c78df75f

SHA256 (7.0-BETA1.5-i386-bootonly.iso) =
467abe92fd1b704b95f9c61cff24e299e3712965e8697257de085f0598b2b08d
SHA256 (7.0-BETA1.5-i386-disc1.iso) =
21db871604fc26ea5c804751209a5f90d0ac178ac7ca5706b34fab9bdd15877b
SHA256 (7.0-BETA1.5-i386-disc2.iso) =
a6faa65e80a09d1f0608a1cfcf81325dad92d6404d025b878626b494dcfec48e
SHA256 (7.0-BETA1.5-i386-docs.iso) =
5341373126f21c3c80a9aabc450dafea5a5f78f3f8665b88ef75050c15aa17cd

SHA256 (7.0-BETA1.5-sparc64-bootonly.iso) =
669f696a4f0c5b6f217e2d4b9c8f71a5ae0aeefce22abf8b2dd892bdff981cd8
SHA256 (7.0-BETA1.5-sparc64-disc1.iso) =
090cb07902faf1b16e2f30278ccacb1d67e2e40fc3071624bd0c1a21609dc367
SHA256 (7.0-BETA1.5-sparc64-disc2.iso) =
c855590ce553047e9f9b8573fc94beb6e980694170d864296f29938c3046ebdb


-- 
                                                Ken Smith
- From there to here, from here to      |       kensmith@cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20071025/e649e993/attachment.pgp

On Thursday 25 October 2007, Ken Smith wrote:
> Sorry, I had a bit of a false start with 7.0-BETA1.  I've got sets
> of build machines used for the Monthly Snapshots and procedures in
> place to try and minimize the mistakes I could make while doing
> those Snapshots (previously one set for HEAD, one set for
> RELENG_6).  The set of machines I'll be using for the 7.0-RELEASE
> build are the ones that had previously been doing the HEAD
> snapshots and I missed doing one very important adjustment to the
> build routine while doing the BETA1 builds, which resulted in the
> builds being based on HEAD.  I didn't notice during the tests I do
> before uploading it because the build procedure makes most things
> (e.g. uname) say what you told it to build, you need to look harder
> to discover that sort of mistake.  So, 7.0-BETA1 actually should
> have been called something more like 8.0-SURPRISE...  :-(
>
> Sorry for the screw-up.
>
This change seems to break portupgrade.  It complains that it cannot 
parse the output of uname.  I think it is not capable of handling the 
1.5 after the BETA.

On Thu, Oct 25, 2007 at 06:27:14PM -0400, Ken Smith
wrote:
> ...
> Note you will not have been impacted at all if you updated an older
> machine using cvsup to RELENG_7.  This issue only impacts people who had
> done an install using the 7.0-BETA1 ISOs.
Thanks for this information.  Last night I did a fresh 7.0-BETA1
install, fetched the RELENG_7 sources and had some installworld fun.
Everything wents fine but I wondered how many changes where between
7.0-BETA1 and the latest RELENG_7... hehe :)

Everything wents fine.  Mergemaster did a great job but I still want
to ask if there can be a problem in the future because I switched from
8.0-SUPRISE to 7.0-STABLE...

-- 
Oliver PETER, eMail: hoschi@mouhaha.de, ICQ# 113969174
"Worker bees can leave.  Even drones can fly away.
                         The Queen is their slave."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20071026/1005375c/attachment.pgp