Em 06/10/2016 17:18, Glen Barber escreveu:
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 planne
If memory serves me right, Cassiano Peixoto wrote:
> Looks we have some import issues to be fixed before 11-RELEASE. I have
> another one that nobody cares:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257
> and
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212413
>
> It's affec
On Fri, Oct 07, 2016 at 10:52:37AM +0200, Johan Hendriks wrote:
> Op 06/10/2016 om 22:18 schreef 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
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, b
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
_
Looks we have some import issues to be fixed before 11-RELEASE. I have
another one that nobody cares:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257
and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212413
It's affecting ALTQ users on both FreeBSD 11 and 10.3, the system just
crash.
Op 06/10/2016 om 22:18 schreef 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
Op 06/10/2016 om 22:18 schreef 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
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
Will final 11.0-RELEASE include fixes related to broken Hyper-V compatibility?
11.0-RC2, 11.0-RC3 and non-final 11.0-RELEASE failed to install on
Hyper-V 2012 R2 with all current updates.
storvsc0: on vmbus0
(probe0:blkvsc0:0:0:0): storvsc scsi_status = 2
(probe0:blkvsc0:0:1:1): invalid LUN 1
...
-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
republish
-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 mirro
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 (ab
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).
> >
Any chance for MFC'ing r304443?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210686
If not, the workaround should be better documented in RELNOTES.
On Thu, 1 Sep 2016 21:10:00 +
Glen Barber wrote:
> As some of you may be aware, a few last-minute showstoppers appeared
> since 11.0-R
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
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
>> s
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 lar
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
19 matches
Mail list logo
