Commit 0b76c99
committed
fix: sign top-level Release files instead of non-existent component files
The signing function was looking for component-level Release files
(dists/{release}/{component}/Release) which aptly doesn't create.
Aptly only creates:
- Top-level: dists/{release}/Release
- Binary subdir: dists/{release}/{component}/binary-{arch}/Release
Changed the signing function to:
- Use find -maxdepth 2 to limit search depth
- Sign files with slash_count=1 (top-level Release files)
- This creates InRelease and Release.gpg for each distribution
Verified:
- All 4 distributions (bookworm, jammy, noble, trixie) now have signed Release files
- gpg --verify confirms signatures are valid
- Both InRelease (clearsigned) and Release.gpg (detached) created
Signed-off-by: Igor Pecovnik <igor@armbian.com>1 parent d339800 commit 0b76c99
1 file changed
+8
-14
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
666 | 666 | | |
667 | 667 | | |
668 | 668 | | |
669 | | - | |
670 | | - | |
671 | | - | |
672 | | - | |
673 | | - | |
674 | | - | |
675 | | - | |
676 | | - | |
677 | | - | |
678 | | - | |
679 | | - | |
680 | | - | |
| 669 | + | |
| 670 | + | |
| 671 | + | |
| 672 | + | |
| 673 | + | |
| 674 | + | |
681 | 675 | | |
682 | | - | |
| 676 | + | |
683 | 677 | | |
684 | 678 | | |
685 | | - | |
| 679 | + | |
686 | 680 | | |
687 | 681 | | |
688 | 682 | | |
| |||
0 commit comments