Re: release(7) targets busted

2017-11-04 Thread Bryan Drewery
On 11/4/2017 9:35 AM, Bryan Drewery wrote: > On 11/3/2017 9:35 PM, Bryan Drewery wrote: >>> *** FATAL ERROR: Cannot 'cd' to /root/git/freebsd/release/.. and install >>> files to >>> the temproot environment >>> >>>

Re: release(7) targets busted

2017-11-04 Thread Bryan Drewery
On 11/3/2017 9:35 PM, Bryan Drewery wrote: >> *** FATAL ERROR: Cannot 'cd' to /root/git/freebsd/release/.. and install >> files to >> the temproot environment >> >> > > If you run into an issue like that with t

Re: release name

2016-08-05 Thread RW
On Sun, 31 Jul 2016 18:41:20 + (UTC) Kostya Berger wrote: > Could somebody, please, explain this: > Am I right to assume that CURRENT or "head" release number is now > 12.0?For in that case I'll have to reduild the ports in case of > upgrading my system to the current head, right?Because my cu

Re: release name

2016-07-31 Thread Kurt Jaeger
Hi! > Could somebody, please, explain this: > Am I right to assume that CURRENT or "head" release number is now > 12.0? Yes. > For in that case I'll have to reduild the ports in case of > upgrading my system to the current head, right? Because my current > system was build well before the 11.0-a

Re: release build problems, drivers.flp: file system is full

2003-11-12 Thread Makoto Matsushita
toha> Release build fails: toha> drivers.flp: file system if full. Since yesterday. toha> Can somebody remove some driver from drivers.conf? No, don't do that. Since we have only 3 floppies, simply removing some modules may mean "it cannot use it while installing FreeBSD." Fortunately w

Re: Release Engineering Status Report

2003-09-17 Thread Dag-Erling Smørgrav
Jeremy Messenger <[EMAIL PROTECTED]> writes: > On Wed, 17 Sep 2003 10:57:58 +0200, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: > > No. 3.6.1 has the same bug, and 3.7 isn't out yet. > http://www.mindrot.org/pipermail/openssh-unix-announce/2003-September/64.html We use OpenSSH-portable, whi

Re: Release Engineering Status Report

2003-09-17 Thread Jeremy Messenger
On Wed, 17 Sep 2003 10:57:58 +0200, Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: "Mike Jakubik" <[EMAIL PROTECTED]> writes: > Is there a specific problem with OpenSSH 3.5 which requires an update > to 3.6.1? Or do you just want me to update it to make the numbers > look pretty on your screen? A

Re: Release Engineering Status Report

2003-09-17 Thread Dag-Erling Smørgrav
David Rhodus <[EMAIL PROTECTED]> writes: > On Tuesday, September 16, 2003, at 11:54 AM, Dag-Erling Smørgrav wrote: > > Is there a specific problem with OpenSSH 3.5 which requires an update > > to 3.6.1? Or do you just want me to update it to make the numbers > > look pretty on your screen? > Umm,

Re: Release Engineering Status Report

2003-09-17 Thread Dag-Erling Smørgrav
"Mike Jakubik" <[EMAIL PROTECTED]> writes: > > Is there a specific problem with OpenSSH 3.5 which requires an update > > to 3.6.1? Or do you just want me to update it to make the numbers > > look pretty on your screen? > Apparently, yes. No. 3.6.1 has the same bug, and 3.7 isn't out yet. DES --

Re: Release Engineering Status Report

2003-09-16 Thread Jacques A. Vidrine
On Tue, Sep 16, 2003 at 09:47:44PM -0400, David Rhodus wrote: > On Tuesday, September 16, 2003, at 11:54 AM, Dag-Erling Smørgrav wrote: > >Is there a specific problem with OpenSSH 3.5 which requires an update > >to 3.6.1? Or do you just want me to update it to make the numbers > >look pretty on yo

Re: Release Engineering Status Report

