robotpkg

because of an issue with zst packaging:

dpkg-deb: error: archive '/opt/robotpkg/var/lib/robotpkg/packages/debian/pub/dists/impish/robotpkg/binary-amd64/robotpkg-pinocchio_2.6.4_amd64.deb' uses unknown compression for member 'control.tar.zst', giving up

http://robotpkg.openrobots.org/rbulk/robotpkg/math/pinocchio/pinocchio-2.6.9/Debian-9-x86_64/pkg.html

But maybe we can remove Debian 9 ?

(I keep pressing ctrl+enter instead of enter, sorry for the multiple messages)

Debian 9 support is over since July 2020, and its LTS ended in June 2022

This is an indirect consequence of the real error:

===> Building binary package for pinocchio-2.6.9
robotpkg_create: can't stat `/opt/openrobots/lib/cmake/pinocchio/cxx-standard.cmake'
robotpkg_create: lstat failed for file
lib/cmake/pinocchio/cxx-standard.cmake: No such file or directory

I'm not sure why this happens on Debian-9 though.

The error you see is a consequence: when the packaging fails, the
strategy is to remove the corresponding .deb package. However, since
there is no robotpkg package (it failed to build), the `pkgrepo2deb`
cannot compute the repository path of the .deb file (because
'codename' cannot be computed from OS_VERSION in the robotpkg binary
package that does not exist). So the strategy is to remove all .deb
files with the right package name in all existing repositories (thus
for all Debian versions) that do not have an existing "source" in the
control file (the "source" is set by pkgrepo2deb to point to the
robotpkg binary package). So this will normally remove the only
package that just failed ...

So far so good, but it seems that yes, dpkg-deb on Debian-9 cannot
parse newer .deb format. pkgrepo2deb just prints the error and then
continues with other entries, so this is not what makes the whole
process fail (it would normaly just flag the package with "warnings"
if there were not the first error above).

Apart from that long story ... I agree that Debian-9 is EOL and it can
be removed soon :)