This repository has been archived by the owner on Apr 12, 2021. It is now read-only.
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: NixOS/nixpkgs-channels
base: 873e114cf49c
Could not load branches
Nothing to show
Could not load tags
Nothing to show
{{ refName }}
default
...
head repository: NixOS/nixpkgs-channels
compare: 1ccc512b39a4
Could not load branches
Nothing to show
Could not load tags
Nothing to show
{{ refName }}
default
- 17 commits
- 14 files changed
- 9 contributors
Commits on May 12, 2020
Commits on May 16, 2020
Commits on May 17, 2020
-
-
-
vdirsyncer: Convert to a python module (#87865)
* vdirsyncer: standardize derivation Use toPythonApplication and use callPackage from python-packages.nix. Make vdirsyncerStable somewhat functional again, but mark it as broken for Python 3.6 or higher. * vdirsyncer: use buildPythonPackage as it's a package now * vdirsyncer: move to python-modules/ * vdirsyncer: Move disabled logic into expression
-
redis: handle changes to systemd support
The 6.0 changelog notes that systemd support was rewritten. The effects of that seem to be twofold: * Redis will silently fail to sd_notify if not built with libsystemd, breaking our unit configuration. * It also appears to misbehave if told to daemonize when running under systemd -- note that upstream's sample unit configuration does not daemonize: https://github.com/antirez/redis/blob/unstable/utils/systemd-redis_server.service
-
Merge pull request #87960 from eonpatapon/cue-0.1.2
cue: 0.1.1 -> 0.1.2
-
Merge pull request #88009 from JJJollyjim/redis-systemd-fixes
redis: handle changes to systemd support
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 873e114cf49c...1ccc512b39a4