2003-09-16 Thread David Rhodus
On Tuesday, September 16, 2003, at 11:54 AM, Dag-Erling Smørgrav wrote: David Rhodus <[EMAIL PROTECTED]> writes: Right, say if still the OpenSSH did or still comes out to be real. Ops, now thats right, we don't have 3.6.1 in STABLE, why ? It was released on April 1, does that not give one enough t

Re: Release Engineering Status Report

2003-09-16 Thread Erik Trulsson
On Tue, Sep 16, 2003 at 10:30:50AM -0600, Scott Long wrote: > Mike Silbersack wrote: > >On Tue, 16 Sep 2003, Scott Long wrote: > > > > > >>Patches have been floated on the mailing list that revert PAE in its > >>various stages. Maybe those need to be brought back up. Silby? Tor? > >> > >>Scott >

Re: Release Engineering Status Report

2003-09-16 Thread Terry Lambert
Scott Long wrote: > Agreed. PAE was merged into -stable in three steps. Backing out the > third step and leaving the first two steps removes the instability. > Unfortunately, it was the third step that also was the most complex. > In any case, we have 2 weeks to find the resolution before the dec

Re: Release Engineering Status Report

2003-09-16 Thread Ruben de Groot
ovalov; Scott Long; [EMAIL PROTECTED]; [EMAIL PROTECTED] > > Subject: Re: Release Engineering Status Report > > > > > > David Rhodus <[EMAIL PROTECTED]> writes: > > > Right, say if still the OpenSSH did or still comes out to be > > > real. Ops, now thats

Re: Release Engineering Status Report

2003-09-16 Thread Scott Long
Mike Silbersack wrote: On Tue, 16 Sep 2003, Scott Long wrote: Patches have been floated on the mailing list that revert PAE in its various stages. Maybe those need to be brought back up. Silby? Tor? Scott I believe that Tor's commit on August 30th resolved the PAE-related problems, so there

Re: Release Engineering Status Report

2003-09-16 Thread Sean Chittenden
> 3. A panic caused by sending 64K-1 ping packets, which I can't reproduce. Is this a firewall induced panic? -sc -- Sean Chittenden ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

Re: Release Engineering Status Report

2003-09-16 Thread Mike Silbersack
On Tue, 16 Sep 2003, Scott Long wrote: > Patches have been floated on the mailing list that revert PAE in its > various stages. Maybe those need to be brought back up. Silby? Tor? > > Scott I believe that Tor's commit on August 30th resolved the PAE-related problems, so there is no need for a

RE: Release Engineering Status Report

2003-09-16 Thread Mike Jakubik
c: Maxim Konovalov; Scott Long; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Release Engineering Status Report > > > David Rhodus <[EMAIL PROTECTED]> writes: > > Right, say if still the OpenSSH did or still comes out to be > > real. Ops, now thats right, we don'

Re: Release Engineering Status Report

2003-09-16 Thread Scott Long
Bill Moran wrote: Scott Long wrote: Bruce Evans wrote: On Tue, 16 Sep 2003, Maxim Konovalov wrote: PAE MFC brought an incredible instability to stable branch. It affects 100% of our user community especially when we issued several SAs since PAE commit. They often can't switch to RELENG_4_x sec

Re: Release Engineering Status Report

2003-09-16 Thread Bill Moran
Scott Long wrote: Bruce Evans wrote: On Tue, 16 Sep 2003, Maxim Konovalov wrote: PAE MFC brought an incredible instability to stable branch. It affects 100% of our user community especially when we issued several SAs since PAE commit. They often can't switch to RELENG_4_x security branches beca

Re: Release Engineering Status Report

2003-09-16 Thread Dag-Erling Smørgrav
David Rhodus <[EMAIL PROTECTED]> writes: > Right, say if still the OpenSSH did or still comes out to be > real. Ops, now thats right, we don't have 3.6.1 in STABLE, why ? It > was released on April 1, does that not give one enough time to merge > this in ? Is there a specific problem with OpenSSH

