| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |\ \ \
| |/ /
|/| /
| |/
| | |
obsidiansystems/deprecate-top-level-platform-aliases
top-level: Deprecate top-level `{build,host,target}Platform`
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
I don't know when we can/should remove them, but this at least gets
people to stop using them. The preferred alternatives also date back to
17.09 so writing forward-compatable code without extra conditions is
easy.
Beginning with these as they are the least controversial.
|
| |/ |
|
| |\
| |
| | |
Section ids
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
nodePackages: 6_x -> 8_x
|
| | | |
|
| |\ \
| | |
| | | |
doc: add installCheckTarget and installCheckFlags to manual
|
| | | |
| | |
| | |
| | | |
Fixes #42393
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
obsidiansystems/dont-use-obsolete-platform-aliases
treewide: Dont use obsolete platform aliases
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Want to get this out of here for 18.09, so it can be deprecated
thereafter.
|
| | | |/
| |/|
| | |
| | | |
It is deprecated and will be removed after 18.09.
|
| | | |
| | |
| | |
| | | |
https://github.com/NixOS/nixpkgs/pull/45822#issuecomment-417566642
|
| |/ /
| |
| |
| | |
cc @FRidh, @dotlambda
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
Clarify the issue encountered at
https://github.com/NixOS/nixpkgs/issues/45503
|
| | | |
|
| |\ \ |
|
| | |\ \
| | | |
| | | |
| | | | |
Hydra: ?compare=1473892
|
| | |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts: gobby and libinfinity - I took the hand-edited versions
instead of those resuting from the mass-replacement.
Hydra: ?compare=1473190
|
| | |\ \ \ \ |
|
| | |\ \ \ \ \ |
|
| | |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
treewide: All configureFlags are lists
|
| | | | | | | | | |
|
| | |\| | | | | | |
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
where required
|
| | |_|_|_|_|/ /
|/| | | | | | |
|
| |\ \ \ \ \ \ \
| |_|_|_|_|/ /
|/| | | | | | |
buildRustPackage: allow patches to fix Cargo.lock
|
| | | | | | | | |
|
| | |_|_|_|/ /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Staging next
|
| | |\ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
There's been some large rebuild on master.
I don't really have time ATM to find what it was.
|
| | |\ \ \ \ \ \ \
| | |_|_|/ / / /
| |/| | | | / /
| | | |_|_|/ /
| | |/| | | | |
|
| | | | | | | | |
|
| | |_|/ / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Since #44522 it's possible to specify custom certificates for the Citrix
receiver. As it took me some time to create a proper setup Citrix can
behave fairly unexpected.
I mostly covered two aspects:
* Don't install Citrix with `nix run`: when `citrix.desktop` is linked
to $XDG_CONFIG_DIRS, it's possible to start a session directly from the
browser when loading `.ica` files which makes the usage *way* easier.
* It's possible to add custom certificates using the Citrix wrapper. A
new store path with the original derivation and the certificates will be
created and therefore no rebuild of the package is needed when adding
new certs.
|
| |\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
doc: Fixes mentions of mention-bot.
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Its last mention was on 2017-09-25. Close to a year.
The CODEOWNERS feature of github, though, fills in the gap in a more
appropriate manner (IMHO).
|
| | |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The server is not verified over the git:// transfer protocol. If you
clone a repository over git://, you should check if the latest commit's
hash is correct.
On the other hand, https:// will always verify the server automatically,
using certificate authorities.
|
| |/ / / |
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Use example package `zerobin` instead of `bepasty-server` which
is no longer part of python-packages.
This fixes the examples for current nixpkgs versions.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1. Use the same approach like in the overlay example:
Override `python` instead of `pythonPackages` so that
`python.pkgs` refers to the new package set like `pythonPackages`.
This also fixes a bug in the original example where
`pkgs.fetchgit` was not in scope.
Add an extra example to illustrate how to override just a
package set.
2. Fix mix-up between `super` and `self` in the explanation text.
Also, simplify the explanation.
|
| | |
| |
| |
| | |
The `pythonPackages` definition is redundant
|
| | | |
|
| |\ \
| | |
| | | |
[bot] treewide: remove unreferenced code
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This makes the command ‘nix-env -qa -f. --arg config '{skipAliases =
true;}'’ work in Nixpkgs.
Misc...
- qtikz: use libsForQt5.callPackage
This ensures we get the right poppler.
- rewrites:
docbook5_xsl -> docbook_xsl_ns
docbook_xml_xslt -> docbook_xsl
diffpdf: fixup
|