-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Staging next #71221
Staging next #71221
Conversation
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/poppler-utils/versions
https://lists.infradead.org/pipermail/libnl/2019-September/002415.html FWIW: > The previous 3.4.0 release was in October 2017
Builds, at least, without it :).
https://lists.x.org/archives/xorg-announce/2019-June/003000.html > This release boasts a bunch of cleanup work and a few new keysyms. No functional changes to any of the protocols.
There is a bug in this feature: It allows extra arguments to leak in from the environment. For example: $ export extraFlagsArray=date $ man ls Note that you get the man page for date rather than for ls. This happens because 'man' happens to use a wrapper (to add groff to its PATH). An attempt to fix this was made in 5ae1857 in PR #19328 for issue #2537, but 1. That change didn't actually fix the problem because it addressed makeWrapper's environment during the build process, not the constructed wrapper script's environment after installation, and 2. That change was apparently accidentally lost when merged with 7ff6eec. Rather than trying to fix the bug again, we remove the extraFlagsArray feature, since it has never been used in the public repo in the ten years it has been available. wrapAclocal continues to use its own, separate flavor of extraFlagsArray in a more limited context. The analogous bug there was fixed in 4d7d10d in 2011.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/xonsh/versions
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/xdg-dbus-proxy/versions
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/zerotierone/versions
xonsh: 0.9.10 -> 0.9.11
zerotierone: 1.4.4 -> 1.4.6
xdg-dbus-proxy: 0.1.1 -> 0.1.2
apparmor: 2.13.1 -> 2.13.3
GO 1.12.10 has been released 5 days ago, so bumping it in the hope that it also fixes some flakey GC tests. Also see #69359
go_1_12: 1.12.9 -> 1.12.10
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/wavebox/versions
Patches have been imported into nixpkgs and manually edited to avoid merge conflicts on ChangeLog / NEWS files.
So there's a distinct difference in the shebangs on darwin after the update Before
After
I overlooked that python.withPackages creates a wrapper and scripts are not allowed in shebangs. I believe if I satiate in any other way the issue will be fixed 👍 (pr incoming once I test on darwin) |
@hedning gtk3 keeps timing out causing the majority of newly failing builds |
Bisected it to libsass ugrade: e4b4ff8. Pretty sure it's this sass/libsass#3006, as the timed out logs doesn't contain
|
This hangs when generating gtk3 templates. sass/libsass#3006 This reverts commit e4b4ff8.
I think they plan to make theme generation required in the future, and not have it pre-generated in the tarball. Though I can't remember the PR. |
We can't use shell scripts as shebangs so we drop using .withPackages and just add pygments to the build env to satiate meson's checks. #71221 (comment)
gtk-doc: fix on darwin
This broke after 979811f. Adding the `installTarget` locally works. Couldn't find any other reproducible breakage.
@hedning i see your request :) |
My bad, no idea how that happened :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
poppler bump breaks poppler (trivially) and texlive.bin.core (non-trivially)
I had some progress with fixing texlive by applying
https://git.archlinux.org/svntogit/packages.git/plain/texlive-bin/trunk/pdftex-poppler0.76.patch?id=8cb784073cfd2299a6c301ce7bb0d89126a47f4e
But then I'm stuck at a luatex build failure that archlinux doesn't address.
@veprbl perhaps revert poppler bump for now? |
relies on zope-testrunner. Import fails, likely because of how zope-testrunner functions.
The poppler bump fixes a security issue, so if you decide to keep this reverted then please open a new issue. |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @