Re: 11.0-RELEASE Status Update

[Glen Barber]

On Fri, Oct 07, 2016 at 08:57:26AM -0700, jungle Boogie wrote:
> On 6 October 2016 at 13:18, Glen Barber  wrote:
> > the final release announcement is planned for Monday, October 10.
> 
> suggestion:
> update the schedule
> https://www.freebsd.org/releases/11.0R/schedule.html
> 

I thought I did, but it looks like a local network hiccup caused the
commit to fail.

Fixing.  Thanks.

Glen



signature.asc
Description: PGP signature

Re: 11.0-RELEASE Status Update

[jungle Boogie]

On 6 October 2016 at 13:18, Glen Barber  wrote:
> the final release announcement is planned for Monday, October 10.

suggestion:
update the schedule
https://www.freebsd.org/releases/11.0R/schedule.html



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

11.0-RELEASE Status Update

[Glen Barber]

As many of you are aware, 11.0-RELEASE needed to be rebuilt to address
several issues that were discovered after the release was built.  Extra
caution is being taken in testing the rebuilt releases, so at present,
the final release announcement is planned for Monday, October 10.

Thank you for your patience in waiting for 11.0-RELEASE.

Glen
On behalf of:   re@



signature.asc
Description: PGP signature

[REVISED] [HEADS-UP] 11.0-RELEASE status update

[Glen Barber]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear FreeBSD Community:

[Corrected the date.]

Although the FreeBSD 11.0-RELEASE has not yet been officially announced,
many have found images on the Project FTP mirrors.

However, please be aware the final 11.0-RELEASE will be rebuilt and
republished on the Project mirrors as a result of a few last-minute
security fixes we feel are imperative to include in the final release.

FreeBSD users already running 11.0-RELEASE will be given instructions on
how to safely upgrade systems to the 11.0-RELEASE-p1 in the final
announcement email.  Those building from source code can obtain the
latest security updates from the releng/11.0 branch in Subversion:

svn://svn.freebsd.org/base/releng/11.0

As the FreeBSD Project strives to provide the best possible product, the
Release Engineering team decided to build an updated release to include
the fixes.  At present, we expect to have the final release available
Wednesday, October 5th.  If you have not yet downloaded 11.0-RELEASE,
please wait for the official release announcement.

Thank you in advance for your patience waiting for 11.0-RELEASE, and of
course for understanding the reasons behind the updated release.

Glen
On behalf of:   re@

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJX7FPNAAoJEAMUWKVHj+KT2joP/0/0AOYfTbFUgZeEUXlmdfew
7nS31bQrBCXi7dgPicfSavdvDfqi4sgiw2/+HY3MxpfLWFJ/WNGveiwryGSiapkA
V3BJ9MCOZb3ZZTbp0JlwbRk1NyGg4ur0S4L6zD+MXuHE95Kts3m/ON8CiGtNUE+1
rzE7Yr10tsU2Zu1Bvtv8rJa9SfLCln8k2FXtG0pxVWO+cK2xo6v84bjOJdExrB4t
eXYoMSoxIyZd1Kv2nLbL1mG7RrLQFVm4TrurMwALI39hVr+IWIvElmo6wndDhTly
XE8aMtpgUMp9b4PrQM+BgFVooR4ihFl0cslHfDuBGuiVJMQoa63agUfGAkclc9Na
nwiJiwcQStOdHcRAnZNBms9DTeNXDD0whq30JoY45kFRI74wjjqP8oNUCUWEd6e8
n1puD2Zr2fqX0NziwtRg3Hy0EHM+9rQTEDtyHCG05sqTncyU7p6tkd49FfndXqaq
h/JkHTP1iyQYsq07GZzyhPA04e/i3N8Djwm+WoRgOlSrItJiPQ/FuqKV0cSERvPR
XZm3DPPRt04aOFe7XGrl2IHi+J6LZ5uwYEXiHFb+fPQMuROZ+IJC0Wu56HI2LHGL
f5wyPiNE1NJIeYLzIgk3UUrENaylsW4/NsgLFj6TW//24ekF2NR+Nk8u7mvoJuXq
vcLDdPW7mReqF13WLzh/
=RcJK
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

[HEADS-UP] 11.0-RELEASE status update

[Glen Barber]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear FreeBSD Community:

Although the FreeBSD 11.0-RELEASE has not yet been officially announced,
many have found images on the Project FTP mirrors.

However, please be aware the final 11.0-RELEASE will be rebuilt and
republished on the Project mirrors as a result of a few last-minute
security fixes we feel are imperative to include in the final release.