Re: Release Engineering Status Report

2003-09-16 Thread Andrew R. Reiter
On Tue, 16 Sep 2003, Scott Long wrote: :Bruce Evans wrote: :> On Tue, 16 Sep 2003, Maxim Konovalov wrote: :> :> :>>PAE MFC brought an incredible instability to stable branch. It :>>affects 100% of our user community especially when we issued several :>>SAs since PAE commit. They often can't swit

Re: Release Engineering Status Report

2003-09-16 Thread Scott Long
Bruce Evans wrote: On Tue, 16 Sep 2003, Maxim Konovalov wrote: PAE MFC brought an incredible instability to stable branch. It affects 100% of our user community especially when we issued several SAs since PAE commit. They often can't switch to RELENG_4_x security branches because even RELENG_4_

Re: Release Engineering Status Report

2003-09-16 Thread Jacques A. Vidrine
On Tue, Sep 16, 2003 at 08:43:00AM -0400, David Rhodus wrote: > Right, say if still the OpenSSH did or still comes out to be > real. Ops, now thats right, we don't have 3.6.1 in STABLE, why ? It > was released on April 1, does that not give one enough time to merge > this in ? Merging new versions

Re: Release Engineering Status Report

2003-09-16 Thread David Rhodus
On Tuesday, September 16, 2003, at 06:11 AM, Bruce Evans wrote: On Tue, 16 Sep 2003, Maxim Konovalov wrote: PAE MFC brought an incredible instability to stable branch. It affects 100% of our user community especially when we issued several SAs since PAE commit. They often can't switch to RELENG

Re: Release Engineering Status Report

2003-09-16 Thread Bruce Evans
On Tue, 16 Sep 2003, Maxim Konovalov wrote: > PAE MFC brought an incredible instability to stable branch. It > affects 100% of our user community especially when we issued several > SAs since PAE commit. They often can't switch to RELENG_4_x security > branches because even RELENG_4_8 misses sev

Re: Release Engineering Status Report

2003-09-16 Thread Maxim Konovalov
On Mon, 15 Sep 2003, 23:48-0600, Scott Long wrote: > All, > > I'd like to give a status report for 4.x and 5.x for the developers and > users who didn't attend the DevSummit this past weekend. > > 4.9: > The 4.9 release is likely going to be pushed back for a few weeks while > the recent instabili

Re: Release seems to be broken or maybe I missed a change.

2003-08-20 Thread Shin-ichi Yoshimoto
Subject: Release seems to be broken or maybe I missed a change., On Wed, 20 Aug 2003 10:34:43 -0700, [EMAIL PROTECTED] wrote: > With cvsup early this morning. Make release generated Which version of src/libexec/rtld-elf/Makefile are you using ? This problem was fixed a few days ago. > install -o

Re: release and floppies

2003-04-03 Thread Anton Yudin
> + Anton Yudin <[EMAIL PROTECTED]>: > > | How to fix problem with floppies > 1457664 bytes? > > By not downloading a new release before it's announced. Just wait, a > corrected version of 4.8-RELEASE without this problem will appear. > Wait a little longer, for the official announcement. The

Re: release and floppies

2003-04-03 Thread Harald Hanche-Olsen
+ Anton Yudin <[EMAIL PROTECTED]>: | How to fix problem with floppies > 1457664 bytes? By not downloading a new release before it's announced. Just wait, a corrected version of 4.8-RELEASE without this problem will appear. Wait a little longer, for the official announcement. Then get it.

Re: Release building broken for -current

2002-09-09 Thread Udo Schweigert
On Sun, Sep 08, 2002 at 19:05:08 +0200, John Hay wrote: >> >> when bulding release on -current I get (since a couple of days): >> > >> rm -rf /R/stage/dists > >> mkdir -p /R/stage/dists > >> rolling base/base tarball > >> mtree: line 0: dumpdates: No such file or directory > >> *** Error code 1

