commits
thelounge: fix sqlite logging
python310Packages.bitarray: 2.7.3 -> 2.7.4
python310Packages.rns: 0.5.3 -> 0.5.4
kubedog: 0.9.11 -> 0.9.12
gh-markdown-preview: 1.4.0 -> 1.4.1
qovery-cli: 0.58.15 -> 0.59.0
lima: 0.15.1 -> 0.16.0
delta: 0.16.4 -> 0.16.5, add figsoda as a maintainer
Changelog: https://github.com/ilanschnell/bitarray/raw/2.7.4/CHANGE_LOG
Diff: https://github.com/markqvist/Reticulum/compare/refs/tags/0.5.3...0.5.4
Changelog: https://github.com/markqvist/Reticulum/releases/tag/0.5.4
ddosify: 1.0.1 -> 1.0.3
Diff: https://github.com/Qovery/qovery-cli/compare/v0.58.15...v0.59.0
Changelog: https://github.com/Qovery/qovery-cli/releases/tag/v0.59.0
exodus: 23.5.8 -> 23.5.22
python311Packages.aiopvpc: 4.1.0 -> 4.2.1
python311Packages.aiokafka: 0.8.0 -> 0.8.1
python311Packages.aio-pika: 9.0.7 -> 9.1.2
Previously, we never actually built the SQLite binding, causing The Lounge
to bail when attempting to load SQLite logs [0]. It wasn't caught before
because it wasn't thrown fatally, for whatever reason. Perhaps we should
fix this in the future with a patch and/or more robust tests, but for now,
let's just fix the issue.
[0]: https://github.com/NixOS/nixpkgs/pull/233511#issuecomment-1567182450
jackett: 0.21.88 -> 0.21.114
ferdium: 6.2.6 -> 6.3.0
terragrunt: 0.45.16 -> 0.45.18
https://salsa.debian.org/reproducible-builds/strip-nondeterminism/-/blob/master/lib/File/StripNondeterminism/handlers/zip.pm#L29
it was working on linux because the tests are run on linux
Bump Ferdium version from 6.2.6 -> 6.3.0 (skipping 6.2.7)
Changelog (6.3.0): https://github.com/ferdium/ferdium-app/releases/tag/v6.3.0
Changelog (6.2.7): https://github.com/ferdium/ferdium-app/releases/tag/v6.2.7
reproxy: 0.11.0 -> 1.0.0
breitbandmessung: 3.1.0 -> 3.3.0; use electron_24
python311Packages.python-benedict: 0.30.1 -> 0.30.2
spotify-player: 0.13.1 -> 0.14.1
talosctl: 1.4.4 -> 1.4.5
grpc-gateway: 2.15.2 -> 2.16.0
switcheroo-control: 2.3 -> 2.6
vimPlugins.vim-just: init at 2023-04-21
Fixes a bug where pre-commit would pollute the PYTHONPATH with its
dependencies, potentially interfering with the user's dependencies.
Since python documentation requires Sphinx to build, documentation is built in
separate derivation to avoid hard recursion/bootstrapping questions and plugged
into main derivation. Care is taken that "python3.doc" derivation feels and
looks as close as possible to as if it were main derivation were multi-output
one.
This change does not cause rebuild of python3 itself.
Diff: https://github.com/azogue/aiopvpc/compare/refs/tags/v4.1.0...v4.2.1
Changelog: https://github.com/azogue/aiopvpc/blob/v4.2.1/CHANGELOG.md
Diff: https://github.com/aio-libs/aiokafka/compare/refs/tags/v0.8.0...v0.8.1
Changelog: https://github.com/aio-libs/aiokafka/releases/tag/v0.8.1
Diff: https://github.com/mosquito/aio-pika/compare/refs/tags/9.0.7...9.1.2
Changelog: https://github.com/mosquito/aio-pika/blob/9.1.2/CHANGELOG.md
Previously, we never actually built the SQLite binding, causing The Lounge
to bail when attempting to load SQLite logs [0]. It wasn't caught before
because it wasn't thrown fatally, for whatever reason. Perhaps we should
fix this in the future with a patch and/or more robust tests, but for now,
let's just fix the issue.
[0]: https://github.com/NixOS/nixpkgs/pull/233511#issuecomment-1567182450
Since python documentation requires Sphinx to build, documentation is built in
separate derivation to avoid hard recursion/bootstrapping questions and plugged
into main derivation. Care is taken that "python3.doc" derivation feels and
looks as close as possible to as if it were main derivation were multi-output
one.
This change does not cause rebuild of python3 itself.