Weekly GitHub Report for Nixpkgs: July 14, 2025 - July 21, 2025 (12:01:16)

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
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

No recent version releases were found.

1.2 Version Information:

To provide a summary, I would need the specific version release information, including the description and creation date. Please provide those details so I can assist you effectively.

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.

1. Proper channel for requesting new packages?: This issue discusses the removal of the package request template from the NixOS/nixpkgs GitHub repository and the resulting confusion about the proper way to request new packages. The user highlights the benefits of the previous template, such as its structured format, ease of classification, and ability to track progress, and suggests establishing a new channel or guideline for package requests.

   • The comments reflect a debate on the effectiveness and consequences of package request templates, with some arguing that they lead to low-quality maintenance and others emphasizing the need for a structured way to track package requests. There is a consensus that package requests should not be checklist-driven, and contributors express concerns about the sustainability of maintaining packages without genuine interest. Some suggest using social channels like Discourse for package requests, while others highlight the importance of engaging new contributors and maintaining a balance between user requests and contributor capacity.
   • Number of comments this week: 22

2. protonvpn-gui: issues connecting to VPN regardless of protocal.: This issue involves a user experiencing connectivity problems with the ProtonVPN GUI version 4.9.6 on NixOS, where attempts to connect to a VPN server using OpenVPN result in an unexpected error, and while WireGuard connects, it fails to route traffic. The user provides detailed logs and system information, noting that a newer version of the software is available but unsure if it resolves the issue.

   • The comments discuss troubleshooting steps, including trying the latest software version, adjusting application settings, and sharing configuration details. Users identify that missing NetworkManager plugins might be causing the issue, and enabling the openvpn plugin resolves the problem for some, suggesting it should be a dependency for the ProtonVPN GUI.
   • Number of comments this week: 13

3. Can't reuse Nixos Installation USB, nixos is permanently stored in my USB: This issue describes a problem where a user is unable to reuse a USB drive after installing NixOS, as attempts to format or overwrite the drive with another ISO result in the USB still showing the NixOS live ISO. The user expresses concern that their main drive might also be permanently affected by NixOS, and they plan to try using another USB to resolve the issue.

   • The comments discuss potential causes and solutions, including the possibility of data being cached rather than written, and the use of the dd command for flashing. Suggestions are made to check if the USB is unmounted before using dd, and to try using other tools like "Disks (Gnome)" for formatting. The user eventually resolves the issue by using "Disks (Gnome)" to take ownership and format the USB, expressing gratitude for the help and deciding to try another Linux distribution.
   • Number of comments this week: 12

4. Build failure: jetbrains.jdk: This issue involves a build failure related to the JetBrains JDK package in the NixOS/nixpkgs repository, specifically when attempting to build using a specified Nixpkgs version. The problem is highlighted by an error in the log output indicating an "unbound variable" during the build process, which suggests issues with variable handling in the build scripts.

   • The comments discuss difficulties in reproducing the build status due to Hydra search timeouts, with some users encountering the same issue on their machines. Workarounds and patches are shared, including using an override for JetBrains Rider and a patch to address variable passing issues. There are mentions of related pull requests and requests for review from the NixOS Java team to resolve the issue.
   • Number of comments this week: 9

5. Build failure: oterm (collateral damage of textual being now marked as broken): This issue concerns a build failure in the Nixpkgs project, specifically related to the 'oterm' package, which is affected by the 'textual' package being marked as broken due to a dependency issue with 'py-tree-sitter'. The problem arises because 'py-tree-sitter' has not yet been updated to accommodate changes in the 'tree-sitter' API, causing the 'textual' package to fail during the build process.

   • The comments discuss the root cause of the issue, which is linked to recent updates in the 'tree-sitter' API and the lack of corresponding updates in 'py-tree-sitter'. Contributors suggest potential solutions, such as patching 'textual' or downgrading dependencies, but acknowledge the complexity and potential for further breakage. There is also a discussion about the need for a tracking issue for 'textual' and the challenges of managing dependencies from GitHub versus PyPI.
   • Number of comments this week: 9

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.