Re: Release building broken for -current

2002-09-08 Thread Makoto Matsushita
jhay> md5 died on zero length files. You will have to upgrade the machine or jhay> at least do a buildworld with new source before you try a release again. Ya, that's exactly the problem on my buildbox... Thank you for the info. But if new md5(1) doesn't used by during a release, it's yet anot

Re: Release building broken for -current

2002-09-08 Thread John Hay
> > when bulding release on -current I get (since a couple of days): > > > rm -rf /R/stage/dists > > mkdir -p /R/stage/dists > > rolling base/base tarball > > mtree: line 0: dumpdates: No such file or directory > > *** Error code 1 > > > > Stop in /usr/src/release. > > Somehow dumpdates didn't

RE: Release Building - failing at usr/share/doc/usd/13.viref

2002-05-29 Thread Chris Knight
Howdy, Disconnecting usr/share/doc/usd/13.viref and usr/share/doc/papers/sysperf from the build process allowed me to build a -current snapshot. I found the reference in the CVS logs (2002/05/15 09:29:45 PDT) that c++ isn't being built. This explains the lack of groff and tbl. There must be some

Re: Release b0rked..

2001-02-23 Thread Assar Westerlund
Jun Kuriyama <[EMAIL PROTECTED]> writes: > Assar, can you review and commit this? This is ok, but jhb has already fixed this. /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Release b0rked..

2001-02-23 Thread John Baldwin
On 23-Feb-01 John Hay wrote: >> ===> lib/libgssapi >> rm -f .depend >> mkdep -f .depend -a > ... >> /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:43: >> krb5_err.h: No such file or directory >> /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:

Re: Release b0rked.. (libgssapi)

2001-02-23 Thread John Hay
It looks like I was wrong. This patch fix a "make release" for me. The other problems must have been fixed with the other krb fixes over the past few days. Any reason not to commit it? John -- John Hay -- [EMAIL PROTECTED] > > ===> lib/libgssapi > > rm -f .depend > > mkdep -f .depend -a > .

Re: Release b0rked..

2001-02-22 Thread Jun Kuriyama
Assar, can you review and commit this? At 23 Feb 2001 04:31:06 GMT, John Hay wrote: > Index: kerberos5/lib/libgssapi/Makefile > === > RCS file: /home/ncvs/src/kerberos5/lib/libgssapi/Makefile,v > retrieving revision 1.1 > diff -u -

Re: Release b0rked..

2001-02-22 Thread John Hay
> ===> lib/libgssapi > rm -f .depend > mkdep -f .depend -a ... > /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:43: > krb5_err.h: No such file or directory > /usr/src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/krb5/krb5.h:44: > heim_err.h: No such file or dire

Re: Release of 5.0

2000-10-18 Thread Warner Losh
In message <[EMAIL PROTECTED]> Forrest Aldrich writes: : Just curious on the potential release of 5.0 -- which I presume won't be : until next year.. ? 2001 sometime, likely not early in the year. At least that's my WAG at the moment. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: Release still broken with new Perl

2000-06-29 Thread Mark Murray
> > On 29-Jun-00 Mark Murray wrote: > > Hi > > > > I just committed a fix for this. > > Thank you!! Please give me feedback on this when releases work again for you... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "uns

Re: Release still broken with new Perl

2000-06-29 Thread John Baldwin
On 29-Jun-00 Mark Murray wrote: > Hi > > I just committed a fix for this. Thank you!! > M -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscr

Re: Release still broken with new Perl

2000-06-29 Thread Mark Murray
Hi I just committed a fix for this. M > Mark, > > A test release I built today died while installing Perl the second > time around into the trees directory where the install distributions > are rolled from as follows: > > ===> gnu/usr.bin/perl/library/re > cd /usr/obj/usr/src/gnu/usr.bin/perl

Re: Release still broken with new Perl

