The nixpkgs-unstable channel's programs.sqlite was used to identify
packages producing exactly one binary, and these automatically added
to their package definitions wherever possible.
It's time again, I guess :>
Main motivation is to stop being pinged about software that I maintained
for work now that I'm about to switch jobs. There's no point in pinging
me to review/test updates or to debug issues in e.g. the Atlassian stack
or on mailman since I use neither personally.
But there's also a bunch of other stuff that I stopped using personally. While
at it I realized that I'm still maintainer of a few tests & modules related to
packages I stopped maintaining in the past already.
checkInputs used to be added to nativeBuildInputs. Now we have
nativeCheckInputs to do that instead. Doing this treewide change allows
to keep hashes identical to before the introduction of
nativeCheckInputs.
SQLAlchemy-Utils v0.36.6 package override build is failing.
This is due to a patch in the original SQLAlchemy-Utils package which
broke the build of this package override:
```bash
> applying patch /nix/store/pd6anhwbf0in3r3jhi3sbn5v2fjs0mf2-skip-database-tests.patch
> patching file conftest.py
> Hunk #1 FAILED at 61.
> Hunk #2 succeeded at 98 (offset -10 lines).
```
These SQLAlchemy package overrides were originaly added to fix
incompatibilities with Flask-Admin.
See commit 05ae01fcea
However with Flask-Admin >= v1.5.6, several SQLAlchemy compatibility patches were added:
* https://flask-admin.readthedocs.io/en/latest/changelog/
We can now safely remove these package overrides to make bukuserver work again.
Failing Hydra build: https://hydra.nixos.org/build/148285785
The underlying issue is `flask-admin` not working with newer versions of
`SQLAlchemy` and `SQLAlchemy-Utils`[1].
I decided to only fix `buku` now since this is the package I wanted to
take care of initially. Also, multiple versions of python packages - a
measure that would be necessary for `flask-admin` - are generally
discouraged[2].
[1] 1.5.8 works with `SQLAlchemy`, but is broken with `SQLAlchemy-Utils`
at 0.37, see also https://github.com/flask-admin/flask-admin/issues/2113
[2] https://github.com/NixOS/nixpkgs/pull/127707
I'm baaaaack!
This patch reverts my patch where I removed myself as maintainer because
of my traveling. I'm back now and I want to maintain these packages
again.
This reverts commit ce1c1e3093.
With this patch I remove myself as a maintainer for all packages I
currently maintain.
This is due the fact that I will be basically off the grid from May 2018
until early 2019, as I will be on a trip through north america.
I will revert this patch as soon as I'm back, as I plan to continue
contributing to nixpkgs then.
But as I cannot maintain anything during that time, I'd like to get this
patch merged.
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/buku/versions.
These checks were done:
- built on NixOS
- ran `/nix/store/xhqxppgivy66mf4v46acf4p9qzqrnfhs-buku-3.7/bin/.buku-wrapped -h` got 0 exit code
- ran `/nix/store/xhqxppgivy66mf4v46acf4p9qzqrnfhs-buku-3.7/bin/.buku-wrapped --help` got 0 exit code
- ran `/nix/store/xhqxppgivy66mf4v46acf4p9qzqrnfhs-buku-3.7/bin/.buku-wrapped -h` and found version 3.7
- ran `/nix/store/xhqxppgivy66mf4v46acf4p9qzqrnfhs-buku-3.7/bin/.buku-wrapped --help` and found version 3.7
- ran `/nix/store/xhqxppgivy66mf4v46acf4p9qzqrnfhs-buku-3.7/bin/buku -h` got 0 exit code
- ran `/nix/store/xhqxppgivy66mf4v46acf4p9qzqrnfhs-buku-3.7/bin/buku --help` got 0 exit code
- ran `/nix/store/xhqxppgivy66mf4v46acf4p9qzqrnfhs-buku-3.7/bin/buku -h` and found version 3.7
- ran `/nix/store/xhqxppgivy66mf4v46acf4p9qzqrnfhs-buku-3.7/bin/buku --help` and found version 3.7
- found 3.7 with grep in /nix/store/xhqxppgivy66mf4v46acf4p9qzqrnfhs-buku-3.7
- directory tree listing: https://gist.github.com/231e0667743da0993083d1dd37c787b7
Some more tests were disabled as they require internet connection.
The tests were disabled by simply removing the "assertEqual" statements,
as this is the simplest way to do it.