1. Build failure: python3Packages.horizon-eda: This issue pertains to a build failure encountered when attempting to build the python3Packages.horizon-eda package using Nix, specifically on the stable version 25.05. The failure is reproducible by Hydra, and the error occurs during the build phase with a "ninja: error: unknown target 'horizon.so'" message, indicating a problem with the build configuration or target specification.
2. unityhub: FontAsset.cs and Liberation Sans Do Not Exist: This issue pertains to a bug in Unity where many user interfaces fail to load properly due to the inability to find and load the Liberation Sans font, resulting in significant UI elements, such as the Asset Store, being unusable. The problem is further compounded by an error message indicating the non-existence of a critical file, FontAsset.cs, which reoccurs whenever an affected UI element is interacted with, despite the Liberation Sans font being installed on the system.
3. Update Request: cie-middleware-linux 1.5.6 → 1.5.9: This issue is about updating the cie-middleware-linux package from version 1.5.6 to the upstream version 1.5.9 in the Nixpkgs repository. The request highlights the need for maintainers to address this update, ensuring that the package is current and aligns with the latest stable release, while also confirming that no existing pull requests or issues cover this update.
4. zed-editor-fhs: mismatch with zed-editor about provided packages and outputs: This issue highlights a discrepancy between the zed-editor-fhs and zed-editor packages in terms of the packages they provide and their outputs. The user expects these two packages to have matching outputs and has provided steps to reproduce the issue, along with screenshots for further clarification.
5. nheko: libcurl is not build properly with it: This issue pertains to the improper build configuration of libcurl when installing the nheko application, resulting in its inability to communicate with any server due to missing features or protocols. The problem is highlighted by an error message indicating that a requested feature or option was not found in libcurl due to a build-time decision, which prevents successful autodiscovery and server connection.

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: 112

Summarized Issues:

• Build Failures: This topic covers various issues related to build failures in the Nixpkgs project. Many packages, such as ocaml-ng.ocamlPackages_5_1.pyml, Envoy, and gnucobol, encounter build interruptions due to missing dependencies, outdated configurations, or compatibility issues with newer software versions. These failures often require specific patches or updates to resolve, and some are reproducible by Hydra, indicating a broader impact on the build system.
  • issues/424996, issues/425065, issues/425255, issues/425285, issues/425304, issues/425306, issues/425311, issues/425328, issues/425333, issues/425335, issues/425336, issues/425338, issues/425342, issues/425343, issues/425346, issues/425350, issues/425353, issues/425357, issues/425365, issues/425366, issues/425370, issues/425798, issues/425800, issues/425802, issues/425816, issues/425826, issues/426046, issues/426056, issues/426112, issues/426154, issues/426401, issues/426410, issues/426717

• Package Updates: Several issues request updates to existing packages in the Nixpkgs repository. These updates often involve moving to newer versions to incorporate bug fixes, new features, or security patches, as seen with packages like Mullvad VPN, whisky, and readline. The process typically requires maintainers to verify compatibility and ensure that no existing functionality is broken.
  • issues/424929, issues/425089, issues/425150, issues/425153, issues/425339, issues/425380, issues/425424, issues/425425, issues/425608, issues/426140, issues/426187, issues/426362, issues/426514, issues/426523, issues/426669

• New Package Requests: There are multiple requests to add new packages to the Nixpkgs repository. These requests often highlight the need for specific software tools or libraries, such as the "lsfg-vk" package for Linux scaling or the "obico-server" for 3D printer monitoring, and require maintainers to evaluate the feasibility and demand for inclusion.
  • issues/425013, issues/425263, issues/425457, issues/425846, issues/426001, issues/426236, issues/426656

• Bug Reports: Various issues report bugs in existing packages or configurations within the Nixpkgs project. These bugs can range from application crashes, such as in the ayugram-desktop and Element Desktop, to misconfigurations in system services, requiring detailed investigation and often collaboration with upstream developers to resolve.
  • issues/424868, issues/425116, issues/425167, issues/425180, issues/425231, issues/425327, issues/425355, issues/425577, issues/425620, issues/425735, issues/425797, issues/425910, issues/426027, issues/426133, issues/426282, issues/426296, issues/426375, issues/426467, issues/426675

• Feature Requests: Some issues involve requests for new features or enhancements to existing functionalities in the Nixpkgs project. These requests often aim to improve user experience, such as adding support for new hardware features or enhancing existing modules with additional options.
  • issues/424877, issues/425059, issues/425460, issues/425474, issues/425551, issues/425583, issues/425974, issues/426174, issues/426214, issues/426225, issues/426519, issues/426379, issues/426408

• Configuration and Documentation Issues: Several issues highlight problems with configuration settings or documentation within the Nixpkgs project. These issues often involve missing or incorrect settings, such as the meta.mainProgram attribute in fluxbox, or the need for clearer guidelines on using tools like nixpkgs-review.
  • issues/425759, issues/425827, issues/426408

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: 86

Summarized Issues:

