For the rainbow specific packages we have specific needs regarding
repository access, but potentially also regarding package outside
of our control, like:
| Setting up cloud-wrg (1.166.0~202206270731.84f00df-972+deb11) ...
| /var/lib/dpkg/info/cloud-wrg.postinst: 5: systemctl: not found
| dpkg: error processing package cloud-wrg (--configure):
| installed cloud-wrg package post-installation script subprocess returned error exit status 127
| [...]
| Setting up mongodb-org-server (3.6.23) ...
| [...]
| Done.
| /var/lib/dpkg/info/mongodb-org-server.postinst: 43: systemctl: not found
Handle this by detecting the project "rainbow-misc" and then set up a custom
cowbuilder based environment for piuparts usage:
1) Retrieve latest ngcp-rainbow-keyrings-pro package from
release-trunk-$distribution for repository keys
2) Set up /etc/apt/sources.list.d/rainbow.list and
/etc/apt/preferences as needed
3) Deploy further workarounds like the one for systemctl mentioned above
Change-Id: I8253aaa645c3b69d784f29a3b050267c3a8a03dc
echo "Error: ngcp-rainbow-keyrings-pro version for release-trunk-${distribution} could not be detected." >&2
exit 1
fi
local deb_package="ngcp-rainbow-keyrings-pro_${version}_all.deb"
if ! sudo wget --timeout=30 -O "${PIUPARTS_BASEDIR}"/root/"${deb_package}" "https://deb.sipwise.com/autobuild/pool/main/n/ngcp-rainbow-misc/${deb_package}" ; then
echo "Error: failed to download ngcp-rainbow-keyrings-pro Debian package" >&2