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-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, yeah, so

Re: Release Engineering Status Report

2003-09-17 Thread Jeremy Messenger
On Wed, 17 Sep 2003 10:57:58 +0200, Dag-Erling Smrgrav [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?

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, which lags

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 instability

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

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

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 of

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

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 switch to

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 3.5

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

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

RE: Release Engineering Status Report

2003-09-16 Thread Mike Jakubik
; [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't have 3.6.1 in STABLE, why ? It was released on April 1, does that not give

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 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 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 Ruben de Groot
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't have 3.6.1 in STABLE, why ? It was released on April 1, does that not give one enough time to merge

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

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 I believe that

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

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 your

Release Engineering Status Report

2003-09-15 Thread Scott Long
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 instability reports are tracked down. The target goal is two weeks, but