b73e9758ba
phpPackages.php-codesniffer: 3.12.0 -> 3.12.2 ( #398308 )
2025-04-13 11:18:32 +02:00
c86bc1d321
phpPackages.php-codesniffer: 3.12.0 -> 3.12.2
2025-04-13 09:07:35 +00:00
f9445fde9f
firewalld: fix gui icons ( #398283 )
2025-04-13 17:05:44 +08:00
f47a69d878
github-markdown-toc-go: 1.4.0 -> 2.0.0 ( #398291 )
...
Co-authored-by: DanNixon <dan@dan-nixon.com >
2025-04-13 08:35:50 +00:00
7236f9c721
cuda_gdb: remove python39 related files ( #398268 )
2025-04-13 10:32:08 +02:00
9e9def6457
kine: 0.13.11 -> 0.13.13 ( #398280 )
...
Co-authored-by: techknowlogick <hello@techknowlogick.com >
2025-04-13 08:31:10 +00:00
f1fcf6b13a
tana: 1.0.25 -> 1.0.26 ( #398152 )
...
Co-authored-by: massix <massimo.gengarelli@proton.me >
2025-04-13 07:25:03 +00:00
4072420b03
github-markdown-toc-go: 1.4.0 -> 2.0.0
2025-04-13 07:06:06 +00:00
10189aca67
xdg-desktop-portal-cosmic: substitute fallback background path
...
The directory `/usr/share/backgrounds/pop/` is not accessible on NixOS
because the directory `/usr` does not exist on NixOS. The package
`cosmic-wallpapers` exists in nixpkgs that provides the background image
that is used in the COSMIC DE's screenshots on the first-party
website[0]. Substitute the unreachable, FHS path with a valid path of
the background image from the Nix store.
Note: We are putting in a different fallback background path alltogether
but I believe that this is okay because that is used by upstream in
their marketing materials. Meaning, after substitution, we match
marketing screenshots from upstream.
[0]: https://system76.com/cosmic/
2025-04-13 07:46:39 +02:00
4faf539901
firewalld: fix gui icons
2025-04-13 13:05:47 +08:00
5de66298aa
sourcepawn-studio: init at 8.1.2 ( #395652 )
2025-04-12 21:45:24 -07:00
71eaa3e8ab
tests.importCargoLock: various fixes ( #397281 )
2025-04-13 00:29:58 -04:00
c010a1bf84
yaziPlugins.ouch: 0-unstable-2025-04-09 -> 0-unstable-2025-04-12 ( #398276 )
2025-04-12 21:27:58 -07:00
95f56147d8
kine: 0.13.11 -> 0.13.13
2025-04-13 04:25:25 +00:00
c91fffabc2
yaziPlugins.ouch: 0-unstable-2025-04-09 -> 0-unstable-2025-04-12
2025-04-12 23:15:04 -05:00
ae29fc75d2
yaziPlugins.yatline-catppuccin: init at 0-unstable-2025-03-05 ( #398266 )
2025-04-12 20:19:29 -07:00
5d4016b502
cosmic-ext-ctl: 1.1.0 -> 1.4.0 ( #398143 )
2025-04-12 20:06:07 -07:00
1b0f4030f2
yaziPlugins: cleanup descriptions
2025-04-12 22:04:42 -05:00
67afa4df86
yaziPlugins.yatline-catppuccin: init at 0-unstable-2025-03-05
2025-04-12 22:01:44 -05:00
bc27118dc7
cuda_gdb: remove python39 related files
2025-04-13 10:57:37 +08:00
e528b296de
python313Packages.home-assistant-chip-wheels: 2024.11.4 -> 2025.4.0 ( #397441 )
2025-04-12 19:43:43 -07:00
793eef6168
vocal: drop ( #398146 )
2025-04-13 09:48:54 +08:00
827f89447c
letsdns: init at 1.2.1 ( #396558 )
2025-04-12 21:30:13 -04:00
e02c44f9ef
hyprlang: 0.6.0 -> 0.6.1 ( #398250 )
2025-04-13 01:27:16 +00:00
07a930402a
hyprlang: 0.6.0 -> 0.6.1
2025-04-13 00:38:45 +00:00
f6db44a8da
outline: 0.82.0 -> 0.83.0
2025-04-13 03:59:46 +04:00
208645bf60
python39: drop ( #397258 )
2025-04-13 01:46:51 +02:00
43aad2d145
exabgp: add mainProgram ( #398003 )
2025-04-13 01:44:41 +02:00
cd13eb58ac
magic-vlsi: 8.3.524 -> 8.3.526
2025-04-12 18:38:39 -05:00
accf4b8745
dxvk_2: 2.6 -> 2.6.1 ( #397499 )
...
Co-authored-by: reckenrode <randy@largeandhighquality.com >
2025-04-12 23:29:36 +00:00
f362195287
nixos/doc: update python39Packages reference
...
The packages set is now gone and pytorch has been renamed to just torch.
2025-04-13 01:26:42 +02:00
8e93fb0f32
python39: drop before the 25.05 branch-off
...
End of security support is scheduled for 2025-10-31, which does not cover
the complete 25.05 release cycle.
2025-04-13 01:26:42 +02:00
1076d576f5
crossfire-server: unpin python39 and mark broken
2025-04-13 01:26:41 +02:00
46a6dcc365
cjdns: unpin python39 and mark broken
2025-04-13 01:26:41 +02:00
24a979ee8c
cuda-modules: drop python39 support
2025-04-13 01:26:41 +02:00
2d71c5f5dd
flutter: unpin python3.9
...
No version we have in nixpkgs is older than 3.20.
2025-04-13 01:26:40 +02:00
713e715fb5
easyabc: 1.3.8.6 -> 1.3.8.7-unstable-2025-01-12
2025-04-13 01:26:33 +02:00
c8cfe3d57b
python312Packages.cx-freeze: fix build-system substition
2025-04-13 01:26:33 +02:00
5a98c14dc3
aldente: 1.31.3 -> 1.32 ( #398177 )
2025-04-12 18:57:00 -04:00
11286c28a8
nixos/forgejo: leverage systemd-notify support ( #398210 )
2025-04-12 18:28:30 -04:00
78863b295a
gcc-arm-embedded-{6,7,8,9,10,11,12}: drop ( #398204 )
2025-04-12 22:58:38 +02:00
8942550656
python313Packages.ufomerge: 1.8.2 -> 1.8.3 ( #397953 )
2025-04-12 22:48:57 +02:00
5eefeb3fe0
nixos/forgejo: leverage systemd-notify support
...
This feature goes all the way back to v1.20.0 (mid 2023) back when
Forgejo was still a soft-fork and simply used the nixos/gitea module.
The tl;dr:
nixos/gitea enabled it as part of the Gitea 1.20 bump PR, while Forgejo
was still at 1.19.4 and did not support this yet, causing Forgejo to
get restarted after 90s by systemd in a loop. This, among other things,
was part of the reason why Forgejo forked the nixos/gitea module into
nixos/forgejo and it since moving independently in nixpkgs.
systemd-notify provides more accurate service unit states over the
previous service type "simple".
Ref: b61919e5e044aee34594
2025-04-12 22:40:25 +02:00
0c6cf1f8d7
python312Packages.unstructured-client: 0.32.0 -> 0.32.3 ( #398183 )
2025-04-12 13:28:28 -07:00
98951d66f2
python3Packages.pypdfium2: fix cross, reduce closure size ( #396787 )
2025-04-12 20:17:45 +00:00
4aa89d19f4
gcc-arm-embedded-{6,7,8,9,10,11,12}: drop
2025-04-12 22:09:30 +02:00
e7e6e9db85
hubble: fix cross build, re-enable tests, misc. cleanup ( #396796 )
2025-04-12 20:05:56 +00:00
449b9d0e64
qdl: fix cross build, misc. cleanup ( #396777 )
2025-04-12 19:59:54 +00:00
5464c34f4d
python312Packages.sparse: 0.15.5 -> 0.16.0 ( #397670 )
2025-04-12 21:57:18 +02:00
c154df9f54
zitadel: 2.71.1 -> 2.71.7 ( #394317 )
2025-04-12 21:54:14 +02:00
Pol Dellaiera