diff options
| -rw-r--r-- | shared/releases.adoc | 4 | ||||
| -rw-r--r-- | website/content/en/releng/_index.adoc | 2 | ||||
| -rw-r--r-- | website/content/en/status/report-2025-07-2025-09/portmgr.adoc | 52 | ||||
| -rw-r--r-- | website/content/en/status/report-2025-07-2025-09/valgrind.adoc | 53 |
4 files changed, 108 insertions, 3 deletions
diff --git a/shared/releases.adoc b/shared/releases.adoc index 130a0dde47..f6a4976117 100644 --- a/shared/releases.adoc +++ b/shared/releases.adoc @@ -37,13 +37,13 @@ // Set to 'INCLUDE' when the schedule is available. -:beta-upcoming: IGNORE +:beta-upcoming: INCLUDE // Set to 'INCLUDE' when the installation images are available. :beta-testing: IGNORE :betarel-current-major: 14 -:betarel-current: 14.3 +:betarel-current: 14.4 :betarel-vers: RELEASE :u-betarel-schedule: https://www.FreeBSD.org/releases/{betarel-current}R/schedule/ diff --git a/website/content/en/releng/_index.adoc b/website/content/en/releng/_index.adoc index 59cb5d62b6..2e0e42f6c4 100644 --- a/website/content/en/releng/_index.adoc +++ b/website/content/en/releng/_index.adoc @@ -33,7 +33,7 @@ General information about committing to -STABLE. |=== |Date |Event |Information |December 2025 |FreeBSD 15.0 |link:../releases/15.0R/schedule/[Target Schedule] -|March 2026 |FreeBSD 14.4 | +|March 2026 |FreeBSD 14.4 |link:../releases/14.4R/schedule/[Target Schedule] |June 2026 |FreeBSD 15.1 | |September 2026 |FreeBSD 14.5 | |December 2026 |FreeBSD 15.2 | diff --git a/website/content/en/status/report-2025-07-2025-09/portmgr.adoc b/website/content/en/status/report-2025-07-2025-09/portmgr.adoc new file mode 100644 index 0000000000..ef1fb377e0 --- /dev/null +++ b/website/content/en/status/report-2025-07-2025-09/portmgr.adoc @@ -0,0 +1,52 @@ +=== Ports Collection + +Links: + +link:https://www.FreeBSD.org/ports/[About FreeBSD Ports] URL:link:https://www.FreeBSD.org/ports/[] + +link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[Contributing to Ports] URL: link:https://docs.freebsd.org/en/articles/contributing/#ports-contributing[] + +link:https://www.freebsd.org/portmgr/[Ports Management Team] URL: link:https://www.freebsd.org/portmgr/[] + +link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[Ports Tarball] URL: link:http://ftp.freebsd.org/pub/FreeBSD/ports/ports/[] + +Contact: Tobias C. Berner <portmgr-secretary@FreeBSD.org> + +Contact: FreeBSD Ports Management Team <portmgr@FreeBSD.org> + +The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages, and personnel matters. +Below is what happened in the last quarter. + +During the last quarter, we welcomed Älven (alven@) and Tiago Gashiba (tiga@) as new ports committers, and said goodbye to six committers. +We also promoted Dan Langille (dvl@) as a full portmgr member after successfully being on the lurker program. + +According to INDEX, there are currently 37,163 (up from 36,605) ports in the Ports Collection. +There are currently about 3,428 (up from 3,330) open ports PRs, of which 821 are unassigned. +The last quarter saw 8,738 (down from 10,924) commits by 156 (down from 157) committers on the main branch and 898 (up from 770) commits by 61 (up from 56) committers on the 2025Q3 branch. + +The most active committers to main were: + +- 2348 sunpoet@FreeBSD.org +- 574 yuri@FreeBSD.org +- 409 vvd@FreeBSD.org +- 406 tagattie@FreeBSD.org +- 348 bofh@FreeBSD.org +- 223 jbeich@FreeBSD.org +- 161 fluffy@FreeBSD.org +- 153 eduardo@FreeBSD.org +- 147 alven@FreeBSD.org +- 143 arrowd@FreeBSD.org + +A lot has happened in the ports tree in the last three months, an excerpt of the major software upgrades are: + +- pkg 2.3.1 +- New USES: zig +- Default version of Lazarus switched to 4.2 (non-devel, non-aarch64) +- Default version of Perl switched to 5.42 +- Chromium 140.0.7339.207 +- Electron 37 and 38 added +- Firefox 143.0.3 +- Firefox-esr 140.3.1 +- KDE Applications 25.08.1 +- KDE Frameworks 6.18.0 +- KDE Plasma 6.4.5 +- Ruby 3.4.6 +- Rust 1.89.0 +- SDL 3.2.22 + +During the last quarter, pkgmgr@ ran 12 exp-runs to test source code changes and various ports upgrades. diff --git a/website/content/en/status/report-2025-07-2025-09/valgrind.adoc b/website/content/en/status/report-2025-07-2025-09/valgrind.adoc new file mode 100644 index 0000000000..d836878b21 --- /dev/null +++ b/website/content/en/status/report-2025-07-2025-09/valgrind.adoc @@ -0,0 +1,53 @@ +=== Valgrind: preparing for 15.0-RELEASE + +Links: + +link:https://www.valgrind.org/[Valgrind Home Page] URL: link:https://www.valgrind.org/[] + +link:https://www.valgrind.org/docs/manual/dist.news.html[Valgrind News] URL: link:https://www.valgrind.org/docs/manual/dist.news.html[] + +link:https://github.com/paulfloyd/freebsdarm64_valgrind[arm64 port] URL: link:https://github.com/paulfloyd/freebsdarm64_valgrind[] + +Contact: Paul Floyd <pjfloyd@wanadoo.fr> + +I have not submitted any reports for over a year. On the whole that is good news as it means that there have not been any major issues. Back then I said that aarch64 support was about to land and indeed it dit in mid April 2024. + +I added a nice little script for use with Valgrind called `vgscript`. This works in a similar manner to `pstack` (or `bstack` on FreeBSD) in that you give it a PID and it will generate a stack trace for that process. If you use `bstack` with a Valgrind process you will see the Valgrind call stack which is probabably of no use to you. If you run `vgstack` with a Valgrind PID it will print the call stack of the test exe running under Valgrind. + +If you use Valgrind regularly could you take a look and answer the survey that I posted on the forums (if you have not done so already). +Here is the link:https://forums.freebsd.org/threads/valgrind-feature-poll.98707/#post-716085[link]. + +Valgrind 3.26 is due out at the end of October 2025 and package:devel/valgrind[] will be updated shortly after that. + +package:devel/valgrind-devel[] will get one (or maybe more) updates as I fix issues with FreeBSD 15.0. + +The oustanding issues that I have on FreeBSD 15.0 are +* aarch64: there is a problem when using Valgrind with gdb/vgdb. Hitting ctrl-c to interrupt the process running under Valgrind does not work and Valgrind crashes with an assert. +* aarch64: a known old issue that was infrequent regarding initialisation of thread memory now seems to occur much more often. +* amd64: maybe similar to the first issue with gdb/vgdb and interrupting a process, but this time I'm seeing `select` return an 'impossible' value. +* amd64: a test for `setcred` is getting an extra "Conditional jump" error message. + +Most of the above are not too serious unless you are a heavy user of gdb/vgdb. + +Here is a list of bugfixes since my last report, Q1 2024. + +* Several suppressions added for libc, libc++ and libstdc++ functions +* Improvements to `setcontest` argument checking +* Some more `aio_*` fixes +* Syscall `_sysctlname` was checking the wrong length of the name argument +* New syscall wrappers for `kcmp`, `getrlimitusage`, `close_range`, `fchroot`, `setcred`, `exterrctl`, `inotify_add_watch_at`, `inotify_rm_awtch`, `jail_attach_jd` and `jail_remove_jd` +* Started adding better `ioctl` argument checking +* Fixes to Valgrinds self-checking modes +* Support aarch64 auxv AT_HWCAP, AT_CHERI_STATS, AT_HWCAP3 and AT_HWCAP4 +* Valgrind file descriptor checking has been significantly enhanced and this includes FreeBSD +* Some old code that I could never test for FreeBSD 10 has been removed +* Removed as much as possible FreeBSD version dependent code. This reduces everyday maintenance at the cost of making version-independent regression tests more difficult +* Turn off check for lock created during text handling that will deliberately leak +* Syscall `sigwait` was not correctly dealing with its atypical return value +* Improved checking of `utrace` syscall arguments +* amd64: syscall arguments 7 and 8 were swapped (it turns out that argument 8 is never needed and has been removed) +* amd64: added `sysarch` subcommands `AMD64_SET_TLSBASE` and `AMD_GET_TLSBASE` +* Reduced warnings that get printed in quiet (-q) mode +* Improved checking done by `sysctl` kern.proc.pathname +* Handle `mmap` MAP_STACK and MAP_GUARD +* Syscalls `open*` now produce an error if you try to open the guest exe for writing +* Syscalls `sigwait` and `sigwaitingfo` were too lax in accepting NULL arguments +* Many of the `*at` system calls (like `faccessat`) were not checking that the directory fd is not one of the file descriptors reserved for Valgrind's use +* Function `memalign` now accepts a size of zero |