Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Jan 2017 00:25:57 -0800
From:      Mark Millard <markmi@dsl-only.net>
To:        ticso@cicely.de
Cc:        Kurt Jaeger <lists@opsec.eu>, freebsd-arm <freebsd-arm@freebsd.org>, Bernd Walter <ticso@cicely7.cicely.de>, freebsd-ports@freebsd.org
Subject:   Re: 11.0-RC1 unsupported by ports?
Message-ID:  <87BFEE93-7617-4131-832B-BE697D352E0D@dsl-only.net>
In-Reply-To: <20170125075459.GL85666@cicely7.cicely.de>
References:  <20170125042413.GK85666@cicely7.cicely.de> <20170125062045.GS13006@home.opsec.eu> <20170125075459.GL85666@cicely7.cicely.de>

next in thread | previous in thread | raw e-mail | index | archive | help

On 2017-Jan-24, at 11:55 PM, Bernd Walter <ticso at cicely7.cicely.de> =
wrote:

On Wed, Jan 25, 2017 at 07:20:45AM +0100, Kurt Jaeger wrote:
> Hi!
>=20
>>> [61]cnc# make install
>>> /!\ ERROR: /!\
>>>=20
>>> Ports Collection support for your FreeBSD version has ended, and no =
ports are
>>> guaranteed to build on this system. Please upgrade to a supported =
release.
>>>=20
>>> No support will be provided if you silence this message by defining
>>> ALLOW_UNSUPPORTED_SYSTEM.
>>=20
>> 11.0-RC1 was superseded by 11.0-REL, so while that message is a bit
>> drastic, there's a point to it.
>=20
> With that argument only the latest version would be supported.
> That said, it is a release candidate and as such one could argue that
> there never had been any official support at all.
> In that case however the message is wrong, because when a support has
> ended it implies that there was support.
>=20
> The check in the code is this one:
> .if (${OPSYS} =3D=3D FreeBSD && (${OSVERSION} < 1003000 || =
(${OSVERSION} >=3D 1100000 && ${OSVERSION} < 1100122))) || \
>    (${OPSYS} =3D=3D DragonFly && ${DFLYVERSION} < 400400)
>=20
> It is not about RC as such, it is explicitly about 11.0-RC.
> My OSVERSION is 1100121.
> So obviously support starts with the first release.
> Fair enough, but then the message is still wrong unless it was =
supported.
>=20
> --=20
> B.Walter <bernd@bwct.de> http://www.bwct.de
> Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.

This is a new check as of -r431746 (Jan 17). The wording
is simply not explicit about prior history from before
the check was added.

For as "as if the check had been in place for a long time"
interpretation I'd guess:

A) 11.0-RC1 would be considered supported when first created.

https://www.freebsd.org/security/security.html#sup says:

In the run-up to a release, a number of -BETA and -RC releases may be =
published for testing purposes. These releases are only supported for a =
few weeks, as resources permit, and will not be listed as supported on =
this page. Users are strongly discouraged from running these releases on =
production systems.

B) 11.0-RELEASE would have made 11.0-RC1 not be supported
   (if 11.0-RC1 was even supported for that long).

C) stable/11 is supported

D) head is "supported" (no complaint anyway).

That last (head) is despite:

https://www.freebsd.org/security/security.html#sup

reporting as currently supported:

stable/10
releng/10.3 (10.3-RELEASE)
stable/11
releng/11.0 (11.0-RELEASE)

(head is not mentioned.)



Quoting https://svnweb.freebsd.org/ports/head/Mk/bsd.port.mk?view=3Dlog
. . .

Revision 431746 - (view) (download) (annotate) - [select for diffs]=20
Modified Tue Jan 17 15:49:16 2017 UTC (7 days, 16 hours ago) by amdmi3=20=

File length: 181933 byte(s)=20
Diff to previous 431681
- Refuse (overridable) to build ports on unsupported system version

Unfortunately, it's not uncommon for FreeBSD users to not update
their systems timely and thus end up using unsupported FreeBSD
release. These users continue to update ports tree as usual and
expect it to work, either unaware of the release EoL, or not clearly
understanding the consequences, which results in unexpected build
failures, bogus bug reports, attempts to bring back removed legacy
support bits and general discontent.

This change introduces system version check which makes ports refuse
to build anything on unsupported system. This makes users aware of
EoL of their system and makes it clear that no port is guaranteed to
build.

The error message tells how to override the check (by defining
ALLOW_UNSUPPORTED_SYSTEM, in which case it's turned into a simple
warning), additionally stressing that this configurartion is not
supported.

Currently outdated are OSVERSION < 1003000 (pre 10.3-RELEASE) and
1100000 <=3D OSVERSION < 1100122 (from 11-CURRENT'2013 to =
11.0-PRERELEASE)

I expect these to be kept up to date with base system lifetimes,
be updated BEFORE removing any support for outdated release from
the tree and also serve as a reference of which OSVERSION checks
may be removed.

Approved by:	portmgr (swills, mat)
Differential Revision:	D9210




=3D=3D=3D
Mark Millard
markmi at dsl-only.net




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87BFEE93-7617-4131-832B-BE697D352E0D>