Any last-minute 3.6 commits?
dragonflybsd at marino.st
Wed Nov 20 23:09:09 PST 2013
Just march on. I patched the package to build correctly with or without
the commit and I'll just leave my patch in place for a year or two,
that's fine. The latest 3.6 release packages are building fine now and
I'll probably update the LATEST packages later today (The RELEASE
packages stay the same).
P.S. However, swildner already MFC'd it 9 hours ago and it would be nice
if it were included in the first release. It's just no longer an issue
On 11/21/2013 02:35, Justin Sherrill wrote:
> It's never too late. Are you saying that MFCing this change would add
> 6000 packages that would otherwise not build? If that is so, we can
> cherry-pick, tag 3.6.1, and that is what we release. Extra packages are
> more beneficial than a version number ending in 0.
> On Nov 20, 2013 4:03 AM, "John Marino" <dragonflybsd at marino.st
> <mailto:dragonflybsd at marino.st>> wrote:
> On 11/19/2013 06:08, Justin Sherrill wrote:
> > It's been two weeks, and dports packages are built (thanks marino) and
> > release notes are mostly done (thanks ftigeot) and there's no
> nasty bugs
> > waiting that I know of, or MFCs pending... I'm not used to it
> being so
> > quiet.
> > Tomorrow night I'll tag 3.6.0 and start building the iso/img files.
> > There's no GUI images right now because of the dports switch, but
> > that's not worth holding up the release.
> Hi Justin,
> I just found out this commit:
> was not MFC'd. That was unfortunate. It actually caused 6000+ dports
> breakage on Release 3.6 after libcheck was adjusted for master. Too
> late now, I guess.
More information about the Kernel