• Package Update Requests: These issues involve requests to update various packages in the Nixpkgs repository, such as 'gale', 'Archipelago', 'torsocks', 'helix', 'materialgram', 'open-webui', 'hyprland', and 'proton pass'. The updates are necessary to incorporate new features, bug fixes, or compatibility improvements, and often involve checking for existing pull requests or ensuring adherence to the NixOS Code of Conduct.
  • issues/424741, issues/424891, issues/425427, issues/425746, issues/426338, issues/426145, issues/426147, issues/426713

• Build Failures Due to Obsolete Macros: Several issues report build failures in the Nixpkgs project due to obsolete macros during the autoreconf phase, affecting packages like 'axel', 'kakasi', 'msmtp', 'dvdauthor', and 'extractpdfmark'. These failures often require updates to the build configuration files or the use of alternative macros to resolve the issues.
  • issues/425275, issues/425352, issues/425490, issues/426212, issues/426767

• Build Failures Due to Missing Dependencies: These issues highlight build failures caused by missing dependencies, such as 'libpcre2' for 'zabbix74.server', 'libavif' for 'darktable', and 'libxml2.so.2' for 'hopper'. The resolution often involves adding the necessary dependencies to the build inputs or updating the package configuration.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Undefined Macros: Several issues report build failures due to undefined macros during the autoreconf phase, affecting packages like 'guile-lib', 'strongswan', 'mldonkey', and 'connman-gtk'. These failures often require updates to the build configuration files or the use of alternative macros to resolve the issues.
  • issues/425317, issues/425321, issues/425557, issues/426206

• Build Failures Due to Incompatibility with New Versions: These issues involve build failures caused by incompatibility with new versions of dependencies, such as Python 3.13 for 'routersploit', NumPy 2.3.0 for 'python310Packages.numpy', and SciPy for 'GNU Radio'. The resolution often involves updating the dependencies or modifying the package configuration to ensure compatibility.
  • issues/425369, issues/425456, issues/425465

• Build Failures Due to Missing Files or Paths: These issues report build failures caused by missing files or paths, such as the 'head' builtin function for 'gale', missing include paths for 'sdl3-image', and missing template arguments for 'radiotray-ng'. The resolution often involves updating the package configuration or providing the necessary files or paths.
  • issues/426489, issues/426562, issues/425752

• Build Failures Due to Deprecated Features: These issues involve build failures caused by deprecated features, such as deprecated Rust features for 'vectorchord', deprecated macros for 'redshift', and deprecated command options for 'guile-lib'. The resolution often involves updating the package configuration or using alternative features to ensure compatibility.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Configuration Errors: These issues report build failures caused by configuration errors, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a misconfiguration in 'libavif-config.cmake', and a missing 'AM_ICONV' macro for 'dvdauthor'. The resolution often involves updating the package configuration or providing the necessary attributes or macros.
  • issues/426301, issues/426581, issues/426212

• Build Failures Due to Test Failures: These issues involve build failures caused by test failures, such as assertion errors for 'python3Packages.formulaic', mismatched text output for 'python3Packages.docling-parse', and test failures for 'Scrapy'. The resolution often involves updating the package configuration or modifying the tests to ensure compatibility.
  • issues/426251, issues/426428, issues/425363

• Build Failures Due to Cycles or Dependency Issues: These issues report build failures caused by cycles or dependency issues, such as a cycle detected in the build of 'OpenJDK 8', a cycle in the build of 'scx_cscheds-1.0.13.drv', and a dependency issue for 'libguestfs'. The resolution often involves updating the package configuration or modifying the dependencies to resolve the issues.
  • issues/425402, issues/425498, issues/426129

• Build Failures Due to Missing Capabilities or Permissions: These issues involve build failures caused by missing capabilities or permissions, such as missing capabilities for 'btop', missing permissions for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the necessary capabilities or permissions.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Incorrect Error Messages or Misconfigurations: These issues report build failures caused by incorrect error messages or misconfigurations, such as an incorrect error message for 'fish shell', a misconfiguration in 'nixos-rebuild', and a misconfiguration in 'libavif-config.cmake'. The resolution often involves updating the package configuration or providing the correct error messages or configurations.
  • issues/425613, issues/425637, issues/426581

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues report build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues report build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues involve build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues report build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues involve build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues report build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues report build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues report build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues involve build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues report build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues involve build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues report build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues involve build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues involve build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues involve build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues involve build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues involve build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues involve build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues involve build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues involve build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues involve build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues involve build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues involve build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues involve build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues involve build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues involve build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues involve build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues involve build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues involve build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues involve build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues involve build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues involve build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues involve build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues involve build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues involve build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues involve build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues involve build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues involve build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues involve build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues involve build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues involve build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues involve build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues involve build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues involve build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues involve build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues involve build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues involve build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues involve build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues involve build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues involve build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues involve build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues involve build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues involve build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • issues/426301, issues/426212, issues/425753