FreeBSD users already running 11.0-RELEASE will be given instructions on
how to safely upgrade systems to the 11.0-RELEASE-p1 in the final
announcement email.  Those building from source code can obtain the
latest security updates from the releng/11.0 branch in Subversion:

svn://svn.freebsd.org/base/releng/11.0

As the FreeBSD Project strives to provide the best possible product, the
Release Engineering team decided to build an updated release to include
the fixes.  At present, we expect to have the final release available
Wednesday, October 3rd.  If you have not yet downloaded 11.0-RELEASE,
please wait for the official release announcement.

Thank you in advance for your patience waiting for 11.0-RELEASE, and of
course for understanding the reasons behind the updated release.

Glen
On behalf of:   re@

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJX7EaGAAoJEAMUWKVHj+KTtrgP/iaIozjqDQ2poH1i7J+BewmE
wov+vRcfmGmBvCFLxGPWDsXsYWYw8HCUNrloBesNlUZNe7BoFKliVrBp7KAN5YRE
R+l9AQU8u7UhYoKbM1epB28nDYdLH/veKMpkhyEr2mPglmRDJoJa1JL3xcnRXDj+
yFeeCH5He/jH/ILiO8ChfY8e3aA+K/qMOSicVENW5M2kGs/q0m/i5UZK2LZ+gT7R
/eMl0USfW2B5LebHViv3a6GRArfTzBYZKYdoxXH7vUZ1zgb9CcEPfhYBxu41RMe3
I+HquvqzWKPNwG3GhwqPmKfwQt4PHlATkZwddGosIgSmUZRhhD4eR0DWdXD6k/oS
iSi7QR8lef6ALcVTjt65JNqzPF/9eUJsZikcI0Ov6I0TkV2yzAGnUNneZQ6+22AS
//ZhqWkIu7w1hePJ+Af+SZJDzVdUWzVNiAyMmSFkfW3mFaidyhjR0OULnquG6kSS
kdPOdl/RwJzfP3wkFjt56I8YTyk7YQdwNEcEBQUlXlyZOC/NvUH5eebPJ1Va5UDV
q0FHFaYiATKvQyZUO3Ne9eLzBdYQhmaPSrvTGXrZw53hgShIBOEnwkJYiEGgySL3
vCDro397boLkRL89HUXwuCFurZp/7g/V+I3w4X45y2/GpC/w7isPX/5YYJloETnR
VLGBedKpJbR/5LUJH8Bw
=t8IC
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

11.0-RELEASE status update

[Glen Barber]

There is one issue that was brought to our attention, which we are
waiting for feedback before classifying as an EN candidate.  Once we
receive feedback, the 11.0-RELEASE schedule should be updated to reflect
reality.

At present, I am hopeful 11.0-RC3 builds should start 9/14/2016 at 00:00
UTC (about 11 hours from now).

Thank you for your patience, and apologies for the delay.

Glen
On behalf of:   re@



signature.asc
Description: PGP signature

Re: 11.0-RELEASE status update

[John Baldwin]

On Thursday, September 01, 2016 02:22:04 PM Bryan Drewery wrote:
> On 9/1/2016 2:13 PM, Slawa Olhovchenkov wrote:
> > On Thu, Sep 01, 2016 at 09:10:00PM +, Glen Barber wrote:
> > 
> >> As some of you may be aware, a few last-minute showstoppers appeared
> >> since 11.0-RC1 (and before RC1).
> >>
> >> One of the showstoppers has been fixed in 12-CURRENT, and merged to
> >> stable/11 and releng/11.0 that affected booting from large volumes:
> >>
> >>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212139
> >>
> >> There is one issue that is still being investigated, which we are
> >> classifying as an EN candidate, given the manifestations of the issue
> >> and reproducibility:
> >>
> >>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212168
> >>
> >> There is one blocker before 11.0-RELEASE, that affects libarchive, which
> >> we are waiting for feedback.  Once feedback is received, the schedule
> >> for 11.0-RELEASE will be updated on the website to reflect reality.
> >>
> >> There are a few post-release EN items on our watch list as well, so if
> >> something was not mentioned here, that does not mean it will not be
> >> fixed in 11.0-RELEASE.
> >>
> >> Apologies for the delay, and as always, thank you for your patience.
> >>
> >> Glen
> >> On behalf of:  re@
> >>
> > 
> > 
> > Do you planed to fix issuse with missied and delete libmap32.conf?
> > 
> 
> This was done intentionally quite a while ago:
> https://svnweb.freebsd.org/base?view=revision=282421
> 
> Though it was later removed from ObsoleteFiles so 'make delete-old'
> would not remove it from users' systems in r282423.
> 
> etcupdate removing it is the problem really being reported here.

