nathan/nixpkgs
1
0
Fork 0
mirror of https://github.com/NixOS/nixpkgs.git synced 2026-10-02 04:50:21 +00:00
Code Issues Packages Projects Releases Wiki Activity
1,058,993 Commits 261 Branches 81 Tags
python-updates
Commit Graph

18 Commits

Author SHA1 Message Date
Grimmauld
af253c905a libapparmor: 5.0.1 -> 5.0.2 2026-07-14 20:09:03 +02:00
Grimmauld
eb8d97ca2d libapparmor: 5.0.0 -> 5.0.1 2026-07-07 21:44:48 +02:00
R. Ryantm
06b17cff7d libapparmor: 4.1.7 -> 5.0.0 2026-05-01 15:40:47 +00:00
R. Ryantm
5013c241b0 libapparmor: 4.1.3 -> 4.1.7 2026-03-11 20:42:15 +00:00
R. Ryantm
929d40a173 python3Packages.libapparmor: 4.1.2 -> 4.1.3 2026-01-10 01:11:23 +00:00
R. Ryantm
9c4bd4b424 libapparmor: 4.1.1 -> 4.1.2 2025-09-12 21:23:54 +00:00
Wolfgang Walther
5a0711127c treewide: run nixfmt 1.0.0 2025-07-24 13:55:40 +02:00
Grimmauld
05fb388ea7 libapparmor: 4.1.0 -> 4.1.1 
Release Notes: https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_4.1.1
Diff: https://gitlab.com/apparmor/apparmor/-/commits/v4.1.1

Contains partial fixes for musl, some improvements to test coverage,
and a couple minor fixes to oversights in the 4.1.0 release.
 2025-06-10 20:10:05 +02:00
Grimmauld
6c085c8ead libapparmor: avoid generating __pycache__ in tests 
Upstream PR: https://gitlab.com/apparmor/apparmor/-/merge_requests/1697
Closes https://github.com/NixOS/nixpkgs/issues/409032

The upstream Make procedure spawns apparmor tests in a stripped environment.
This results in pycache files that contain the actual current timestamp.
Solution: Don't generate pyc files while running tests.
`setup.py` will already correctly generate the `__pycache__`,
respecting the reproducibility flags.
 2025-05-24 10:58:23 +02:00
nixpkgs-ci[bot]
72306e012b Merge master into staging-next 2025-05-10 18:04:20 +00:00
Grimmauld
ce8e2c978b apparmor: fix cross for different bit depths between build and host 
Fixes #405780

Void also does not attempt to enable python on cross for armv7 [1].
This means apparmor-parser will never work on cross.

[1] f8130e11ca/srcpkgs/apparmor/template (L32-L36)
 2025-05-10 19:41:44 +02:00
nixpkgs-ci[bot]
8dcc425d08 Merge staging-next into staging 2025-04-28 00:17:31 +00:00
Alyssa Ross
2e8d275c2f libapparmor: fix static 
The Python bindings were recently enabled when cross compiling, but it
still doesn't make sense to build them (a shared library) in
pkgsStatic.

Fixes: eba90bba66 ("apparmor: 4.0.3 -> 4.1.0, rewrite")
 2025-04-27 21:22:42 +02:00
FliegendeWurst
8326a9a0f5 libapparmor: fix cross properly 2025-04-26 16:59:11 +02:00
FliegendeWurst
7c607cf908 Revert "libapparmor: fix build if doCheck = false (e.g. on cross)" 
This reverts commit 61857a9832.
 2025-04-26 16:58:49 +02:00
Grimmauld
61857a9832 libapparmor: fix build if doCheck = false (e.g. on cross) 
This is a HACK. The correct fix is #401980,
but causes rebuilds and therefore is unsuitable for staging-next.
 2025-04-26 16:40:22 +02:00
Grimmauld
1d315c8bb1 libapparmor: transfer maintenance to team 2025-04-22 23:56:39 +02:00
Grimmauld
eba90bba66 apparmor: 4.0.3 -> 4.1.0, rewrite 
Upstream release: https://gitlab.com/apparmor/apparmor/-/releases/v4.1.0

Notable changes made to the packaging:
- apparmor-kernel-patches: drop. This was outdated and unused, and wouldn't even apply to any kernel anymore.
- aa-teardown: migrate to writeShellAPplication
- apparmor-*: migrate to by-name
- apparmor-*: enable checks and actually run checks
- libapparmor: test python module imports correctly
- libapparmor: no seperate $python output (makes no sense)
 2025-04-22 23:48:08 +02:00