Date: Tue, 06 Sep 2016 07:49:15 -0700 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Bryan Drewery <bdrewery@freebsd.org>, Slawa Olhovchenkov <slw@zxy.spb.ru>, Glen Barber <gjb@freebsd.org>, freebsd-current@freebsd.org, freebsd-stable@freebsd.org, FreeBSD Release Engineering Team <re@freebsd.org> Subject: Re: 11.0-RELEASE status update Message-ID: <2864250.fYmTXZWezJ@ralph.baldwin.cx> In-Reply-To: <54d83440-d54d-fe5b-a55e-7fae9dde1ba9@FreeBSD.org> References: <20160901211000.GZ19112@FreeBSD.org> <20160901211351.GA22212@zxy.spb.ru> <54d83440-d54d-fe5b-a55e-7fae9dde1ba9@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 +0000, 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&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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2864250.fYmTXZWezJ>