| Summary: | 13.0-RELEASE-p11 reportedly EOL sooner than EOL for releng/13.0 | ||
|---|---|---|---|
| Product: | Services | Reporter: | Graham Perrin <grahamperrin> |
| Component: | FreeBSD Update | Assignee: | Security Team <secteam> |
| Status: | Closed FIXED | ||
| Severity: | Affects Many People | CC: | kevans |
| Priority: | --- | ||
| Version: | unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
| URL: | https://www.freebsd.org/security/#sup | ||
|
Description
Graham Perrin
2022-08-02 18:26:37 UTC
From <https://markmail.org/message/jtv7hiz5alglr5jl> (2022-01-30): > … 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 ---- Discussion of 13.0-RELEASE-p11: <https://markmail.org/thread/uduyvxy6c6vnzl4a> This should be fixed with the latest available updates. Thank you for the report. Please re-open this ticket if this is not the case. (In reply to Graham Perrin from comment #1) > … <https://markmail.org/message/jtv7hiz5alglr5jl> (2022-01-30): … FreeBSD-provided alternatives, since MarkMail disappeared: <https://lists.freebsd.org/archives/freebsd-questions/2022-January/000591.html> <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaEqw5aKaxiouV-94okA6uCYpoTV3H1QPOWwHqo9zwcjpQ> > … Discussion of 13.0-RELEASE-p11: <https://markmail.org/thread/uduyvxy6c6vnzl4a> I can't guess an alternative URL for any message within that thread. |