Mmm, etcupdate should not remove a modified file.  However, etcupdate
assumes that a file removed from /etc is supposed to be removed.  If
your libmap32.conf is unmodified then it truly is pointless since
/usr/lib32/private doesn't exist anymore in 11.

-- 
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: 11.0-RELEASE status update

[Piotr Kubaj]

Can somebody also look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211959 ?

It happens on two PC's.



signature.asc
Description: OpenPGP digital signature

Re: 11.0-RELEASE status update

[Bryan Drewery]

On 9/1/2016 2:13 PM, Slawa Olhovchenkov wrote:
> On Thu, Sep 01, 2016 at 09:10:00PM +, Glen Barber wrote:
> 
>> As some of you may be aware, a few last-minute showstoppers appeared
>> since 11.0-RC1 (and before RC1).
>>
>> One of the showstoppers has been fixed in 12-CURRENT, and merged to
>> stable/11 and releng/11.0 that affected booting from large volumes:
>>
>>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212139
>>
>> There is one issue that is still being investigated, which we are
>> classifying as an EN candidate, given the manifestations of the issue
>> and reproducibility:
>>
>>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212168
>>
>> There is one blocker before 11.0-RELEASE, that affects libarchive, which
>> we are waiting for feedback.  Once feedback is received, the schedule
>> for 11.0-RELEASE will be updated on the website to reflect reality.
>>
>> There are a few post-release EN items on our watch list as well, so if
>> something was not mentioned here, that does not mean it will not be
>> fixed in 11.0-RELEASE.
>>
>> Apologies for the delay, and as always, thank you for your patience.
>>
>> Glen
>> On behalf of:re@
>>
> 
> 
> Do you planed to fix issuse with missied and delete libmap32.conf?
> 

This was done intentionally quite a while ago:
https://svnweb.freebsd.org/base?view=revision=282421

Though it was later removed from ObsoleteFiles so 'make delete-old'
would not remove it from users' systems in r282423.

etcupdate removing it is the problem really being reported here.

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: 11.0-RELEASE status update

[Glen Barber]

On Fri, Sep 02, 2016 at 12:13:51AM +0300, Slawa Olhovchenkov wrote:
> Do you planed to fix issuse with missied and delete libmap32.conf?
> 

Is there a PR about this?  This issue does not sound familiar, so I am
not sure it is (or was) on our radar.

Glen



signature.asc
Description: PGP signature

Re: 11.0-RELEASE status update

[Slawa Olhovchenkov]

On Thu, Sep 01, 2016 at 09:10:00PM +, Glen Barber wrote:

> As some of you may be aware, a few last-minute showstoppers appeared
> since 11.0-RC1 (and before RC1).
> 
> One of the showstoppers has been fixed in 12-CURRENT, and merged to
> stable/11 and releng/11.0 that affected booting from large volumes:
> 
>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212139
> 
> There is one issue that is still being investigated, which we are
> classifying as an EN candidate, given the manifestations of the issue
> and reproducibility:
> 
>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212168
> 
> There is one blocker before 11.0-RELEASE, that affects libarchive, which
> we are waiting for feedback.  Once feedback is received, the schedule
> for 11.0-RELEASE will be updated on the website to reflect reality.
> 
> There are a few post-release EN items on our watch list as well, so if
> something was not mentioned here, that does not mean it will not be
> fixed in 11.0-RELEASE.
> 
> Apologies for the delay, and as always, thank you for your patience.
> 
> Glen
> On behalf of: re@
> 


Do you planed to fix issuse with missied and delete libmap32.conf?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

11.0-RELEASE status update

[Glen Barber]

As some of you may be aware, a few last-minute showstoppers appeared
since 11.0-RC1 (and before RC1).

One of the showstoppers has been fixed in 12-CURRENT, and merged to
stable/11 and releng/11.0 that affected booting from large volumes:

 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212139

There is one issue that is still being investigated, which we are
classifying as an EN candidate, given the manifestations of the issue
and reproducibility:

 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212168

There is one blocker before 11.0-RELEASE, that affects libarchive, which
we are waiting for feedback.  Once feedback is received, the schedule
for 11.0-RELEASE will be updated on the website to reflect reality.

There are a few post-release EN items on our watch list as well, so if
something was not mentioned here, that does not mean it will not be
fixed in 11.0-RELEASE.

Apologies for the delay, and as always, thank you for your patience.

Glen
On behalf of:   re@



signature.asc
Description: PGP signature