2000-06-28 Thread John Baldwin
On 28-Jun-00 Mark Murray wrote: >> ===> gnu/usr.bin/perl/library/B >> make: don't know how to make distribute. Stop > > OK - I know how to fix this. > > Thanks for the report! Thanks. :) > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org -- John Baldwin <[EMAIL PROT

Re: Release still broken with new Perl

2000-06-27 Thread Mark Murray
> ===> gnu/usr.bin/perl/library/B > make: don't know how to make distribute. Stop OK - I know how to fix this. Thanks for the report! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the bod

Re: Release still broken with new Perl

2000-06-27 Thread John Baldwin
> On Tue, Jun 27, 2000 at 03:55:59PM -0700, John Baldwin wrote: > > Mark, > > > > A test release I built today died while installing Perl the second > > time around into the trees directory where the install distributions > > are rolled from as follows: > > I just successfully upgraded from a ap

Re: Release still broken with new Perl

2000-06-27 Thread Jesper Skriver
On Tue, Jun 27, 2000 at 03:55:59PM -0700, John Baldwin wrote: > Mark, > > A test release I built today died while installing Perl the second > time around into the trees directory where the install distributions > are rolled from as follows: I just successfully upgraded from a approx 3-4 week ol

Re: RELEASE timelines

1999-12-14 Thread Matthew Thyer
Yes 2.x went on for too long but I was counting 2.2.x as the equivalent of 3.x due to the change in the release schedule (mainly just a change in the numberring). The thing that worries me is the bad reputation that comes from releasing not quite ready releases. Basically the real way to run Fre

FW: RE: RELEASE timelines

1999-12-13 Thread will andrews
On 13-Dec-99 Matthew Thyer wrote: > Consider the 2.2 stream that went through many more releases (counting > 2.2.1 -> 2.2.8). Using that yardstick you'd expect 4.0 to stay in > development until 3.7 is released. I know 7 releases of the 2.2 stream > was considerred a few too many but surely we

Re: RELEASE timelines

1999-12-13 Thread Donn Miller
On Mon, 13 Dec 1999, Steve O'Hara-Smith wrote: > Tell a computer to WIN and ... >... You lose Actually, I always thought there was something subliminal about typing "WIN". Funny how they didn't choose "WIND". It's like, you're typing "WIN", so you in

Re: RELEASE timelines

1999-12-13 Thread Steve O'Hara-Smith
On 13-Dec-99 Sheldon Hearn wrote: > > > On Tue, 14 Dec 1999 00:34:28 +1030, Matthew Thyer wrote: > >> What is the big rush to 4.0-RELEASE ? > > We are relying on public awareness of the fact that .0 releases (in just > about any project) are _going_ to have issues. We need the 4 branch out >

Re: RELEASE timelines

1999-12-13 Thread Sheldon Hearn
On Tue, 14 Dec 1999 00:34:28 +1030, Matthew Thyer wrote: > What is the big rush to 4.0-RELEASE ? We are relying on public awareness of the fact that .0 releases (in just about any project) are _going_ to have issues. We need the 4 branch out out there in the hands of the masses. Ciao, Sheldo

Re: RELEASE

1999-11-17 Thread Jordan K. Hubbard
Months. :) > Any idea of when 4.0-RELEASE will be out, in terms of months or years? > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the

Re: RELEASE

1999-11-17 Thread Poul-Henning Kamp
In message <02d801bf3132$71f6f8c0$[EMAIL PROTECTED]>, "David W. Chapman Jr. " writes: >Any idea of when 4.0-RELEASE will be out, in terms of months or years? Feature freeze in this year. Release in Q1/2000. -- Poul-Henning Kamp FreeBSD coreteam member [EMAIL PROTECTED]

Re: Release schedule of 4.0

1999-11-08 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Forrest Aldrich writes: >We're building a few new systems. I wondered what the status >was of the 4.0 project (stability and release date estimate). We expect release Q1/2000 some time. Feature freeze will probably happen this year. -- Poul-Henning Kamp