| Commit message (Collapse) | Author | Age |
|
|
|
| |
It has long been deprecated
|
|
|
|
| |
These are no longer used by anything
|
|
|
|
|
|
| |
Fixes CVE-2017-0379
See http://lists.gnu.org/archive/html/info-gnu/2017-08/msg00014.html
for release announcement
|
|\
| |
| | |
darwin attribute cleanup
|
| | |
|
| | |
|
|\ \
| |/
|/| |
gettext: libiconv should be a buildInput
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This becomes necessary if more wrappers besides cc-wrapper start
supporting hardening flags. Also good to make the warning into an
error.
Also ensure interface is being used right: Not as a string, not just in
bash.
|
| |
| |
| |
| |
| |
| | |
GCC just passes `-z ...` flags to ld unaltered, and they are already
passed to LD anyways. On the other hand, `-pie` affects gcc behavior
too.
|
|\ \
| |/
|/| |
ncurses: put tic binary in bin
|
| | |
|
|\ \
| | |
| | | |
gnome-disk-utility: fix missing schemas for gnome-disk-image-mounter
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Continuation of #28053
gnome-disk-image-mounter from gnome-disk-utility was not wrapped, resulting in an
error due to the inability to find gsettings schemas.
This commit replaces the manual wrapping of gnome-disks binary with wrapGAppsHook
so that all binaries are wrapped correctly.
|
|\ \ \
| | | |
| | | | |
CoreFoundation: use rpath to fix issues when using frameworks
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This will get propagated down to other libraries loaded because
everything in nixpkgs references CF based on an rpath entry.
|
| | | |
| | | |
| | | |
| | | | |
NIX_COREFOUNDATION_RPATH
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
At least for now. It would increase the ISO size by ~10 MB,
after the fixup in the parent commit.
|
| | | | |
|
| |/ /
|/| | |
|
|\ \ \
| | | |
| | | |
| | | | |
There were some conflicts in python modules, commented at #28314.
|
| |\ \ \
| | | | |
| | | | | |
Mednafen: 0.9.38.7 -> 0.9.47
|
| | | | |
| | | | |
| | | | |
| | | | | |
And some minor changes
|
| | | | |
| | | | |
| | | | |
| | | | | |
And some minor modifications
|
| | | | |
| | | | |
| | | | |
| | | | | |
not yet compatible according to upstream
|
| |\ \ \ \
| | | | | |
| | | | | | |
ply: Allow building for git-fetched kernels
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Additional CUPS drivers can be added via "services.printing.drivers" but
Gutenprint was an exception. It was possible to add a Gutenprint
derivation to that list and it would work at first but unlike the other
drivers Gutenprint requires a script to be run after each update or any
attempt to print something would simply fail and an error would show up
in the jobs queue (http://localhost:631/jobs/):
"The PPD version (5.2.11) is not compatible with Gutenprint 5.2.13.
Please run
`/nix/store/7762kpyhfkcgmr3q81v1bbyy0bjhym80-gutenprint-5.2.13/sbin/cups-genppdupdate'
as administrator."
This is due to state in "/var/lib/cups/ppd" and one would need to run
"/nix/store/.../bin/cups-genppdupdate -p /var/lib/cups/ppd" manually.
The alternative was to enable the following option:
"services.printing.gutenprint" but this had two disadvantages:
1) It is an exception that one could be unaware of or that could
potentially cause some confusion.
2) One couldn't use a customized Gutenprint derivation in
"services.printing.drivers" but would instead have to overwrite
"pkgs.gutenprint".
This new approach simply detects a Gutenprint derivation in
"services.printing.gutenprint" by checking if the meta set of a
derivation contains "isGutenprint = true". Therefore no special
exception for Gutenprint would be required and it could easily be
applied to other drivers if they would require such a script to be run.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes #26611.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
what the..
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Progress on: #28643
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
lilypond-unstable: 2.19.24 -> 2.19.65
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
xpdf: 3.04-> 4.00
|
| | | | | | | | |
|
| | | | | | | | |
|