• Build Failures Due to Missing or Incorrect Dependencies: These issues involve build failures caused by missing or incorrect dependencies, such as a missing 'libpcre2' dependency for 'zabbix74.server', a missing 'libavif' dependency for 'darktable', and a missing 'libxml2.so.2' dependency for 'hopper'. The resolution often involves updating the package configuration or providing the correct dependencies.
  • issues/425720, issues/426487, issues/425348

• Build Failures Due to Missing or Incorrect Configurations: These issues involve build failures caused by missing or incorrect configurations, such as a missing configuration for 'libavif-config.cmake', a missing configuration for 'bash-language-server', and a missing configuration for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct configurations.
  • issues/426581, issues/426603, issues/426206

• Build Failures Due to Missing or Incorrect Macros: These issues involve build failures caused by missing or incorrect macros, such as a missing 'AM_ICONV' macro for 'dvdauthor', a missing 'AM_NLS' macro for 'pcmanfm', and a missing 'AM_GNU_GETTEXT' macro for 'msmtp'. The resolution often involves updating the package configuration or providing the correct macros.
  • issues/426212, issues/425753, issues/426195

• Build Failures Due to Missing or Incorrect Features: These issues involve build failures caused by missing or incorrect features, such as missing features for 'vectorchord', missing features for 'redshift', and missing features for 'guile-lib'. The resolution often involves updating the package configuration or providing the correct features.
  • issues/426258, issues/426342, issues/425317

• Build Failures Due to Missing or Incorrect Capabilities: These issues involve build failures caused by missing or incorrect capabilities, such as missing capabilities for 'btop', missing capabilities for 'Electrum', and missing capabilities for 'surfer'. The resolution often involves updating the package configuration or providing the correct capabilities.
  • issues/424986, issues/426067, issues/426049

• Build Failures Due to Missing or Incorrect Permissions: These issues involve build failures caused by missing or incorrect permissions, such as missing permissions for 'Electrum', missing permissions for 'surfer', and missing permissions for 'btop'. The resolution often involves updating the package configuration or providing the correct permissions.
  • issues/426067, issues/426049, issues/424986

• Build Failures Due to Missing or Incorrect Paths: These issues involve build failures caused by missing or incorrect paths, such as a missing path for 'libavif', an incorrect path for 'libavif-config.cmake', and a missing path for 'bash-language-server'. The resolution often involves updating the package configuration or providing the correct paths.
  • issues/426487, issues/426581, issues/426603

• Build Failures Due to Missing or Incorrect Files: These issues involve build failures caused by missing or incorrect files, such as a missing file for 'bash-language-server', a missing file for 'msmtp', and a missing file for 'connman-gtk'. The resolution often involves updating the package configuration or providing the correct files.
  • issues/426605, issues/426195, issues/426206

