Fimeg/souveraine
Watch
1
0
Fork
You've already forked souveraine
 0
Code Releases Activity

publish-edge: ship the bare .files names too

Browse source 
pacman -Fy asks for souveraine-<arch>.files, not .files.tar.zst, so it 404'd.
This commit is contained in:
Fimeg 2026-07-25 18:45:02 -04:00
commit 6eb87a542d
1 changed files with 14 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

16
packaging/arch/publish-edge.sh
View file

@ -309,11 +309,21 @@ for ARCH_DIR in "$REPO_DIR"/*/; do
fi
log "$ARCH: merged — $(wc -l < "$WORK/before.tsv") entries in, $(wc -l < "$WORK/after.tsv") out"
# repo-add leaves .db and .db.sig as symlinks; release assets cannot carry
# those, so publish real files.
# repo-add leaves .db/.files and their .sig as symlinks; release assets cannot
# carry those, so publish real files. pacman fetches the BARE names — `-Sy`
# asks for `$DB.db`, `-Fy` for `$DB.files` — so the .tar.zst copies alone are
# not enough. The files db was missing its bare name until 2026-07-25, which
# is why `pacman -Fy` 404'd on this repo while `-Sy` worked.
rm -f "$WORK/$DB.db" "$WORK/$DB.db.sig"
cp "$WORK/$DB.db.tar.zst" "$WORK/$DB.db"
cp "$WORK/$DB.db.tar.zst.sig" "$WORK/$DB.db.sig"
if [ -f "$WORK/$DB.files.tar.zst" ]; then
rm -f "$WORK/$DB.files" "$WORK/$DB.files.sig"
cp "$WORK/$DB.files.tar.zst" "$WORK/$DB.files"
if [ -f "$WORK/$DB.files.tar.zst.sig" ]; then
cp "$WORK/$DB.files.tar.zst.sig" "$WORK/$DB.files.sig"
fi
fi
# Producer-scoped checksums: a whole-archive manifest would go stale the
# moment another producer published, and claim coverage it does not have.
@ -330,8 +340,10 @@ for ARCH_DIR in "$REPO_DIR"/*/; do
upload_asset "$WORK/$PRODUCER-$ARCH.sha256"
if [ -f "$WORK/$DB.files.tar.zst" ]; then
upload_asset "$WORK/$DB.files.tar.zst"
upload_asset "$WORK/$DB.files"
if [ -f "$WORK/$DB.files.tar.zst.sig" ]; then
upload_asset "$WORK/$DB.files.tar.zst.sig"
upload_asset "$WORK/$DB.files.sig"
fi
fi
upload_asset "$WORK/$DB.db.tar.zst"