pyrox.dev
1name: "Build failure"
2description: "Report a package that is failing to build."
3title: "Build failure: PACKAGENAME"
4labels: ["0.kind: build failure"]
5body:
6 - type: "markdown"
7 attributes:
8 value: |
9 <p align="center">
10 <a href="https://nixos.org">
11 <picture>
12 <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/NixOS/nixos-artwork/refs/heads/master/logo/nixos.svg">
13 <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/NixOS/nixos-artwork/refs/heads/master/logo/nixos-white.svg">
14 <img src="https://raw.githubusercontent.com/NixOS/nixos-artwork/refs/heads/master/logo/nixos.svg" width="400px" alt="NixOS logo">
15 </picture>
16 </a>
17 </p>
18
19 Welcome to Nixpkgs. Please replace the **`Build failure: PACKAGENAME`** template above with the correct package name (As seen in the [NixOS Package Search](https://search.nixos.org/packages)).
20
21 > [!TIP]
22 > For instance, if you were filing a build failure against the [`hello`](https://search.nixos.org/packages?channel=unstable&from=0&size=1&buckets=%7B%22package_attr_set%22%3A%5B%22No%20package%20set%22%5D%2C%22package_license_set%22%3A%5B%22GNU%20General%20Public%20License%20v3.0%20or%20later%22%5D%2C%22package_maintainers_set%22%3A%5B%5D%2C%22package_platforms%22%3A%5B%5D%7D&sort=relevance&type=packages&query=hello) package, your title would be as follows:
23 > ```
24 > Build failure: hello
25 > ```
26
27 ---
28 - type: "dropdown"
29 id: "version"
30 attributes:
31 label: "Nixpkgs version"
32 description: |
33 In what version of Nixpkgs did the build failure occur?
34
35 If you are using an older version, please update to the latest stable version and check if the build failure persists before continuing this report.
36
37 If you are purposefully trying to build an ancient version of a package in an older Nixpkgs, please coordinate with the [NixOS Archivists](https://matrix.to/#/#archivists:nixos.org).
38 options:
39 - "Please select a version."
40 - "- Unstable (25.11)"
41 - "- Stable (25.05)"
42 default: 0
43 validations:
44 required: true
45 - type: "textarea"
46 id: "how-to-reproduce"
47 attributes:
48 label: "Steps to reproduce"
49 description: "Please include a step-by-step guide for reproducing this build failure. Consider writing in concise, numbered bullet points to ensure that Nixpkgs developers can retrace your steps."
50 validations:
51 required: true
52 - type: "dropdown"
53 id: "hydra"
54 attributes:
55 label: "Can Hydra reproduce this build failure?"
56 description: |
57 Can [Hydra](https://hydra.nixos.org), Nixpkgs' Continuous Integration system, reproduce this build failure?
58 Please use the search function in the header bar to locate the last build job for the package in question.
59 - If there's a <img src="https://raw.githubusercontent.com/NixOS/hydra/refs/heads/master/src/root/static/images/emojione-red-x-274c.svg" width="20px" align="top" alt="Red X"> icon near the package entry, say '**Yes, Hydra can reproduce this build failure.**'
60 - If there's a <img src="https://raw.githubusercontent.com/NixOS/hydra/refs/heads/master/src/root/static/images/emojione-gray-x-2716.svg" width="20px" align="top" alt="Dark Gray X"> icon near the package entry, then the build failure occurs with another package, and you need to track the original failing package by going down the chain of 'Cached failures' until you reach the final package in the failing dependency chain. Once you locate the failing package, re-write this report against that package and say '**Yes, Hydra can reproduce this build failure.**'
61 - If there's a <img src="https://raw.githubusercontent.com/NixOS/hydra/refs/heads/master/src/root/static/images/emojione-check-2714.svg" width="20px" align="top" alt="Green Check Mark"> icon near the package entry, then it most likely means it's a local issue with your system. (Maybe you ran out of space?)
62 You can still open a build failure report, but please say '**No, Hydra cannot reproduce this build failure.**' below.
63 - If there's a <img src="https://raw.githubusercontent.com/NixOS/hydra/refs/heads/master/src/root/static/images/emojione-question-2754.svg" width="20px" align="top" alt="Gray Question Mark"> icon near the package entry, say '**Hydra is currently rebuilding this package.**'
64 - If there's a <img src="https://raw.githubusercontent.com/NixOS/hydra/refs/heads/master/src/root/static/images/emojione-stopsign-1f6d1.svg" width="20px" align="top" alt="Red Stop Sign"> icon near the package entry, then the build job was stopped manually. If this occurs, please coordinate with the [Infrastructure Team](https://matrix.to/#/#infra:nixos.org), and say '**The last build job was manually cancelled.**'
65 - If Hydra isn't supposed to build the package at all, say '**Hydra doesn’t try to build the package.**'
66 options:
67 - "Please select the Hydra Status."
68 - "Yes, Hydra can reproduce this build failure."
69 - "No, Hydra cannot reproduce this build failure."
70 - "Hydra is currently rebuilding this package."
71 - "The last build job was manually cancelled."
72 - "Hydra doesn’t try to build the package."
73 default: 0
74 validations:
75 required: true
76 - type: "input"
77 id: "hydra-logs"
78 attributes:
79 label: "Link to Hydra build job"
80 description: "If you answered 'yes' in the question above, please copy-and-paste the link to the failing Hydra job here."
81 validations:
82 required: false
83 - type: "textarea"
84 id: "logs"
85 attributes:
86 label: "Relevant log output"
87 description: |
88 Please copy and paste the logs from the failed build.
89 This will be automatically formatted into code, so no need for backticks.
90 render: "console"
91 validations:
92 required: true
93 - type: "textarea"
94 id: "additional-context"
95 attributes:
96 label: "Additional context"
97 description: "Add any other context about the problem here."
98 validations:
99 required: false
100 - type: "textarea"
101 id: "metadata"
102 attributes:
103 label: "System metadata"
104 description: "Please run `nix-shell -p nix-info --run \"nix-info -m\"` on a terminal and paste the output of that command here."
105 validations:
106 required: true
107 - type: "textarea"
108 id: "maintainers"
109 attributes:
110 label: "Notify maintainers"
111 description: |
112 Please mention the people who are in the **Maintainers** list of the offending package. This is done by by searching for the package on the [NixOS Package Search](https://search.nixos.org/packages) and mentioning the people listed under **Maintainers** by prefixing their GitHub usernames with an '@' character. Please add the mentions above the `---` characters in the template below.
113 value: |2
114
115
116 ---
117
118 **Note for maintainers:** Please tag this issue in your pull request description. (i.e. `Resolves #ISSUE`.)
119 validations:
120 required: false
121 - type: "checkboxes"
122 id: "sanity-check"
123 attributes:
124 label: "I assert that this issue is relevant for Nixpkgs"
125 description: |
126 This bug tracker is for actionable issues that are not the result of user error. If you need help using your system and are unsure if this is a bug with Nixpkgs, please consider asking for help on the [NixOS Discourse](https://discourse.nixos.org/) or the [NixOS Matrix Space](https://matrix.to/#/#community:nixos.org) before opening an issue.
127 options:
128 - label: "I assert that this is a bug and not a support request."
129 required: true
130 - label: "I assert that this is not a [duplicate of an existing issue](https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aissue+label%3A%220.kind%3A+build+failure%22). "
131 required: true
132 - label: "I assert that I have read the [NixOS Code of Conduct](https://github.com/NixOS/.github/blob/master/CODE_OF_CONDUCT.md) and agree to abide by it."
133 required: true
134 - type: "markdown"
135 attributes:
136 value: |
137 # Thank you for helping improve Nixpkgs!
138
139 ---
140 - type: "textarea"
141 id: "prioritisation"
142 attributes:
143 label: "Is this issue important to you?"
144 description: |
145 **Please do not modify this text area!**
146
147 This template helps Nixpkgs developers know which issues should be prioritised by allowing users to vote with a :+1: reaction.
148 This is not a guarantee that highly-requested issues will be fixed first, but it helps us to figure out what's important to users. Please react on other users' issues if you find them important.
149 value: |
150 Add a :+1: [reaction] to [issues you find important].
151
152 [reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/
153 [issues you find important]: https://github.com/NixOS/nixpkgs/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc