robotpkg

On Tuesday 5 Oct 2021, at 15:53, Guilhem Saurel wrote:

Ubuntu 20.04 provides gazebo 9 and 11.

Maybe initially there was only gazebo 9, that's why this is what is
installed. Otherwise I prefer to have the most recent for bulk builds.

I think replacing gazebo9 by gazebo11 on hydra64-ubuntu2004 would
workaround this issue.

Yes, done.

There are obscure issues on Ubuntu-21.04 with gazebo-11, but let's see
what happens. On my workstation I'm using gazebo-11 and ubuntu-20.04
just fine.

I also triggered a new bulk build.
Normally, all packages depending on gazebo should increase PKGREVISION
to catch the dependency update properly. We will probably not bother
with that, but packages should be rebuilt (because there is a
minimalistic dependency tracking through SYSTEM_SEARCH). So apt update
may get a bit confused. Or maybe not :)

I was wrong: the SYSTEM_SEARCH files are not used to check if a binary
package needs rebuilding. SYSTEM_SEARCH is currently used only to
generate the system dependencies for the .deb packages.

I could easily fix that, but at the moment, the result is that
packages that depend on gazebo have not necessarily been rebuilt yet
(only as a side effect of the recent hpp update, for that matters).

Do you think it is a good idea to check for the timestamp of files in
SYSTEM_SEARCH and trigger a rebuild if anything is newer than the
binary package? (a consequence would be that more package would
potentially change without a change in the version/revision number).

I don't think this would be worth it. A PKGREVISION bump will solve all issues that could arise from such situations. And I expect such situations to occur at very low frequency.

OK, that's right.

In practice, this happens each time system packages are updated
upstream. It can be worth checking that the builds are still OK with
the update. However, binary packages would require the most recent
system dependencies, which is not good.