about summary refs log tree commit diff
path: root/nixpkgs/pkgs
Commit message (Collapse)AuthorAge
* Merge commit '9480bae337095fd24f61380bce3174fdfe926a00'Alyssa Ross2020-07-13
| | | | | | 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.
* overlays: don't apply to all nixpkgs treesAlyssa Ross2020-07-13
| | | | | | | | | | | | | | | | | | | | | 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.
* python3Packages.zope_i18nmessageid: fix testsJonathan Ringer2020-06-04
| | | | (cherry picked from commit 7a8434c710c2bf9310d9b21988bc4ee2ac683d04)
* python3Packages.zope-hookable: 4.2.0 -> 5.0.1Jonathan Ringer2020-06-04
| | | | (cherry picked from commit 0e13f49e7c55268fcdca81cec53d879150d39264)
* Merge commit '467ce5a9f45aaf96110b41eb863a56866e1c2c3c'Alyssa Ross2020-06-04
|
* python3.pkgs.hyperkitty: 1.3.2 -> 1.3.3Alyssa Ross2020-06-04
|
* python3.pkgs.postorius: 1.3.2 -> 1.3.3Alyssa Ross2020-06-04
|
* mailman: 3.3.0 -> 3.3.1Alyssa Ross2020-06-04
|
* python3.pkgs.django-mailman3: 1.3.2 -> 1.3.3Alyssa Ross2020-06-04
|
* python3.pkgs.mailmanclient: 3.3.0 -> 3.3.1Alyssa Ross2020-06-04
| | | | Also enable tests, which seem to work now.
* python3.pkgs.zope_interface: 4.7.1 -> 5.1.0Alyssa Ross2020-06-04
|
* python3.pkgs.importlib-resources: 1.0.2 -> 1.5.0Alyssa Ross2020-06-04
|
* python3.pkgs.importlib-metadata: 1.5.0 -> 1.6.0Alyssa Ross2020-06-04
|
* python3.pkgs.coverage: 4.5.4 -> 5.1Alyssa Ross2020-06-04
|
* python3Packages.bleach: 3.1.0 -> 3.1.5Frederik Rietdijk2020-06-04
| | | | (cherry picked from commit f2fd4a4129c37b6ea7eea461f909a05246c3a280)
* cargo-download: fix buildAlyssa Ross2020-06-01
| | | | url: 1.6.0 -> 1.7.2
* ffmpeg_4: 4.2.2 -> 4.2.3zowoq2020-05-23
|
* ffmpeg_2_8: 2.8.15 -> 2.8.16zowoq2020-05-23
|
* ffmpeg-full: 4.2.2 -> 4.2.3zowoq2020-05-23
|
* Merge commit 'b47873026c7e356a340d0e1de7789d4e8428ac66'Alyssa Ross2020-05-18
|
* Merge commit '683c68232e91f76386db979c461d8fbe2a018782'Alyssa Ross2020-05-12
|
* cgit: 1.2.1 -> 1.2.3Alyssa Ross2020-05-09
| | | | cgit now supports lzip and zstd compression.
* python3: expose packageOverrides in passthruAlyssa Ross2020-05-09
| | | | | | | | | | | | | | 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.
* python3.pkgs: apply packageOverrides recursivelyAlyssa Ross2020-05-09
| | | | | | | 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.
* gnupg: use libusb1 (#85374)Linus Heckemann2020-05-06
| | | | | | | | | | * gnupg: use libusb1 This fixes scdaemon's direct ccid support. * systemd: fix gnupg-minimal (cherry picked from commit 6673a4988e4a4ff25ca94a84d8e2acf92453dbf1)
* Merge commit '22a3bf9fb9edad917fb6cd1066d58b5e426ee975'Alyssa Ross2020-04-27
|
* wf-recorder: 0.2 -> 0.2.1Michael Weiss2020-04-15
| | | | (cherry picked from commit ca2a222747bd14d0f477b8eb231eda68355ca240)
* mblaze: install msuck and mblowAlyssa Ross2020-04-15
| | | | | | | | | | 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.
* mailman-web: use default Nixpkgs DjangoAlyssa Ross2020-04-10
| | | | | | | | | | 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
* firefox: 74.0 -> 74.0.1Andreas Rammhold2020-04-06
| | | | (cherry picked from commit 48e6a3f1f16f29a30e34331a101ea40b535a784f)
* Merge commit 'ae6bdcc53584aaf20211ce1814bea97ece08a248'Alyssa Ross2020-04-06
| | | | | | # Conflicts: # nixpkgs/pkgs/build-support/rust/default.nix # nixpkgs/pkgs/development/go-modules/generic/default.nix
* Merge commit 'a2e06fc3423c4be53181b15c28dfbe0bcf67dd73'Alyssa Ross2020-04-01
|
* gnustep/base: replace libbfd with binutils-unwrappedajs1242020-02-28
| | | | | | Fixes #76927 (second try) (cherry picked from commit 664c02c89bdafd21e9d0cf4d16baceeb70003185)
* rust: include the rustc-dev componentSymphorien Gibol2020-01-27
| | | | | | | | This enables to compile rls and rustc See also https://github.com/rust-lang/rust/pull/64823 (cherry picked from commit 47681d7c5c9529615e9f481f02d945a2c3cfe599)
* Merge commit '3d085a399c436a41d875801619e8f976b8519196'Alyssa Ross2020-01-26
|
* Merge commit '90441b4b47fc7280de6a5bd1a228017caaa0f97f'Alyssa Ross2020-01-22
|
* python3.pkgs.postorius: 1.3.1 -> 1.3.2Alyssa Ross2020-01-17
|
* python3.pkgs.postorius: use checkInputsAlyssa Ross2020-01-17
|
* python3.pkgs.hyperkitty: use checkInputsAlyssa Ross2020-01-17
| | | | | | The previously propagated build inputs are optional, and so are included in checkInputs so the tests can run, but not propagated so they aren't included if unneeded.
* python3.pkgs.hyperkitty: 1.3.0 -> 1.3.2Alyssa Ross2020-01-17
|
* python3.pkgs.mailman-web: add missing whoosh depAlyssa Ross2020-01-17
| | | | | This is propagated by Hyperkitty, but it should really only be a checkInput there.
* Merge commit '100012e55bc2a82fc680cba31a426ad38ead6fab'Alyssa Ross2020-01-14
|
* mailman: don't try to create /etc/mailman.cfgAlyssa Ross2020-01-14
|
* Revert "Re-revert "awscli: Get rid of runtime -dev dependencies""Alyssa Ross2020-01-14
| | | | | | | | | | This reverts commit a1eacb900e1b705678b2c199cb97baafc9b77f86. Adding dev outputs to python packages means they can't be included in a Python environment created with python3.withPackages, because makePythonPath will include the dev output, which is empty apart from nix-support, rather than the out output, which contains all the Python code.
* hyperkitty: fix buildAlyssa Ross2020-01-14
|
* python3.pkgs.publicsuffix: fix buildAlyssa Ross2020-01-13
| | | | | | This patch has not been necessary since 5425867bfa3e4ba83a3d67aa50b811b5f70d6fe5, and has in fact broken the build since then.
* mailman-postorius: update from version 1.2.4 to 1.3.1Peter Simons2020-01-13
|
* mailman: update from version 3.2.2 to 3.3.0Peter Simons2020-01-13
|
* python-authheaders: initial version 0.12.1Peter Simons2020-01-13
| | | | This package is a dependency of GNU Mailman 3.3.x.
* public-inbox: fix buildAlyssa Ross2020-01-12
| | | | | | This fixes some two-digit year rounding bugs that started triggering because 2020 is closer to 2070 than 1970. Apparently two digits years are still a thing.
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-06-29 05:45:54 +0000