Re: Upgrading 7.1-PRERELEASE
On Fri, Oct 24, 2008 at 07:52:11AM +0200, Leslie Jensen wrote: Jeremy Chadwick skrev: On Fri, Oct 24, 2008 at 06:41:05AM +0200, Leslie Jensen wrote: Jeremy Chadwick skrev: On Fri, Oct 24, 2008 at 06:24:56AM +0200, Leslie Jensen wrote: I'm running 7.1-PRERELEASE. Yesterday I csup'ed and upgraded as I've done several times in order to install 7.1-BETA2. Everything went as it should, but my system still says 7.1-PRERELEASE. In my stable-supfile I have *default release=cvs tag=RELENG_7. Can anyone tell me where I can make sure that my system upgrades to BETA-2? You are essentially running BETA2, with even newer fixes since the BETA2 release. You should stay with the RELENG_7 tag. Thanks Jeremy I thought that the uname tag would change to BETA-2 I sincerely do not know where BETA2 (not BETA-2) comes from. It's not defined anywhere in src/sys/conf/newvers.sh in CVS: I got it from here http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046037.html /Leslie You've misunderstood what I said. :-) I want to know where the BETA2 string actually came **from**, meaning who or what idealised it and why. It is not a CVS tag, and it's not referred to anywhere other than the here's the ISOs mails that come from Ken. The problem is that this string generates confusion; you are not the first person who has gotten confused by this (downloading version labelled with XYZ and upon building world/kernel, seeing version ABC, inducing an Email to a mailing list asking I downloaded XYZ, but I'm seeing string ABC. Where is the tag for XYZ? I want to follow it, only to be told XYZ is actually PRERELEASE). In essence what I'm saying is we're inconsistent with the strings we use for distributions of FreeBSD. Users **barely** understand the difference between -STABLE and -RELEASE, and only a select few understand the difference between CVS tags RELENG_x and RELENG_x_y. For distributions that are not STABLE or RELEASE, we need to stick with a single string, and that string (IMHO) should be PRERELEASE-MMDD (to signify the build date). http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/newvers.sh To me, this means someone is hand-hacking the file before making ISO releases. The problem with this is there's no way to correlate what CVS tag said string is based on; I have to assume it's RELENG_7. CC'ing Ken, who can probably explain where BETA2 comes from, since I believe he's the one who makes the builds. opinion I really wish we'd name our not-yet-RELEASE-or-STABLE ISO releases as FreeBSD x.y-PRERELEASE-MMDD, which would make more sense to users. /opinion -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 7.1-PRERELEASE
On Thu, 2008-10-23 at 22:30 -0700, Jeremy Chadwick wrote: I sincerely do not know where BETA2 (not BETA-2) comes from. It's not defined anywhere in src/sys/conf/newvers.sh in CVS: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/newvers.sh To me, this means someone is hand-hacking the file before making ISO releases. The problem with this is there's no way to correlate what CVS tag said string is based on; I have to assume it's RELENG_7. CC'ing Ken, who can probably explain where BETA2 comes from, since I believe he's the one who makes the builds. Release builds are done using whats in /usr/src/release. One of the things you can set on the command line when you run make(1) there is the BUILDNAME variable, for example BUILDNAME=7.1-BETA2 in this case. The result of doing that is to change src/sys/conf/newvers.sh inside the build environment (which is among other things a checked out source tree) before doing the build. We use BUILDNAME for the Monthly Snapshots as well, that's why src/sys/conf/newvers.sh doesn't need to be altered just for those builds. opinion I really wish we'd name our not-yet-RELEASE-or-STABLE ISO releases as FreeBSD x.y-PRERELEASE-MMDD, which would make more sense to users. /opinion What to have in src/sys/conf/newvers.sh before we do the branch for the release (typically the BETA builds, we usually do the branch for the release at the point we shift over to Release Candidates (RCs)) is unfortunately something we can't win with no matter what we do. The truth is that branches like RELENG_7 are development branches. We try very hard to never break things (well, badly anyway... :-) in those branches once they're considered to be a stable branch. But from time to time things do get broken there. If we were a corporation RELENG_7 type branches wouldn't be available to the public - they would be a tool for the staff programmers to work in. Its the RELENG_7_0 type branches that would be considered suitable for our customers. But we're not a corporation, and we don't want to keep stuff private. The downside to that however is people who are sort-of involved in the FreeBSD community but aren't truly active participants see RELENG_7 called stable and figure its OK to run their systems on that. We tell them not to, or at least to be sure to read mailing lists like freebsd-stable@ if they're going to do that, but lots of people don't follow that advice. And someone in that situation *really* freaks out if they update a system and winds up with a system that calls itself something too strange. It was a lot worse the last couple times we tried calling a stable branch something that had the word BETA in it, and we've more or less settled on PRERELEASE with no other fiddling as a way to suggest something is going on but not freak out that set of people too much... We do bump src/sys/conf/newvers.sh in the release branches once they get created (so it will become 7.1-RC1 at the point we create RELENG_7_1). But for the BETAs the best you can do to be a bit more descriptive of when you had done a source-based update is just note the date you did the update. -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Upgrading 7.1-PRERELEASE
I'm running 7.1-PRERELEASE. Yesterday I csup'ed and upgraded as I've done several times in order to install 7.1-BETA2. Everything went as it should, but my system still says 7.1-PRERELEASE. In my stable-supfile I have *default release=cvs tag=RELENG_7. Can anyone tell me where I can make sure that my system upgrades to BETA-2? Thank you /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 7.1-PRERELEASE
On Fri, Oct 24, 2008 at 06:24:56AM +0200, Leslie Jensen wrote: I'm running 7.1-PRERELEASE. Yesterday I csup'ed and upgraded as I've done several times in order to install 7.1-BETA2. Everything went as it should, but my system still says 7.1-PRERELEASE. In my stable-supfile I have *default release=cvs tag=RELENG_7. Can anyone tell me where I can make sure that my system upgrades to BETA-2? You are essentially running BETA2, with even newer fixes since the BETA2 release. You should stay with the RELENG_7 tag. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 7.1-PRERELEASE
Jeremy Chadwick skrev: On Fri, Oct 24, 2008 at 06:24:56AM +0200, Leslie Jensen wrote: I'm running 7.1-PRERELEASE. Yesterday I csup'ed and upgraded as I've done several times in order to install 7.1-BETA2. Everything went as it should, but my system still says 7.1-PRERELEASE. In my stable-supfile I have *default release=cvs tag=RELENG_7. Can anyone tell me where I can make sure that my system upgrades to BETA-2? You are essentially running BETA2, with even newer fixes since the BETA2 release. You should stay with the RELENG_7 tag. Thanks Jeremy I thought that the uname tag would change to BETA-2 /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 7.1-PRERELEASE
On Fri, Oct 24, 2008 at 06:41:05AM +0200, Leslie Jensen wrote: Jeremy Chadwick skrev: On Fri, Oct 24, 2008 at 06:24:56AM +0200, Leslie Jensen wrote: I'm running 7.1-PRERELEASE. Yesterday I csup'ed and upgraded as I've done several times in order to install 7.1-BETA2. Everything went as it should, but my system still says 7.1-PRERELEASE. In my stable-supfile I have *default release=cvs tag=RELENG_7. Can anyone tell me where I can make sure that my system upgrades to BETA-2? You are essentially running BETA2, with even newer fixes since the BETA2 release. You should stay with the RELENG_7 tag. Thanks Jeremy I thought that the uname tag would change to BETA-2 I sincerely do not know where BETA2 (not BETA-2) comes from. It's not defined anywhere in src/sys/conf/newvers.sh in CVS: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/newvers.sh To me, this means someone is hand-hacking the file before making ISO releases. The problem with this is there's no way to correlate what CVS tag said string is based on; I have to assume it's RELENG_7. CC'ing Ken, who can probably explain where BETA2 comes from, since I believe he's the one who makes the builds. opinion I really wish we'd name our not-yet-RELEASE-or-STABLE ISO releases as FreeBSD x.y-PRERELEASE-MMDD, which would make more sense to users. /opinion -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 7.1-PRERELEASE
Jeremy Chadwick skrev: On Fri, Oct 24, 2008 at 06:41:05AM +0200, Leslie Jensen wrote: Jeremy Chadwick skrev: On Fri, Oct 24, 2008 at 06:24:56AM +0200, Leslie Jensen wrote: I'm running 7.1-PRERELEASE. Yesterday I csup'ed and upgraded as I've done several times in order to install 7.1-BETA2. Everything went as it should, but my system still says 7.1-PRERELEASE. In my stable-supfile I have *default release=cvs tag=RELENG_7. Can anyone tell me where I can make sure that my system upgrades to BETA-2? You are essentially running BETA2, with even newer fixes since the BETA2 release. You should stay with the RELENG_7 tag. Thanks Jeremy I thought that the uname tag would change to BETA-2 I sincerely do not know where BETA2 (not BETA-2) comes from. It's not defined anywhere in src/sys/conf/newvers.sh in CVS: I got it from here http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/046037.html /Leslie http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/conf/newvers.sh To me, this means someone is hand-hacking the file before making ISO releases. The problem with this is there's no way to correlate what CVS tag said string is based on; I have to assume it's RELENG_7. CC'ing Ken, who can probably explain where BETA2 comes from, since I believe he's the one who makes the builds. opinion I really wish we'd name our not-yet-RELEASE-or-STABLE ISO releases as FreeBSD x.y-PRERELEASE-MMDD, which would make more sense to users. /opinion ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