• Build Failures Due to Missing or Incorrect Attributes: These issues involve build failures caused by missing or incorrect attributes, such as a missing 'fetcherVersion' attribute for 'pnpm.fetchDeps', a missing 'AM_ICONV' macro for 'dvdauthor', and a missing 'AM_NLS' macro for 'pcmanfm'. The resolution often involves updating the package configuration or providing the correct attributes or macros.
  • [issues/426301](

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.

1. Portable dependencies?
   • Toxicity Score: 0.65 (Frustration expressed, Accusations of trolling, Dismissive language, Technical disagreements.)
   • This GitHub conversation involves multiple users discussing a technical issue related to software compatibility on NixOS. The original poster expresses frustration about their program not working as intended on NixOS, despite it functioning on other Linux distributions. Several users, including @7c6f434c, provide technical advice and potential solutions, while others express skepticism about the approach and criticize the use of AI-generated solutions. The tone varies from helpful and collaborative to dismissive and confrontational, with some users accusing others of trolling. The conversation includes technical exchanges and attempts to resolve the issue, but also features moments of tension and disagreement.

---

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: 746

Key Open Pull Requests

1. python312Packages.mypy-boto3-*: updates: This pull request updates various mypy-boto3 packages for Python 3.12, including cloudfront, datasync, dynamodbstreams, ec2, ecs, events, glue, guardduty, iotwireless, logs, mediaconvert, mediapackagev2, opensearch, payment-cryptography-data, pricing, quicksight, s3, sagemaker, stepfunctions, synthetics, auditmanager, outposts, sesv2, and ssm, as well as boto3-stubs for Python 3.13, with version increments to ensure compatibility and incorporate the latest features and fixes.

• URL: pull/426460

• Merged: No

• Associated Commits: 2ac92, fa249, 774ab, 24f3b, 1c43a, 6ee4f, e23fd, e416a, e31c4, d136d, 6f79d, d3d26, 39eca, b8362, 630a0, ea20d, 01d1d, 97194, 85cee, a69a3, 8df0b, 39894, 64405, ec6b4, 72814, 3e254, 37479, c3e6c, 1dfb8, 06ae4, a958d, cf5ed, 08823, 1097a, cbda4, f8114, e5a36, c02f8, 0a8ba, 6b729, af7c3, 3d22e, de648, b4e18

2. treewide: move makeSetupHook top-level users to by-name: This pull request aims to reorganize the makeSetupHook users in the Nixpkgs repository by moving them from pkgs/top-level/all-packages.nix to a by-name structure, while also removing redundant hooks like pruneLibtoolFiles and separateDebugInfo that are already included in the standard environment, with the changes being reviewed commit-by-commit to ensure clarity and manage potential breaking changes.

• URL: pull/425903

• Merged: No

• Associated Commits: bb115, 198ed, 206d1, 6ac18, d9331, f0412, ca835, de979, e2681, a01cf, bab4e, 3b828, 6fbac, 8fcc8, a6126, bc498, 0ce4f, a140e, 27943, 90fd4, 659ee, 595e6, fab78, 211ab, ba496, ad0fc, 1f0c3, 1a53b, ddde5, 142b7, 01b8d, 3ae13, 77062, 01103

3. staging-next 2025-07-15: This pull request involves merging updates from the master branch into the staging-next branch of the NixOS/nixpkgs repository, including specific changes such as LibreOffice adjacent fixes and an update to nspr from version 4.36 to 4.37, while providing helpful links for workflow documentation and job status, and noting that there are no significant breakages reported so far.

• URL: pull/425387

• Merged: No

• Associated Commits: 40669, 6f8ef, 8ef58, 4b4be, 063b7, 2cdbe, f9668, b8dca, 7f9c6, d5b20, bb0f3, 88e9e, aec7c, 8cc55, c1cb6, 1888a, 08b1c, 959ae, 8fcc6

Other Open Pull Requests

• Evaluation Errors in NixOS/nixpkgs: This topic addresses evaluation errors by enabling warnings for x86_64-linux and fixing specific evaluation failures. It also adjusts the handling of asserts and throws to improve error visibility and package searchability, as part of resolving issue #397184.
  • pull/426629

• Building with mlibc: The pull request introduces initial support for mlibc in several components, such as gcc and bintools, enabling C++ support for mlibc platforms. It fixes build issues in packages like libseccomp and libgpg-error, and makes necessary adjustments to accommodate mlibc's requirements.
  • pull/426772

• Package Initialization and Updates: This topic covers the introduction and updates of various packages, including the initial version of "xfox" and updates to SDL3 and ibus packages. It involves restructuring, dependency cleanup, and addressing cross-compilation issues.
  • pull/425528, pull/425265

• Python Package Updates and Cleanup: This topic involves updating Python packages related to the Home Assistant project and cleaning up deprecated Python versions. It ensures compatibility and incorporates the latest features and bug fixes, while removing instances of disabled = pythonOlder.
  • pull/425268, pull/426616

• Systemd Module Configuration: The pull request aims to convert the extraConfig option in the NixOS systemd module to align with RFC 42. It introduces a new systemConfig option, migrating existing configurations and tests to use this new option.
  • pull/426692

• Segmentation Fault on Darwin: This pull request addresses a segmentation fault issue on Darwin systems by disabling the duplicate inclusion of OpenMP in the python3Packages.torch package. It reverts previous commits affected by this bug and disables specific tests in related packages.
  • pull/424873

• Backporting and Security Updates: This topic involves backporting updates to the "audit" package and addressing security vulnerabilities in the libxml2 library. It includes upgrading versions, adding support for plugins, and backporting patches for several CVEs.
  • pull/425015, pull/425246

• Terminal and Tool Initialization: This topic covers the initialization of Tabby Terminal and several Clang-related tools. It includes addressing issues such as release notes removal, syntax errors, and adding necessary Python packages and libraries.
  • pull/425256, pull/425936

• Versioning and Consistency: This pull request introduces versioning and ensures consistent permissions for the pnpm.fetchDeps function. It includes several commits that adjust parameter order and add a fetcherVersion for future tooling upgrades.
  • pull/425419

• Intel oneAPI Toolkits: The pull request introduces the Intel oneAPI base and HPC toolkits by reintroducing legacy package versions with minimal updates. It addresses installation challenges and seeks feedback on several implementation aspects.
  • pull/424900

• Haunt Package Refactoring: This pull request refactors the Haunt package by adopting best practices such as fetching the git source instead of a tarball. It enables tests, uses makeBinaryWrapper, and includes the contributor as a maintainer.
  • pull/426709

• Package Updates and Improvements: This topic covers updates to the "yaak" and "resumed" packages, addressing specific issues and introducing new features. It includes updating maintainer information and ensuring basic functionality on various platforms.
  • pull/424876, pull/425386

• Build System and Configuration Changes: This topic involves changes to the Meson build system configuration and modifications to the make-iso9660-image, make-squashfs, and make-system-tarball processes. It aims to modernize the build process and ensure self-contained outputs.
  • pull/424913, pull/425700

• New Package Introductions: This topic covers the introduction of new packages such as vlagent and lldap-bootstrap. It includes necessary integration tests, dependencies, and options for secure handling of important secrets.
  • pull/424934, pull/425923

• Package Modernization and Compatibility: This topic involves general improvements to the mods package and updates to the Mesa package. It includes replacing deprecated functions, enhancing installation processes, and introducing new dependencies.
  • pull/425744, pull/425843

• Click Package Update: This pull request proposes updating the Click package, acknowledging breaking changes introduced in version 8.2.0. It seeks advice on handling such updates and includes updates to related packages like Typer and Safety.
  • pull/425929

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: 883

Key Closed Pull Requests

1. python311Packages.scipy: fix build by disabling a test: This pull request addresses a build issue in the python311Packages.scipy package by disabling a specific test to ensure successful compilation on the x86_64-linux platform, as indicated by the title and the checklist in the body of the pull request.

• URL: pull/425898

• Merged: No

• Associated Commits: 7f963, e5484, 2f6b5, b5825, b034b, bf514, e2eae, 64f7d, 4eec0, 94a5e, 2a87e, f1757, 5e6b8, 9bf2f, a47f9, 8ff0a, 4bb25, 2c6c5, 7a1e3, cb7ff, 2d6d7, 3ec64, 75a11, b923d, 4ffb8, 22e84, 17fda, ebc63, bc884, 5e1b0, 30a3e, 2d01f, 44b40, 61601, 3a3a2, 47137, 1cb33, 8cccf, eabc1, 8acf8, 1cf01, 8420b, c7f63, a5b92, 6feae, cab9f, d597d, 80947, c03bc, df106, 32cf0, ad74c, 134c7, bd7c9, b8ba1, 77d2b, daca7, 6df72, e65c5, 61602, bf99a, a38a1, 47002, 3c0b2, 40958, 555a0, 23611, c482b, f0b7c, d0dcc, 2d092, 2d606, 1f613, 8f04c, c2047, 3417c, 5d71b, 4b476, 1141a, 756bb, 91661, e9d89, a2012, c2770, c43df, 062c2, cabae, 7311b, 00f92, f2c39, 45b01, db1a3, dc0de, bef2d, 8664a, e2540, d45f4, fc8fd, ec476, e69ff, 18cde, 39752, b7716, 27347, a69b6, 147a6, 3a36f, fb1da, 3da60, fcf8e, e5720, 20abd, 9c17e, 618a1, ff37f, eec48, ee2bb, 115e0, aea19, d256e, 6126e, d238e, 1cc7f, 78d95, ca61f, 405b3, 0c1b0, 08572, 7bca6, 14353, 967da, 62489, c5e9c, ee63d, f70b4, 6941c, b467d, f4614, 98f95, c71ca, 3f15d, 49324, bbe3c, 90c85, 303fa, 45ab6, eb998, faf3e, 0ac69, 9cf7c, b6fe7, 8b85e, c701b, d0a2b, 99c95, dfbd3, d601c, 0fc55, 3a8cd, 5ec62, 25cb1, a023a, 77dca, 82976, b113b, 8d357, e1017, cb4e8, a6b6b, cb6b8, 22a42, a8600, 04d7b, 13b34, ff9f3, dfafe, af15f, 5e8b1, 39327, 68d85, 8b627, 17a71, 2ea4b, ca15b, 2b52f, b5f6f, 1bc93, 2eae0, e73fd, e6703, 14d0e, 51ec2, 4c1ad, ce426

2. python3Packages.click: 8.1.8 -> 8.2.1: This pull request aims to update the Click package from version 8.1.8 to 8.2.1 in the NixOS/nixpkgs repository, acknowledging that version 8.2.0 introduced breaking changes and seeking advice on handling such updates due to the extensive dependencies on Click within the nixpkgs ecosystem.

• URL: pull/425926

• Merged: No

• Associated Commits: efbd6, f5e7f, c9eba, 37922, f9cc9, fff16, 78051, d5469, 6e762, fa9a2, feb97, f7543, 2b78f, e316a, 26555, 85181, 1506d, f4a28, 10ac3, be2dc, 57449, 841ee, dc7cb, 24fad, e3af2, 17c8f, 4ee13, d8ec5, bd0cf, 2f83e, 922be, 2569d, 68b93, b2b49, 6e23b, 8c6e8, 8c5d6, 32828

3. GNOME updates 2025-07-13: This pull request involves a series of updates to various GNOME-related packages within the NixOS/nixpkgs repository, including version upgrades for applications such as Evince, GNOME Builder, GNOME Shell, and Nautilus, among others, with the aim of incorporating bug fixes, performance improvements, and security enhancements, such as addressing a potential heap overflow in Evince.

• URL: pull/424850

• Merged: Yes

• Associated Commits: bceb8, 321ff, d877c, 2aeba, 8391b, 25650, 22426, 5d868, 4fed9, f1ad3, 859ad, ea744, d670c, 65a03

Other Closed Pull Requests

• Vulkan SDK Updates: This topic involves updating various components of the Vulkan SDK to version 1.4.321, including a Qt6 upgrade for vulkan-tools-lunarg. The updates also include trivial version bumps for several packages such as glslang, vulkan-headers, and vulkan-loader, with testing conducted on the x86_64-linux platform.
  • pull/425870

• Backporting Updates and Fixes: This topic covers backporting updates and fixes to various packages, including "froide-govplan" and "teams-for-linux." These updates address version updates for dependencies, cross-compilation issues, and compatibility with newer versions, while also introducing new packages and making necessary adjustments.
  • pull/425325, pull/425580

• Lomiri Ecosystem Build Fixes: This topic addresses build failures across the Lomiri ecosystem by updating components to require C++17 due to a GTest bump. It also resolves a lingering glib gettext macro issue, with multiple commits changing the C++ standard and applying necessary patches for compatibility.
  • pull/426506

• Anubis Package Updates: This topic involves backporting updates to the Anubis package from version 1.19.1 to 1.21.0 into the release-25.05 branch. The updates incorporate changes such as formatting adjustments, package restructuring, metadata additions, and maintenance updates to ensure compatibility and address ongoing abuse issues.
  • pull/426666

• GitHub Script Enhancements: This topic enhances the local testing environment for GitHub scripts by refactoring and relocating the labels.js script to ci/github-script. It introduces a reusable rate-limiting functionality, enables single pull request testing, and adds a non-dry mode for more efficient script testing and development.
  • pull/424872

• Grafana Plugins Updates: This topic updates several Grafana plugins within the NixOS/nixpkgs repository to their latest versions. The updates ensure improved functionality and compatibility for plugins such as grafana-lokiexplore-app, grafana-oncall-app, and others.
  • pull/425032

• Linux Kernel Version Updates: This topic involves updating various Linux kernel versions within the NixOS/nixpkgs repository as part of routine maintenance and improvements. The updates include increments for multiple kernel versions, ensuring the system remains up-to-date and secure.
  • pull/426155, pull/425140

• Electron Package Updates: This topic addresses updates to the Electron packages, specifically electron-source, electron-bin, and electron-chromedriver for versions 35 and 37. The updates fix issues caused by a removed upstream release and include updates to Chromium version 138.0.7204.100.
  • pull/425750

• Check-Cherry-Picks Job Improvements: This topic addresses various bug fixes and improvements for the "check-cherry-picks" job. The improvements include ignoring whitespace in patch diffs, blocking merges on errors, maintaining markdown formatting, and clarifying review comments.
  • pull/425789

• Stdenv.mkDerivation Enhancements: This topic ensures that derivations built with stdenv.mkDerivation include an assertion that the env parameter is a non-derivation attribute set. It resolves issue #425858 and involves renaming env to rubyEnv in several packages to comply with this new requirement.
  • pull/426211

• Git Vulnerability Fixes: This topic addresses a recent critical vulnerability in git by migrating several packages that use git as a check input to gitMinimal. This migration reduces the number of rebuilds required and allows for more efficient and conditional CVE fixes directly on the master branch.
  • pull/426610

• NixOS Postsrsd Module Enhancements: This topic involves enhancing the NixOS postsrsd module by migrating to RFC42 settings for a more flexible configuration. It implements a comprehensive hardening setup for the systemd unit and integrates postsrsd with postfix by default.
  • pull/424954

• GitHub Pull Request Template Improvements: This topic focuses on improving the readability and usability of the GitHub pull request template. The improvements include shortening its content, removing unnecessary elements, and relocating certain details to the contribution guidelines.
  • pull/425831

• Visual Studio Code Package Updates: This topic involves backporting updates to the Visual Studio Code package from version 1.101.0 to 1.102.1 in the NixOS/nixpkgs repository. The updates incorporate changes from several previous commits to ensure the package is up-to-date and compatible with the release-25.05 branch.
  • pull/425888

• SrcOnly Function Enhancements: This topic addresses the differentiation between computed and user-passed drvAttrs in the srcOnly function. It utilizes overrideAttrs to fix issues related to attribute duplication and consistency checks, particularly resolving problems with __impureHostDeps.
  • pull/425937

• Electrum Package Updates: This topic updates the Electrum package from version 4.5.8 to 4.6.0 and introduces new dependencies such as electrum-ecc and electrum-aionostr. It also includes a fix for building the zbar package on Darwin platforms.
  • pull/426336

• Glab Package Updates: This topic updates the glab package from version 1.61.0 to 1.62.0, including several improvements such as showing a short commit ID when executing glab version. It also fixes the checkPhase by adding a missing git dependency and disables update checks and telemetry by default.
  • pull/426485

• Common Lisp Package Updates: This topic updates the Common Lisp package expressions in the Nixpkgs repository following the recent Quicklisp release. It incorporates a nixfmt step to maintain consistent formatting and addresses build issues for specific packages.
  • pull/424897

• Polypane Browser Reintroduction: This topic reintroduces the Polypane browser to the Nixpkgs repository at version 25.0.1 after it was previously removed due to lack of maintenance. It is now packaged using pkgs/by-name and includes updates to the maintainers list and formatting corrections.
  • pull/424933

• Nixfmt Updates: This topic updates Nixfmt to its stable 1.0.0 release and modifies the update script to use stable versions. It transitions pkgs.nixfmt to the -rfc-style version while removing the warning and includes several commits that adjust documentation and update scripts.
  • pull/425068

• Ncspot Package Updates: This topic involves backporting changes to the NixOS/nixpkgs repository, specifically updating the ncspot package from version 1.2.2 to 1.3.0. The updates include cleaning up the package by using finalAttrs, removing fetchCargoVendor, and implementing versionCheckHook.
  • pull/425276

• Docling Package Updates: This topic updates several packages related to "docling," including "docling-ibm-models," "docling-core," "docling," and "docling-serve." The updates ensure the packages are up-to-date, although "docling-serve" is not updated to its latest version due to a new dependency not yet available in nixpkgs.
  • pull/425736

• Python Package Updates: This topic updates several Python packages within the NixOS nixpkgs repository, specifically upgrading aiosmb, asysocks, minikerberos, and asyauth. Each update is linked to their respective changelogs to ensure maintainers are aware of any significant changes or potential breaking updates.
  • pull/425922

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.

1. maintainers: drop emaryn

   • Toxicity Score: 0.75 (Personal insults, Accusatory tone, Ad hominem attacks, Tense atmosphere.)
   • This GitHub conversation involves a user expressing dissatisfaction with the community's response to their contributions, highlighting feelings of disappointment and exhaustion due to perceived misalignment with community values. The user describes experiences of nitpicking, criticism, and personal insults, which they feel have created an oppressive atmosphere. The tone of the conversation is tense, with the user feeling that discussions often devolve into personal attacks rather than focusing on technical merits.

2. jdk8: disable structuredAttrs

   • Toxicity Score: 0.55 (Dismissive tone, Frustration, Potential undervaluation of efforts.)
   • This GitHub conversation involves a user expressing strong dissatisfaction with a proposed solution, describing it as a "horrible hack" and showing a lack of interest in understanding its benefits. The tone is dismissive and frustrated, which could potentially trigger tension among contributors who may feel their efforts are undervalued.

---

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	2481	1538	0	0
acid-bong	33	4	1	371
wolfgangwalther	193	29	3	170
fabaff	219	44	0	1
Prince213	128	19	0	46
K900	140	19	1	26
mweinelt	132	19	0	29
dotlambda	76	31	0	46
GaetanLepage	109	24	0	8
Aleksanaa	54	5	2	78