Weekly GitHub Report for Nixpkgs: July 21, 2025 - July 28, 2025 (12:00:41)
Weekly GitHub Report for Nixpkgs
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
No recent version releases were found.
1.2 Version Information:
Please provide the version release information you would like me to analyze and summarize.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
Policy needed for PRs that are seemingly abandoned by their author: This issue addresses the lack of a clear policy for handling pull requests (PRs) that appear to be abandoned by their authors, highlighting divergent community expectations on whether and when others can supersede such PRs. It proposes a process that balances unblocking stalled contributions quickly while preserving proper attribution, including suggestions for communication protocols, timelines for inactivity, and potential automation to identify and manage abandoned PRs.
- The comments discuss various perspectives on defining abandonment, emphasizing the importance of communication with the original author before superseding a PR, with suggested inactivity thresholds ranging from one month to six months. Contributors generally agree that responsiveness, rather than just elapsed time, should guide decisions, and they consider using or improving automation tools like stale bots to help manage this process, while cautioning against relying solely on bots.
- Number of comments this week: 16
-
Missing configuration profile option for FRR: This issue addresses the lack of a configuration profile option, specifically
frr_profile
, in theservices.frr
module for managing FRR daemons, which currently does not allow setting certain parameters available in the FRR daemons file. The discussion focuses on finding a flexible and maintainable way to expose these options in the NixOS configuration, including suggestions for adding a general extra configuration field to the daemons file to cover both current and future needs.- The comments explore workarounds such as setting
frr defaults
in the config or using extra options per daemon, but highlight limitations and inconsistencies between setups. Participants propose adding a generaldaemonsExtraConfig
option to append lines directly to the daemons file, which is seen as a flexible solution, and there is interest in implementing a nullable enum for profiles with a potential pull request forthcoming. - Number of comments this week: 8
- The comments explore workarounds such as setting
-
Build failure:
hyprsplit
: This issue reports a build failure of thehyprsplit
package when updating the nixpkgs flake input to the latest unstable version. The failure is caused by incompatibilities betweenhyprsplit
and a newer version ofhyprland
, specifically due to missing members in theCWorkspace
class, and the discussion reveals thathyprsplit
needs to be updated or patched to match thehyprland
version used.- The comments clarify that the build failure is due to
hyprland
being updated without a corresponding update inhyprsplit
, and that Hydra does not reproduce the failure because of differences in how the package is built or loaded. Contributors identify that upstream has not tagged a compatible release yet but have opened issues and pull requests to fix the problem. A temporary workaround involving overriding the package source with a patched version is provided, and it is noted that version pinning betweenhyprland
andhyprsplit
is crucial to avoid runtime dispatch errors. - Number of comments this week: 8
- The comments clarify that the build failure is due to
-
python313Packages.xapian: missing dist-info files: This issue reports that the
python313Packages.xapian
package in Nixpkgs is missing the required dist-info files, which prevents satisfying dependencies for Python packages that depend onxapian-bindings
. Additionally, there is confusion about the package name, as the user believes it should be calledxapian-bindings
rather thanxapian
, and attempts to build a dependent package fail due to the missing metadata.- The comments clarify the context of the problem, with the reporter providing a minimal reproducible example and confirming the issue is with the
xapian
package rather thannotmuch2
. Discussion highlights thatxapian-bindings
is a separate meta-package not currently in Nixpkgs, and the existingxapian
package may not fully satisfy dependencies. The reporter acknowledges a title correction and the complexity around the naming and packaging of the bindings. - Number of comments this week: 7
- The comments clarify the context of the problem, with the reporter providing a minimal reproducible example and confirming the issue is with the
-
Build failure: cargo-valgrind: This issue reports a build failure of the
cargo-valgrind
package on the unstable and master branches of Nixpkgs, where a specific test (empty_tests_not_leak_in_release_mode
) fails due to a memory leak detected during testing, causing the build to exit with an error. The failure appears to be reproducible on x86_64-linux systems and may be related to incompatibilities between thecargo-valgrind
suppressions and the Rust compiler version 1.88.0, as previous similar issues were fixed only up to Rust 1.86.0.- The comments reveal initial difficulty reproducing the failure, followed by confirmation that it occurs on x86_64-linux. Discussion suggests the problem is linked to known upstream issues with
cargo-valgrind
and Rust version mismatches, referencing related GitHub issues and fixes that do not yet cover Rust 1.88.0, indicating that maintainers or upstream developers familiar with NixOS might need to address the suppression updates for the newer Rust version. - Number of comments this week: 7
- The comments reveal initial difficulty reproducing the failure, followed by confirmation that it occurs on x86_64-linux. Discussion suggests the problem is linked to known upstream issues with
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Build failure: python3Packages.horizon-eda: This issue reports a build failure for the
python3Packages.horizon-eda
package in the stable Nixpkgs version 25.05, where the Meson build system fails with an error indicating an unknown targethorizon.so
during the build phase. The problem has been consistently reproduced by Hydra, confirming that the build cannot complete successfully under the current configuration and dependencies. - unityhub: FontAsset.cs and Liberation Sans Do Not Exist: This issue reports that many user interfaces in Unity fail to load properly because the Liberation Sans font cannot be found, causing critical UI elements such as the Asset Store to become unusable. The error references a missing FontAsset.cs file in a non-existent directory, and this problem persists even when the Liberation Sans font is installed on the system, indicating a deeper issue with Unity's font asset handling on the affected NixOS environment.
- Update Request: cie-middleware-linux 1.5.6 → 1.5.9: This issue requests an update of the package cie-middleware-linux from version 1.5.6 to the newer upstream version 1.5.9 in the Nixpkgs stable channel (25.05). It includes a reference to the changelog for the new release and confirms that no existing pull request or duplicate issue addresses this update, ensuring the request is relevant and necessary.
zed-editor-fhs
: mismatch withzed-editor
about provided packages and outputs: This issue addresses a discrepancy between thezed-editor-fhs
andzed-editor
packages in the Nixpkgs repository, specifically regarding the provided packages and their output. The reporter expects these two related packages to have matching provided packages and outputs, but currently, they do not align, which may cause confusion or functional inconsistencies.- nheko: libcurl is not build properly with it: This issue reports that the libcurl library included with the nheko package in Nixpkgs stable version 23.05 is not built with the necessary options, causing it to fail when attempting to communicate with servers. As a result, users experience connection errors such as autodiscovery failures, preventing successful login and normal operation of the nheko client.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 94
Summarized Issues:
- Build Failures Due to Upstream or Dependency Issues: Multiple packages in Nixpkgs are experiencing build failures caused by incompatibilities with upstream changes or dependencies. These include issues with Hyprland updates breaking hyprsplit, GCC 14.3.0 causing openmsx compilation errors, obsolete Autoconf macros in gimp-plugin-resynthesizer, and Python 3.13 incompatibilities in packages like renpy, nampa, cupy, and gensim, among others.
- Package Version Updates and Backports: There are numerous requests to update packages to newer upstream versions or backport updates to stable branches. These include updates for bambu-studio, JADX, Blender, Ladybird, Grafana, tailscale, calibre, euphonica, yandex-music, Veloren, Metasploit, and others, aiming to keep Nixpkgs current and secure.
- Python 3.13 Compatibility Problems: Several Python packages fail to build or function correctly with Python 3.13 due to unsupported dependencies or missing metadata. This affects packages like renpy, nampa, cupy, xapian, and gensim, causing build failures or incorrect version reporting.
- Build System and Packaging Issues: Various problems arise from build system configurations, packaging errors, or tooling bugs. Examples include redundant CMAKE_BUILD_TYPE settings, broken CMake builds in glew, broken patchShebangs causing corrupted archives in rabbitmq-server, and issues with sanitiseHeaderPathsHook causing unnecessary rebuilds.
- Runtime and Execution Failures: Some applications fail to run or exhibit incorrect runtime behavior due to packaging or environment issues. This includes Zoom silently failing to launch, boot package failing with corrupt jarfile error, teams-for-linux not respecting proxy settings, and dotnet-lambda-test-tool-8.0 failing due to missing assemblies and permission errors.
- Desktop Environment and UI Integration Bugs: Several issues affect desktop environments and UI components, such as duplicate user avatars in KDE Plasma, missing GNOME Classic session files, icon rendering problems in COSMIC, function keys not working in Xfce, and window management bugs in mcaselector on Plasma 6.
- Networking and DNS Issues: Problems related to networking include nscd leaking DNS requests across namespaces, Podman warning about deprecated cgroups-v1 usage, and pihole-ftl failing due to a typo in database path configuration.
- Nixpkgs Infrastructure and Workflow Challenges: Issues include difficulties merging large branches like haskell-updates due to conflicts and rebuilds, infinite recursion in fetchurl overlays caused by netrc dependencies, and the need for a policy on abandoned pull requests to improve community workflow.
- Package Addition and Feature Requests: Requests to add new packages or features include adding the Nginx UI package, qwen-code AI workflow tool, bloodhound-ce, uplift semantic versioning tool, KVMD daemon for PiKVM, and a buildFlutterApplication helper to simplify Flutter packaging.
- Kernel and Low-Level System Failures: Kernel panics and build failures occur due to hardware driver issues and compiler incompatibilities, such as the Synaptics touchpad driver causing kernel crashes and Linux 5.10 kernel build failing due to unresolved symbols.
- Container and Virtualization Issues: The NixOS continuwuity module lacks support for systemd DynamicUser, and Podman warns about deprecated cgroups usage, indicating container management challenges.
- Python Package Metadata and Distribution Problems: Some Python packages have incorrect or missing metadata, such as python3Packages.sqlite-vec showing version 0.0.0 and python313Packages.xapian missing dist-info files, causing dependency resolution failures.
- Application-Specific Functional Failures: Certain applications fail to function as expected, including FreshRSS service extensions not loading, openvscode-server losing secret storage on reload, Prusa-Slicer ignoring key inputs and failing to save credentials, and WhisperX unable to use GPU due to missing CUDA support in dependencies.
- Cross-Compilation and Architecture-Specific Build Failures: Cross-compiling packages like deno and perl for aarch64 and s390x architectures fails due to linker errors and missing declarations, highlighting challenges in multi-architecture support.
- Security and Vulnerability Updates: Updating packages like GStreamer addresses critical security vulnerabilities including remote code execution risks, emphasizing the importance of timely security patches.
- Miscellaneous Packaging and Usability Issues: Other issues include missing desktop shortcuts, incorrect extension installations, infinite recursion in overlays, and UI visual bugs such as incorrect button corner rendering in the Nordic theme.
2.4 Closed Issues
This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.
Issues Closed This Week: 57
Summarized Issues:
- Build Failures Due to Missing or Incorrect Dependencies: Several packages fail to build because of missing headers, incorrect include paths, or removed modules. Issues include zenpower kernel module failing due to a missing asm/amd_nb.h header, darktable and ladybird packages failing due to libavif include path errors, dupeguru breaking from setuptools module removal, and gtkspell2 failing due to obsolete autoconf macros.
- Package Version Updates: Multiple issues request updating packages to newer upstream versions to keep Nixpkgs current. These include updates for Playwright, goimapnotify, automake, Deno, rio, tor-browser, music-assistant, Dolphin-Emu, trilium-next-desktop, venera, and Mastodon.
- Build Failures Due to Environment or Configuration Errors: Some builds fail because of environment variable issues, hash mismatches, or configuration errors. Examples include JetBrains JDK build failures due to unbound
BOOT_JDK
variable, simplex-chat-desktop and flood packages failing due to hash mismatches, fw-fanctrl service failing due to JSON schema errors, and misskey update script failing due to pnpm lockfile mismatch.
- Input Method and GUI Integration Issues: Input method support and GUI tools have problems due to compositor or service failures. Vesktop's input method support is broken with Electron 35 and Niri compositor, and lxqt-config-monitor fails to launch due to missing KDE D-Bus services.
- Python Package and Module Compatibility Issues: Python packages fail due to API changes, missing dependencies, or interpreter mismatches. The
oterm
package breaks due totextual
incompatibilities, pymatgen fails due to Python version mismatches, Sigil fails to launch due to missing lxml, and mcomix tests fail due to multiprocessing context errors.
- Security and Kernel Bug Fix Requests: Some issues report security vulnerabilities or kernel bugs requiring updates. These include a CVE in sqlite, a Linux kernel bug affecting ptp devices, and a kernel update request to fix ptp4l and phc2sys daemon failures.
- Application Crashes and Runtime Failures: Certain applications crash or fail to launch due to missing namespaces, segmentation faults, or malloc errors. GIMP crashes when picking text outline color, Gradia fails due to missing GtkSource namespace, and fontforge-gtk crashes opening specific fonts.
- Package Naming and Repository Metadata Updates: There are requests to rename packages to avoid conflicts and update repository URLs to reflect moves. The hayabusa package rename was discussed but not implemented, and BloodHound's repository URL was updated.
- Service and Daemon Operational Issues: Some services have operational bugs such as bluetooth audio failing to play despite connection, frigate's prestart script deleting caches unnecessarily, and dbus implementation switch causing system rebuild stalls.
- Packaging and Build System Improvements: Requests include packaging new applications like eSearch and emscripten 3, fixing build failures due to C++ standard mismatches, and adding missing manpages.
- Declarative Configuration and UI Sync Issues: Declarative folder configuration in Syncthing does not reflect in the GUI due to type mismatches, causing user confusion despite devices being added correctly.
- Platform-Specific Package Availability and Build Failures: Some packages are unavailable or fail to build on specific platforms, such as acl missing on arm64-apple-darwin and stable_20250702 linux-rpi kernel breaking nixpkgs-review on aarch64-darwin.
- Package Update Backporting and Channel Discrepancies: Backporting fixes like the comma package to stable is needed due to flag removals causing failures, and Discord package updates show discrepancies between stable and unstable channels due to backporting.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.
III. Pull Requests
3.1 Open Pull Requests
This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 607
Key Open Pull Requests
1. python3Packages.{langchain,langgraph}: 250722 update: This pull request updates the python3Packages.langchain and python3Packages.langgraph packages to their latest versions as of July 25, 2022, replaces the build backend from pdm-backend
to hatchling
to align with upstream changes, updates related prerequisites such as python3Packages.anthropic
and python3Packages.orgmsgpack
to meet new requirements, disables certain flaky tests, and includes multiple incremental version bumps across related subpackages while ensuring successful builds and tests on the aarch64-darwin platform.
- URL: pull/427212
- Merged: No
- Associated Commits: 5b874, 0606c, e4508, c8022, 6de6c, ac788, 72183, 4c637, 7317f, 78aff, c979a, 443f6, a41f1, cd592, b1516, 1881d
2. dart.*: refactor and remove unused packages: This pull request refactors multiple Dart-related packages by cleaning up their code and removing unused or potentially unmaintained packages to improve maintainability and organization within the project.
- URL: pull/428480
- Merged: No
- Associated Commits: fbeda, a6a5e, b5e7f, 01777, 90cd7, 11d60, 18341, 338d0, af6d5, 78d4d, 00eae, 46733, 62315, ec702, 7d135, e5f00
3. aws-*: Update: This pull request updates multiple AWS C SDK components and the AWS SDK for C++ in the Nixpkgs repository to their latest versions, incorporating various upstream improvements and fixes across packages such as aws-c-auth, aws-c-common, aws-c-event-stream, aws-c-http, aws-c-mqtt, aws-c-s3, aws-c-compression, aws-c-io, aws-checksums, aws-crt-cpp, aws-c-sdkutils, and aws-c-cal.
- URL: pull/428410
- Merged: No
- Associated Commits: 45a89, e1448, ad19f, 8e2ee, 9676f, af28d, e53b6, 89247, 006be, 8e437, c66c7, f37c2, 3897b, 12db0
Other Open Pull Requests
- Package Modernization and Relocation: This topic covers moving the greetd package and its greeter variants from the
greetd
namespace to the top-levelpkgs/by-name
directory, modernizing their Nix expressions, and adding update scripts while maintaining backward compatibility through passthrough attributes that emit warnings. These changes improve package organization and maintainability without breaking existing setups.- [pull/427540]
- Alias Deprecation Process: Multiple pull requests enhance the maintainers/scripts/remove-old-aliases.py script by implementing a three-stage deprecation process for aliases, updating aliases.nix for better compatibility, and applying these changes to existing aliases based on specified dates. This structured approach helps manage alias lifecycle more cleanly and predictably.
- [pull/427017]
- Whitespace and Metadata Cleanup: This topic involves trimming unnecessary whitespace in description strings and related metadata across the codebase to improve consistency and cleanliness of package information. Such cleanup contributes to better readability and maintenance of package metadata.
- [pull/427369]
- Python Package Updates: Several pull requests update python312Packages related to mypy-boto3 and boto3-stubs to newer versions, bumping various subpackages to 1.39.10 or 1.39.11 to keep them current with upstream releases. Additionally, the python3Packages.jax library is upgraded from 0.6.2 to 0.7.0 with patches for compatibility and test adjustments.
- [pull/427560, pull/427588]
- GTK X11 Dependency Removal on Darwin: This topic addresses removing X11 library dependencies from GTK 3 and GTK 4 builds on Darwin by disabling X11 support, cleaning up related dependencies, and ensuring the
x11Support
flag is correctly propagated. It resolves issues where GTK 4 indirectly pulled inlibX11
through other packages.- [pull/428426]
- Git Executable Path Hardcoding: A pull request hardcodes the path to the git executable in the python3Packages.setuptools-git package to ensure consistent and reliable git usage within the package. This change improves build stability and reproducibility.
- [pull/427223]
- Cloudflared Token-Based Tunnel Support: This update adds support for token-based tunnels in the nixos/cloudflared-service by enabling token file loading and introducing an environmentFile option to configure tunnel parameters, enhancing configuration flexibility and security.
- [pull/427964]
- Mealie Package Update and Fixes: The mealie package is updated from version 2.8.0 to 3.0.2, with removal of unnecessary dependencies, build fixes related to the NuxtJS frontend, added API tests, updated documentation, and ensured compatibility with x86_64-linux platforms. These changes improve package stability and usability.
- [pull/427176]
- Electron Package Updates: This topic updates electron-source, electron-bin, and electron-chromedriver packages to versions 36.7.3 and 37.2.4, incorporating the latest upstream changes and releases as documented in Electron changelogs.
- [pull/427689]
- Feishin Package Upgrade and Build Changes: The Feishin package is upgraded from version 0.12.6 to 0.18.0, switching its build process from npm to pnpm and adjusting the Nix package accordingly, along with related maintenance and build improvements.
- [pull/428283]
- OPTEE-OS Package Improvements: Updates to OPTEE-OS include fixing the TA_DEV_KIT_DIR contents for building Trusted Applications, removing invalid references to other Nix outputs, upgrading OPTEE-OS and optee-client from 4.6.0 to 4.7.0, and various fixes such as multi-output setup hook adjustments and metadata cleanup.
- [pull/428461]
- Standardizing Package Calls: The codebase is updated to use
callPackage
instead ofpython3Packages.callPackage
throughout the project to standardize package calls and achieve zero rebuilds.- [pull/428097]
- New Epson CUPS Drivers Package: A new package is added for proprietary CUPS drivers supporting Epson inkjet printers, specifically the WorkForce 840 series and Stylus Office BX925, including patches for GCC 14 compatibility and metadata adjustments.
- [pull/428670]
- Postfix-tlspol Backport and Update: This manual backport to the
release-25.05
branch updates postfix-tlspol from version 1.8.9 to 1.8.12 by cherry-picking commits related to package and module adoption and resolver configuration improvements.- [pull/428692]
- Junixsocket Integration for PostgreSQL: The junixsocket version 2.10.1 packages are added to enable Unix socket support for PostgreSQL connections in Java applications, integrating this functionality into postgresql_jdbc and Keycloak via JDBC URI syntax.
- [pull/427538]
- VacuumTube Initial Packaging: The initial packaging of VacuumTube version 1.3.10 is added for the x86_64-linux platform, providing an application that runs YouTube TV/Leanback in Nixpkgs.
- [pull/427703]
- Listmonk Major Upgrade and Refactor: The listmonk package is upgraded from 3.0.0 to 5.0.3, refactored to improve override flexibility with a pinData argument and fixed point derivation, removes the separate stuffbin package, and ensures correct version injection with testing on x86_64-linux and NixOS test suites.
- [pull/428070]
- Nix Minimum Version Raised: Support for the insecure Nix 2.3 version is dropped, raising the minimum required version to 2.18 due to unresolved security vulnerabilities and lack of CI testing for Nix 2.3.
- [pull/428076]
- Z-Library Desktop Launcher Added: An initial derivation for the z-library desktop launcher version 2.4.3 is introduced, including fixes for license information, unpack commands, versioning, package location, and adding a new maintainer.
- [pull/428181]
- Alsa-utils Update and Refactor: The alsa-utils package is updated from 1.2.13 to 1.2.14, refactored to adopt the finalAttrs pattern and remove
with lib;
, and provides more precise licensing information clarifying GPL and LGPL components for clear license compatibility.- [pull/428312]
- Amazon-q-cli Backport and Darwin Support: A manual backport to release-25.05 updates amazon-q-cli from 1.12.1 to 1.12.6 and adds support for the Darwin platform.
- [pull/428466]
- Snis-assets Source Switch and Update Script: The snis-assets package source is switched to unofficial snapshots hosted by the contributor due to upstream instability, with updated metadata and an added update script for easier maintenance.
- [pull/428618]
- Cider-2 Package Format Migration: The cider-2 package is migrated from an AppImage format to a deb package format, adding an update script to simplify installation and maintenance, addressing the inconvenience of manual AppImage management.
- [pull/427005]
- Libheif Thumbnailer Fix: The libheif package is updated to use an absolute binary path in its thumbnailer file by adding a separate
lib
output to avoid circular dependencies, fixing thumbnail generation issues in Nautilus when installed via home-manager.- [pull/427112]
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 1343
Key Closed Pull Requests
1. rocmPackages: 6.3.3 -> 6.4.x: This pull request proposes updating the rocmPackages from version 6.3.3 to the 6.4.x series but was not merged because it was superseded by a subsequent pull request from a correctly named branch.
- URL: pull/427942
- Merged: No
- Associated Commits: efe8b, e43bb, b85e4, 601b7, 26c51, df0a8, 8fb8d, 051dd, 8764e, ca88d, b9e24, 5859e, 141d8, 611b8, b5638, f7076, 4dd3a, 551b9, 1d47e, a84b3, 6e401, 67099, 5959e, ed8c4, e014b, b0fc2, 1fd6b, 57086, 80fe2, ee9e7, c0eba, af809, 16204, e63ab, 1798b, 3f984, 80cea, d9972, dd1f0, b6b02, a0333, 62d49, b6e69, 260d2, 59fb4, b7016, 04959, b71a2, abdfc, b22e2, b433a, 478ad, 8b7d9, 9e46b, dc0ac, 1e180, 8974d, a69e4, 3235c, 5028d, e0ee9, ff6fe, 0bbe5, 18939, b24f9, 5ed2c, af13a, 3a2db, 2ca95, 93843, c9549, f2917, d58c6, 7d1cc, 7eb5e, b4ec1, a2635, 34836, e3f7c, d1173, 82aed, c85b8, 0b137, 191a9, dd47c, 69375, 37a9e, b802a, d9a77, e5fc4, 39685, 5a572, b6b5e, 76598, 80148, ff120, 2e7f9, ae006, 62232, 9e21e, 5f046, 70d18, 1207f, 386a3, 84ed6, 733e5, 0c939, 1af1a, d5c6c, 721a5, af6c3, 73cdc, b7d0c, c79b2, ff4ca, 0cf46, 86f7a, 29807, 4ba0e, 067e9, 45836, b0aeb, e88fc, ca97a, a331d, cbc29, 76c46, efba5, 54268, ef1cc, 70439, 183b3, 6f2e2, e0921, 924ab, fea8c, c93d5, 31c13, 90208, 81521, 2ff78, 7ef79, 83ab2, 16729, 6290b, 93022, ec52f, 556cd, 12649, e48d1, 5a456, 9c70a, 2df20, dddbe, 070e7, 8732e, b5a82, d4b59
2. MONAPP-41664: CVE-2025-48174, CVE-2025-48175 Patch on Libavif: This pull request proposes a package version bump for Libavif to patch the security vulnerabilities identified as CVE-2025-48174 and CVE-2025-48175.
- URL: pull/427277
- Merged: No
- Associated Commits: 4ad76, 2e8c0, 70584, 57da0, 564e4, 0f014, 00c31, d292b, 28c98, 0799e, 500fe, 64b86, a787c, d85ff, 5afd2, b30d0, c28dc, 27cd1, eddde, 0bad9, 2cde2, 243cf, 8f419, 4ce39, 57802, 3b736, 9080f, b2ae6, fd751, 49be5, b5eff, 67d71, bec7c, 61a1f, 3c050, df132, ced7d, 37fbb, c8759, 18732, 7cccd, 587b9, 95e9b, 614f3, 3f001, 0ab67, 4dbd0, b0c3b, 1f908, ee295, ebc34, 18373, bd9c3, b04be, 04ebb
3. staging-next 2025-07-15: This pull request merges the latest changes from the master branch into the staging-next branch as of July 15, 2025, including minor fixes such as LibreOffice adjacent updates and an update of nspr from version 4.36 to 4.37, with no notable breakages reported.
- URL: pull/425387
- Merged: 2025-07-26T17:00:52Z
- Associated Commits: 40669, 6f8ef, 8ef58, 4b4be, 063b7, 2cdbe, f9668, b8dca, 7f9c6, d5b20, bb0f3, 88e9e, aec7c, 8cc55, c1cb6, 1888a, 08b1c, 959ae, 8fcc6
Other Closed Pull Requests
- Packaging Refactor and Modernization: This topic covers the refactoring and modernization of packaging for dwm, dwm-status, dmenu (including dmenu-wayland), st, and their forks by migrating them to the
pkgs/by-name
directory. The changes improve configuration handling, remove unnecessary dependencies, and add update scripts to streamline maintenance.
- CI Evaluation and Stability Improvements: Multiple pull requests improve the Nixpkgs CI evaluation by enabling failure on assertion errors for x86_64-linux, fixing evaluation failures, marking packages as broken, and replacing asserts with metadata-based checks to avoid errors for invalid platform combinations. These changes enhance CI stability and ensure more accurate and strict evaluation results.
- Home Assistant and Related Python Package Updates: Several pull requests update the Home Assistant package and related Python packages to their latest versions, ensuring compatibility with newer Python versions and platforms. These updates incorporate multiple upstream changelogs and include dependency and build fixes.
- Backports for Release Branches: This topic includes backports of updates for Zoom client, p2pool, comma package, and libxml2 security patches to the
release-25.05
branch. These backports ensure compatibility, fix build issues, and address security vulnerabilities on stable release branches.
- Package Updates and Upgrades: Multiple packages are updated including materialx, robin-map, nss_latest, Firefox packages, Vim, and hyprlandPlugins. These updates incorporate the latest improvements, security fixes, and version upgrades to maintain compatibility and functionality.
- Python Package Fixes and Compatibility: This includes unbreaking python3Packages.textual and tree-sitter.grammars by reverting problematic updates and pinning stable versions, as well as updating python3Packages.craft-application and related craft-* libraries to prevent test failures. These fixes ensure build stability and compatibility across Python packages.
- CI Environment and Formatting Updates: Updates to the pinned CI environment include upgrading to Nix 2.30 and nixfmt 1.0.0, fixing syntax errors in nix code blocks, resolving formatting conflicts, and raising minimum required Nix versions for tests. These changes improve CI reliability and code formatting consistency.
- Haunt Static Site Generator Refactor: The Haunt package is refactored by switching source fetching to git, enabling tests, adding update scripts, using makeBinaryWrapper, and adding a maintainer. These improvements address previous concerns about non-determinism and enhance package maintainability.
- Linux Kernel Updates: Multiple Linux kernel versions including 6.16-rc7, 6.15.8, 6.12.40, 6.6.100, and 6.1.147 are updated with the latest fixes and improvements to keep the NixOS project current and resolve known issues.
- PHP Extensions and Architecture Support: The phpExtensions.blackfire package is updated to a newer version and adds support for the aarch64-darwin platform, resolving an assertion error blocking PHP 8.4 compatibility on that architecture.
- Removal of Deprecated Dependencies: Various packages are updated to remove dependencies on the older libsoup2 library by enabling newer alternatives like libsoup3 and backporting patches to maintain compatibility and functionality.
- Initial Packaging and Maintainer Additions: The initial packaging of dynarmic and xbyak for x86_64-linux and aarch64-linux platforms is introduced, along with updating the azahar package to use these system-provided libraries and adding a new maintainer.
3.3 Pull Request Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
- maintainers: drop emaryn
- Toxicity Score: 0.85 (Rapid escalation, personal insults, accusatory tone, oppressive atmosphere, ad hominem attacks)
- This GitHub conversation involves a contributor expressing deep frustration and disappointment with the community's response to their efforts, highlighting experiences of nitpicking, disproportionate criticism, personal insults, and an oppressive atmosphere. The tone is predominantly negative and tense, with the contributor feeling misaligned with the community's values and perceiving a culture of coercion and intimidation. The discussion appears to have escalated due to perceived ad hominem attacks and the influence of status within the community, ultimately leading to the contributor's decision to withdraw their involvement.
IV. Contributors
4.1 Contributors
Active Contributors:
We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.
If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.
Contributor | Commits | Pull Requests | Issues | Comments |
---|---|---|---|---|
r-ryantm | 2434 | 1483 | 0 | 0 |
wolfgangwalther | 213 | 62 | 3 | 122 |
acid-bong | 45 | 4 | 0 | 348 |
fabaff | 221 | 48 | 0 | 1 |
wegank | 109 | 59 | 0 | 17 |
drupol | 39 | 20 | 0 | 115 |
Prince213 | 124 | 20 | 0 | 25 |
GaetanLepage | 112 | 35 | 0 | 17 |
K900 | 133 | 8 | 1 | 20 |
philiptaron | 49 | 4 | 0 | 105 |