Bug #172
closedrobotpkg-dynamic-graph-bridge-v3 is stuck in v3.0.8 in apt repositories
Description
Hi,
As previously reported, we have an issue with wip/dynamic-graph-bridge-v3:
http://robotpkg.openrobots.org/rbulk/robotpkg-wip/wip/dynamic-graph-bridge-v3/ seems OK for v3.1.0, but I can only find v3.0.8 in the apt repositories of 14.04 & 16.04, and nothing in 18.04:
State: not a real package (virtual)
N: Can't select candidate version from package robotpkg-dynamic-graph-bridge-v3 as it has no candidate
N: Can't select versions from package 'robotpkg-dynamic-graph-bridge-v3' as it is purely virtual
N: No packages found
As this package is the last requirement for the ones we are currently heavily working on right now (roscontrol_sot & sot-talos), we would like to understand what is happening.
Thanks !
Updated by Guilhem Saurel over 5 years ago
I forgot to mention that I just released the version 3.1.0 yesterday, and updated some dependencies too, to see if this change something, but the issue is still here
Updated by Anthony Mallet over 5 years ago
On ubuntu 16.04 and 18.04, it says:
===> Building binary package for dynamic-graph-bridge-v3-3.1.0
robotpkg_create: can't stat
`/opt/openrobots/lib/libros_interpreter.so' robotpkg_create: lstat
failed for file lib/libros_interpreter.so: No such file or directory
Creating package
/opt/robotpkg/var/lib/robotpkg/wip/packages/bsd/Ubuntu-16.04-x86_64/All/dynamic-graph-bridge-v3-3.1.0
make3: *** [pkg-tarup] Error 2
On 14.04 it has more issues like this.
This prevents from creating the binary packages.
Updated by Guilhem Saurel over 5 years ago
- Status changed from New to Resolved
Ok, thanks.
It seems that for now, I should not have splitted this package in 2.
this has been fixed in
https://git.openrobots.org/projects/robotpkg-wip/repository/revisions/e97f595da510a6dd64bc84afe77d7328a54eba5f
and should work after
https://git.openrobots.org/issues/173
Updated by Anthony Mallet over 5 years ago
- Status changed from Resolved to Closed
Updated by Anthony Mallet over 5 years ago
There was also an issue in pkgrepo2deb 1.3. See commit pkgrepo2deb:bc28507c.
This is fixed in pkgrepo2deb 1.4.