| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
bitlbee.pc requires glib, so all packages that depend on bitlbee will
also depend on glib.
|
| | |
|
| |
|
|
| |
(cherry picked from commit c37347af7eaa0177e3a374dd94158ff546f20fdb)
|
| |
|
|
| |
(cherry picked from commit 751c2ed6e4af9e525fe57b7c0f0ee8a611eab9fa)
|
| |
|
|
|
|
|
|
|
| |
This option has been deprecated for a long time because is redundant
(users.users.root.initialHashedPassword exists).
Moreover, being of type string, it required to handle the special value
"!" separately, instead of using just `null`.
(cherry picked from commit a6ed7d4845f1142f36b2c461d5a721bc68eb7d48)
|
| |
|
|
|
|
|
| |
SJW brigade represent. ;)
Co-authored-by: Jan Tojnar <jtojnar@gmail.com>
(cherry picked from commit 517be841352ec3e6b236e7cdfb1fbd8e26bf49cb)
|
| |
|
|
|
|
| |
This is the last nixos-unstable release before 13b2903169f, which I'm a
bit nervous about. So I want the update including that one to be as
small as possible, hence going to this one first.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the nixlib root is the NIX_PATH root, overlays were in the
NIX_PATH as "nixpkgs-overlays". Nixpkgs imports that by default to
look for overlays. This meant that an arbitrary Nixpkgs tree would
end up trying to use the Nixlib overlays, which wouldn't always work.
It would also mean that derivations built from those trees wouldn't
match the ones other people would try to build, which is undesirable
for working on nixpkgs. I think this is unfortunate behaviour for
anybody working on nixpkgs, and nixpkgs probably shouldn't load
overlays from impurely at all by default, but it is what it is.
Since I can't really change what upstream nixpkgs does here, the best
I can do is change the nixpkgs in nixlib. It will now load overlays
from a sibling "overlays" directory. Renaming the "nixpkgs-overlays"
directory at the nixlib root to "overlays" means that it will be
loaded by default _only_ by the nixpkgs it is colocated with. It also
means that it is still accessible in the NIX_PATH as <overlays>, which
is fine and convenient as long as nothing starts looking at that by
default.
|
| |
|
|
| |
(cherry picked from commit 7a8434c710c2bf9310d9b21988bc4ee2ac683d04)
|
| |
|
|
| |
(cherry picked from commit 0e13f49e7c55268fcdca81cec53d879150d39264)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also enable tests, which seem to work now.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
(cherry picked from commit f2fd4a4129c37b6ea7eea461f909a05246c3a280)
|
| | |
|
| |
|
|
| |
url: 1.6.0 -> 1.7.2
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This needs to be defined as an attribute set two layers deep so that
multiple settings in the same namespace, declared in two different
modules, will be merged together.
For example, the following previously wouldn't be merged properly:
{ ... }:
{
imports = [ (
{ ... }: {
services.public-inbox.config.publicinbox.listid = "foo.example.com;
}
) ];
services.public-inbox.config.publicinbox.css =
"https://example.com/pi.css";
}
|
| |
|
|
| |
cgit now supports lzip and zstd compression.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows (manually) composing packageOverrides, like so:
python3.override {
packageOverrides =
lib.composeExtensions python3.packageOverrides (final: super: { ... });
}
This is still not great, but without this, you can't use
packageOverrides twice at all, because the second use just clobbers
the first with no way to make sure the first override is applied as
well.
|
| |
|
|
|
|
|
| |
This makes it so that if I apply a patch to Django using
packageOverrides, it's applied to python3.pkgs.python.pkgs.django
(and python3.pkgs.python.pkgs.python.pkgs.django) as well as
python3.pkgs.django.
|
| |
|
|
|
|
|
| |
A *good* fix for this problem looks to be a long way off. But I need
my certificates to not expire until that happens.
Fixes: https://github.com/NixOS/nixpkgs/issues/48845
|
| |
|
|
|
|
|
|
|
|
| |
* gnupg: use libusb1
This fixes scdaemon's direct ccid support.
* systemd: fix gnupg-minimal
(cherry picked from commit 6673a4988e4a4ff25ca94a84d8e2acf92453dbf1)
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
We don't want /srv on NixOS, and /home is already created by
users-groups.nix.
Furthermore, systemd tmpfiles are set up post-activation, and so
there's absolutely no way for a user to override them. They can't
even set their own rules in systemd.tmpfiles, because "home.conf"
comes before "nixos.conf" lexicographically, and so systemd always
picks the "home.conf" ones.
|
| |
|
|
| |
(cherry picked from commit ca2a222747bd14d0f477b8eb231eda68355ca240)
|
| |
|
|
| |
For man pages.
|
| |
|
|
| |
This way, we can use StateDirectory instead of a tmpfile rule.
|
| |
|
|
|
|
|
|
|
|
| |
There are lots of other scripts in contrib that we should probably
also install, but I didn't feel like taking the time to review them
all and figure out what dependencies they would need.
It would have been a shame to add a mandatory dependency on Ruby (and
all that entails) to a package that otherwise has basically no
dependencies, so I've made the Ruby dependency optional.
|
| |
|
|
|
|
|
|
|
|
| |
The upstream version bound of <2.2 is overly pessimistic, and
mailman-web works just fine on Nixpkgs' default Django 2.2. I've
applied a patch to relax the bound, which I have also sent
upstream[1] (which is why I included the patch rather than just doing
another sed).
[1]: https://gitlab.com/mailman/mailman-web/-/merge_requests/2
|
| | |
|
| |
|
|
| |
(cherry picked from commit 48e6a3f1f16f29a30e34331a101ea40b535a784f)
|
| |
|
|
|
|
| |
# Conflicts:
# nixpkgs/pkgs/build-support/rust/default.nix
# nixpkgs/pkgs/development/go-modules/generic/default.nix
|
| | |
|
| |
|
|
|
|
| |
Fixes #76927 (second try)
(cherry picked from commit 664c02c89bdafd21e9d0cf4d16baceeb70003185)
|
| |
|
|
|
|
|
|
| |
This enables to compile rls and rustc
See also https://github.com/rust-lang/rust/pull/64823
(cherry picked from commit 47681d7c5c9529615e9f481f02d945a2c3cfe599)
|
| | |
|
| |
|
|
| |
Warns about loaOf deprecation warning.
|
| | |
|