Closed TarikViehmann closed 5 days ago
fixed the build issue due to missing svn dependency: https://github.com/carologistics/clips_vendor/pull/1
we encounter some issues related to svn during the build:
01:17:29 from pkg_resources import load_entry_point
01:17:29 === ./clips_vendor (svn) ===
01:17:29 Could not checkout repository 'https://svn.code.sf.net/p/clipsrules/code/branches/64x': svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
01:17:29 svn: E155004: Working copy '/tmp/ws/build_isolated/clips_vendor/clips_vendor-prefix/src/clips_vendor' locked.
01:17:29 svn: E155004: '/tmp/ws/build_isolated/clips_vendor/clips_vendor-prefix/src/clips_vendor' is already locked.
01:17:29 gmake[2]: *** [CMakeFiles/clips_vendor.dir/build.make:101: clips_vendor-prefix/src/clips_vendor-stamp/clips_vendor-download] Error 1
01:17:29 gmake[1]: *** [CMakeFiles/Makefile2:137: CMakeFiles/clips_vendor.dir/all] Error 2
01:17:29 gmake: *** [Makefile:146: all] Error 2
01:17:29 ---
But we are not sure what the issue is. We mainly use ament_cmake_vendor_package
and they more-or-less hand it through to cmakes externalProject_add
.
Could this be an issue with the build farm polling the svn working directory in multiple threads and locking it?
As it seems that barely any other packages even depends on svn I could offer to mirror the svn to git and use the git mirror for the vendor. Not sure if that is acceptable or not.
If this is the wrong place to discuss this, just let me know.
Edit: We actually just migrated to downloading the code via zip
This change has been deployed.
Name of the new release team: carologistics
Team members
Carologistics is a robotics team of students and reasearch assistants competing at RoboCup since 2012 as well as doing research in the field of robotics. With our migration to ROS 2 we would like to make our contributions readily available to the ROS community. As a first project, we are preparing to release our CLIPS based reasoning framework suitable for knowledge-based applications. Tim and I have experience with general packaging in fedora and I maintain ROS binaries for Fedora for many years now (https://copr.fedorainfracloud.org/coprs/tavie/ros2).
To start, we want to get familiar with the ROS workflows by releasing the clips_vendor (the knowledge engine we use to build the framework) for humble, jazzy and rolling.