proj/portage:master commit in: /
"Matt Turner" <[email protected]>
| Newsgroups | gmane.linux.gentoo.cvs |
|---|---|
| Message-ID | <1786149767.1f7882e4b216a7d969daf00764f15a4270714df8.mattst88@gentoo> |
commit: 1f7882e4b216a7d969daf00764f15a4270714df8 Author: Matt Turner <mattst88 <AT> gentoo <DOT> org> AuthorDate: Sat Aug 8 00:42:12 2026 +0000 Commit: Matt Turner <mattst88 <AT> gentoo <DOT> org> CommitDate: Sat Aug 8 00:42:47 2026 +0000 URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=1f7882e4 NEWS: move FEATURES="observability" entry to the right release It was added under portage-3.0.80 but belongs in portage-3.0.82 (UNRELEASED). Signed-off-by: Matt Turner <mattst88 <AT> gentoo.org> NEWS | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/NEWS b/NEWS index 5dd267dfa..23d90bbe1 100644 --- a/NEWS +++ b/NEWS @@ -29,6 +29,12 @@ Features: status snapshot. Configurable via PORTAGE_CGROUP_ROOT (default /sys/fs/cgroup/portage); requires root and cgroup v2. +* Add FEATURES="observability" to publish a machine-readable snapshot of the + running emerge process (which packages are building/merging, their current + ebuild phase, and elapsed time) to /run/portage/emerge-<pid>.json. Query it + with the new "portageq jobs" command or "emerge --status". A Unix socket + streams the same snapshots live to connected clients. + * vartree: Avoid pruning preserved-libs database or syncing to disk if we installed no files. @@ -193,12 +199,6 @@ Breaking changes: Features: -* Add FEATURES="observability" to publish a machine-readable snapshot of the - running emerge process (which packages are building/merging, their current - ebuild phase, and elapsed time) to /run/portage/emerge-<pid>.json. Query it - with the new "portageq jobs" command or "emerge --status". A Unix socket - streams the same snapshots live to connected clients. - * Add User-Agent to default wget FETCHCOMMAND and RESUMECOMMAND settings, as well as emirrordist, in order to avoid blocking by some web servers, particularly crates.io. (bug #682610)