Conversation
This commit has been generated by maintainers/scripts/haskell/mark-broken.sh based on *evaluation [1816057](https://hydra.nixos.org/eval/1816057) of nixpkgs commit [028a94b](https://github.com/NixOS/nixpkgs/commits/028a94be88e833c919631df2973a00ec008062a8) as of 2025-06-23 09:22 UTC* from the haskell-updates jobset on hydra under https://hydra.nixos.org/jobset/nixpkgs/haskell-updates
Since the shebang calls nix-shell, we can safely assume that Nix (Lix, C++ Nix) is installed. Our scripts should support a wide enough range of Nix versions so that using the “impure” version of the tool is not a problem. This works around #400784. My theory is that the Nix frontend commands no longer work with older versions of the Nix daemon nor the Lix daemon in our workloads.
- Add test to ensure ability to patch read-only-files (see #414448 (comment)) - Add test to ensure the timestamp is preserved - Add test to ensure read-only permissions are preserved
Fixes a regression introduced by c1cc6ff where patchShebangs would crash if a file is read-only
This package is affected by the same problem as jpeg-turbo, missing test files in the sdist.
Interestingly, this did not break anything super obvious before, but now paths between GHC and separate libraries match.
Upstream builds with Gradle now, so yay, we can use normal tooling. Also no more JDK8.
`dev` output unchanged (verified by `diffoscope`). `out` output still contains all the translation files, with no obvious encoding issues i spotted. Slight deviations in the metadata, but should be fine. Fixing the build with modern gettext requires replacing the obsolete glib gettext. Fixing the build with modern autoconf requires making IT_PROG_INTLTOOL unconditional, hence the indent changes in the patch.
The next haskellPackages bulk update will also resolve this, but picking the patch will prevent a broken git-annex until the next staging-next is merged into master.
Upstream doesn't support 3.5 yet.
This sucks, but 3.0 is too old, 3.5 is too new, and we're not shipping 3.4 just for this.
`glib` gettext is deprecated and currently broken. This fixes the build by using regular gettext instead.
Member
|
I can't pin it down to a specific commit for now, but – according to Details: Excerpt from the build logs: I'm working on a minimal reproducible example. |
13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Helpful links
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
Important breakages
nothing notable so far