FreeBSD 13.0 Coming to An End... Already?

[Mark Tinka]

Hi all.

I just ran a 'freebsd-update' today, and got this:

    WARNING: FreeBSD 13.0-RELEASE-p6 is approaching its End-of-Life date.
    It is strongly recommended that you upgrade to a newer
    release within the next 2 months.

Ummh, what am I missing?

I've not seen any notifications about an impending EoL date for 13.0.

https://www.freebsd.org/security/#sup seems to back up my thoughts, and I've not heard a thing about 13.1.

Thoughts?

Mark.

[Graham Perrin]

On 29/01/2022 10:30, Mark Tinka wrote:

… what am I missing? …

We don't yet have a schedule for 13.1-RELEASE. <https://forums.freebsd.org/posts/553459> re: expectations.

[Steve O'Hara-Smith]

On Sat, 29 Jan 2022 12:30:08 +0200
Mark Tinka <ma...@tinka.africa> wrote:

> Hi all.
>
> I just ran a 'freebsd-update' today, and got this:
>
>     WARNING: FreeBSD 13.0-RELEASE-p6 is approaching its End-of-Life date.
>     It is strongly recommended that you upgrade to a newer
>     release within the next 2 months.
>
> Ummh, what am I missing?

I think freebsd-update is using some kind of built in rules to
decide to emit thi message, probably based on some hoped for cadence, and
doesn't actually know the real end of life date.

--
Steve O'Hara-Smith <st...@sohara.org>

[Derek Schrock]

Is your machine synced with ntp?

What is ServerName in /etc/freebsd-update.conf

What's the output of:

$ echo $((1651276800-$(date +%s)))

1651276800 should be the EOL date for 13.0-6 from the latest.ssl and it
appears all update.freebsd.org hosts have that value. I have seen some
update servers get out of sync with others or have bad data.

If the above echo is greater than 7884000 (3 months) then you get that
message.

[Steve O'Hara-Smith]

On Sat, 29 Jan 2022 19:29:52 -0500
Derek Schrock <der...@lifeofadishwasher.com> wrote:

I'm seeing it too so:

> Is your machine synced with ntp?

Yes, 377 reach and a few milliseconds offset - also matches my
radio clocks.

> What is ServerName in /etc/freebsd-update.conf

update.FreeBSD.org

> What's the output of:
>
> $ echo $((1651276800-$(date +%s)))

7763504

> If the above echo is greater than 7884000 (3 months) then you get that
> message.

Less than, surely ?

[Mark Tinka]

On 1/30/22 02:29, Derek Schrock wrote:

> Is your machine synced with ntp?

Yep:

[tinka@ns-02-mba ~]$ ntpq -pn
     remote           refid      st t when poll reach   delay offset 
jitter
==============================================================================
 0.freebsd.pool. .POOL.          16 p    -   64    0    0.000 +0.000  
0.000
+162.159.200.123 10.45.8.5        3 u  998 1024  377   45.124 +0.826   0.069
+162.159.200.1   10.45.8.5        3 u  206 1024  377   45.130 +0.837   0.117
-23.106.249.200  130.133.1.10     2 u  621 1024  377  289.576 -0.338   0.227
*37.228.129.2    193.66.253.90    2 u  106 1024  377  157.506 +0.329   0.425
+81.94.123.17    85.158.27.30     2 u  446 1024  377  147.413 +0.774   0.840
[tinka@ns-02-mba ~]$

> What is ServerName in /etc/freebsd-update.conf

ServerName update.FreeBSD.org

> What's the output of:
>
> $ echo $((1651276800-$(date +%s)))

[tinka@ns-02-mba ~]$ echo $((1651276800-$(date +%s)))
7738780
[tinka@ns-02-mba ~]$

Mark.

[Steve O'Hara-Smith]

On Sat, 29 Jan 2022 19:29:52 -0500
Derek Schrock <der...@lifeofadishwasher.com> wrote:

> 1651276800 should be the EOL date for 13.0-6 from the latest.ssl

That is the 30th April which became less than 90 days in the future
a few days ago. Chances are the real EOL will be later because there's no
sign of 13.1 release starting yet.

[Kyle Evans]

On Sun, Jan 30, 2022 at 6:58 AM Steve O'Hara-Smith <st...@sohara.org> wrote:
>
> On Sat, 29 Jan 2022 19:29:52 -0500
> Derek Schrock <der...@lifeofadishwasher.com> wrote:
>
> > 1651276800 should be the EOL date for 13.0-6 from the latest.ssl
>
> That is the 30th April which became less than 90 days in the future
> a few days ago. Chances are the real EOL will be later because there's no
> sign of 13.1 release starting yet.
>

Correct. The freebsd-update metadata includes the EoL, so it's
initially populated with the projected EoL and gets adjusted when the
next release's schedule is released. I'm trying to see if we can
instead initially populate it with the branch EoL and adjust it to be
closer once the new schedule is released -- in theory, nobody uses
this for other reasons and they just won't notice as long as we get it
set right closer to EoL.

Thanks,

Kyle Evans

[Steve O'Hara-Smith]

On Sun, 30 Jan 2022 09:55:57 -0600
Kyle Evans <kev...@freebsd.org> wrote:

> Correct. The freebsd-update metadata includes the EoL, so it's
> initially populated with the projected EoL and gets adjusted when the
> next release's schedule is released. I'm trying to see if we can

That's about what I thought was going on.

> instead initially populate it with the branch EoL and adjust it to be
> closer once the new schedule is released -- in theory, nobody uses

I like that idea - it's also right for the last one on the branch
and in principle any one might be the last for the branch.

--
Steve O'Hara-Smith
Odds and Ends at http://www.sohara.org/

[Mark Tinka]

Agreed.

Mark.

[Graham Perrin]

Re: FreeBSD 13.0 Coming to An End... Already?

On 30/01/2022 15:55, Kyle Evans wrote:

>
> … The freebsd-update metadata includes the EoL, so it's

> initially populated with the projected EoL and gets adjusted when the
> next release's schedule is released. I'm trying to see if we can
> instead initially populate it with the branch EoL and adjust it to be
> closer once the new schedule is released -- in theory, nobody uses
> this for other reasons and they just won't notice as long as we get it
> set right closer to EoL.
>
> Thanks,
>
> Kyle Evans

Kyle and colleagues: if not already on your radar, maybe also some
adjustment for releng/12.2.

Please see, for example, the notice that's quoted here:

<https://forums.freebsd.org/posts/553832>

As always, thank you.