Solved How long does it take for the latest Firefox appear in the FreeBSD repos ?

john_rambo said:
FreeBSD is actually ahead which is really nice. I am really happy about this
Click to expand...

☑ I did think of you when I saw Firefox progress from 95.⋯ to 97.⋯ within around fifteen days :-)

john_rambo said:
but I am confused about FreeBSD's update policy. …
Click to expand...

Updates to FreeBSD

In a security context, <{link removed}> refers to a February 2015 announcement that might help to put things in context:
  • {link removed}.

Updates to each port within the ports collection

The FreeBSD Project offers a handbook, within which there is (for example) a requirement {link removed} to update /usr/ports/UPDATING in some situations. To the best of my knowledge, the Project does not express a policy for updates to ports.

Wherever a port has a maintainer, updates are a responsibility of the maintainer (sometimes a group of people with a single e-mail address for maintenance purposes).

For some ports, you'll see an occasional exp-run. Unfortunately, this phrase is not in the FreeBSD Handbook glossary {link removed}, which is detached from the FreeBSD Handbook; not in the FreeBSD Handbook; not in the FreeBSD Porter's Handbook. A recent example, for print/harfbuzz:
  • FreeBSD bug {link removed}.
Things such as this are not exactly policy, but they do form part of a holistic set of approaches that's described somewhere.
 
Last edited:
I have updated packages today and still have firefox-96.0.3,2. I am on FreeBSD 13, using packages from the latest branch. FreshPorts shows that Firefox 97 is available on FreeBSD 14.
 
ESR.png

I prefer Firefox-ESR and have been using that exclusively the past few years.

I'm running FreeBSD 13.0-RELEASE-p7 now and installed Firefox hrough pkg. There is an update to that in ports, but I'm not vulnerable and see no reason to compile a new version. Mixing ports and pkg something I do now without hesitation and the sky has not fallen yet.

Two W520's updated differently left me with one having a rust vulnerability the other did not encounter. I updated rust through ports today, am using one and the other is online beside it.
 
<{link removed}>

I once disagreed with someone on Reddit who rudely insisted that I should attempt to install a package that was demonstrably non-existent at the time. They took pleasure in continuing rudeness whilst ignoring the demonstration. Just awful. I drew a line.


john_rambo FYI <{link removed}> et cetera. I usually begin at:

<{link removed}>

Click to get <{link removed}> then 130amd64 in the search box gives us:
  • default default (in other words, latest)
  • default quarterly
– at the time of writing, both stopped:done following starts on 2022-02-03.

When the build that you require starts, you'll be able to track its progress in detail.

In the meantime, you can click for details of a stopped build. An example:

1644136295166.png

FreeBSD bugs

{link removed}

{link removed} …
 
Last edited:
grahamperrin said:
… a holistic set of approaches that's described somewhere.
Click to expand...

Now, I remember where: <{link removed}>. It doesn't describe approaches, but it's a useful way to view the FreeBSD Project as a whole:

1644535932062.png

Teams include Port Management and Ports Security.

{link removed}
  • not dated
  • technically, the page history {link removed} began with the January 2021 migration to Hugo/AsciiDoctor.
 
Last edited:
You must log in or register to reply here.
Back
Top