Publish .orig-$component.tar.*.asc files as well
Merged
requested to merge wip/em/fix-multiple-signed-orig-tarballs-publishing into collabora/staging
- Jun 12, 2023
-
-
Verify that packages with multiple tarballs are handled correctly: their component tarballs should be published, as well as their signatures. For this, artificially extend the dash package with an empty component tarball called "vendor", with fake unverifiable signature files only containing the word "signature". Instead of editing the .dsc file to include those, unpack the source package and generate it again, allowing dpkg-buildpackage to pick up the new component tarball. Signed-off-by:
Andrej Shadura <andrew.shadura@collabora.co.uk> -
Signed-off-by:Andrej Shadura <andrew.shadura@collabora.co.uk>bdb0f649 -
Emanuele Aina authoredThe `freetype` Debian package uses multi-component orig tarballs, and also includes PGP signatures for them: freetype_2.10.4+dfsg-1+deb11u1+apertis0.debian.tar.xz freetype_2.10.4+dfsg-1+deb11u1+apertis0.dsc freetype_2.10.4+dfsg.orig-ft2demos.tar.xz freetype_2.10.4+dfsg.orig-ft2demos.tar.xz.asc freetype_2.10.4+dfsg.orig-ft2docs.tar.xz freetype_2.10.4+dfsg.orig-ft2docs.tar.xz.asc freetype_2.10.4+dfsg.orig.tar.xz However, at publishing time OBS was ignoring these `.orig-$component.tar.*.asc` files, causing the archive manager (reprepro or aptly) to fail since it was not getting some of the files listed in the `.dsc`. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>78a0ca29
-
