Re: PCL 1.1.0

into the Debian package (and upstream as well). 2ct Cheers, Jochen [1] https://launchpad.net/~v-launchpad-jochen-sprickerhof-de/+archive/pcl [2] http://bugs.debian.org/628445 [3] http://bugs.debian.org/607160 -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject

Re: examples of gtest done right in Debian

Hi Anton and Jose, * Anton Gladky gl...@debian.org [2015-08-05 11:15]: gazebo was fixed recently to use a system-installed gtest [1]. [1] http://anonscm.debian.org/cgit/debian-science/packages/gazebo.git/tree/debian/patches/0002_use_system_gtest.patch We have a FindGtest.cmake module in

Re: Looking for sponsor for ROS packages (robotic framework)

* Wookey [2015-10-09 20:13]: > So it is - I have a terrible memory - serves me right for not > checking. I meant things like python-rosdep > python-rosinstall-generator python-wstool which > http://wiki.ros.org/hydro/Installation/Debian told me that I needed. I > see that

Re: flann package

Hi Anton and Leo, I uploaded the package to experimental. Cheers Jochen * Leopold Palomo-Avellaneda [2016-08-06 00:23]: > El Divendres, 15 de juliol de 2016, a les 12:27:22, Anton Gladky va escriure: > > Hi Leo, > > > > 2016-07-15 8:55 GMT+02:00 Leopold Palomo-Avellaneda

Re: ROS environment setup

Hi Dino, great to get some feedback on the packages. Feel free to mail, when you find a problem. * Dino H. [2017-01-28 11:05]: > I installed ROS from the official Stretch sources. However, I'm not able to > use it since the environment is not set up correctly. For example, if I

Re: Please categorise your packages for the Debian Science metapackages (second iteration)

Hi Andreas, thank you for your continuous effort! I see ros-opencv-apps in the list, which is not in testing (and will not make it, due to the freeze). So I assume it shouldn't be categorised as well. Regarding ros-ros, I think it would make sense to blacklist it, as it is only the base of a

Re: Please categorise your packages for the Debian Science metapackages (second iteration)

* Andreas Tille [2017-02-09 16:29]: > Please categorise *any* of your packages - be it in testing or not. The > metapackage creation process will verify whether a package is in testing > and add Recommends *only* if a package is in testing. If not the > package gets a Suggests

BinNMUs of header only libraries (eigen3, flann, pcl)

Hi Anton, Leo, I just stumbled over the problem that we have no transition tracking for header only libraries. If you grep for reverse build depends [1], you get quite a number of packages with outdated builds. I've found [2,3] mentioning Built-Using tags, but I guess for now doing a binNMU is

Re: Please add ros packages to robotics tasks

hat? Cheers Jochen From 3a1a3413d4c460becb8a3c479f04da3890afc983 Mon Sep 17 00:00:00 2001 From: Jochen Sprickerhof <g...@jochen.sprickerhof.de> Date: Sun, 1 Jan 2017 23:51:01 +0100 Subject: [PATCH] Remove old ROS dependencies --- tasks/robotics | 2 -- 1 file changed, 2 deletions(-) diff --git a/t

Re: Please add ros packages to robotics tasks

Hi Andreas, thanks for asking how to integrate ROS into the science meta package. As ROS is so big, we already created a special ros-metapackages package, resembling to what upstream has as well. The top meta package, currently packaged, would probably be ros-desktop-full and for development

Re: ROS installation with pure Debian Packages + some Source Packages

Hi Jörg, * Jörg [2018-06-18 21:59]: I've done the update on my machine and it builds. The problem is then the change of the library version, isn't it? All dependent packages need to be re-builded. See [1] for the exact packages i had to rebuilt. It all starts with pluginlib and classloader.

Re: ROS installation with pure Debian Packages + some Source Packages

* Jörg [2018-06-15 20:46]: $ catkin_make => error with gennodejs (import gennodejs fails) * source ./devel/setup.bash fixed it I usually ignore geneus and gennodejs, as I don't need it. => compile error: srdfdom needs a newer version * debian package libconsole-bridge0.4 has different

Re: ROS installation with pure Debian Packages + some Source Packages

Hi Jörg, do you need more information or help with ROS? Would be really great to see more users of these packages. Cheers Jochen * Jochen Sprickerhof [2018-06-13 11:54]: Hi Jörg, thanks for looking into the packages. * Jörg [2018-06-13 10:41]: But for bigger packages this is to complex

Re: ROS: catkin and ROS_PACKAGE_PATH

* Jörg Kurlbaum [2018-07-17 21:12]: Regarding these bugs, i was wondering if they are real bugs or have something to do with the Debian version of ROS. They are completely unrelated. I'm certain theses packages compiled flawlessly before all the update mess. The only thing I can imagine

Re: ROS: catkin and ROS_PACKAGE_PATH

Hi Jörg, * Jörg [2018-07-13 00:26]: Okay, i would like to help and actually find the reason why it doesn't work, but until now i haven't been successful, i'm sorry. I bet it is libroslib-dev version 1.14.3-1 where upstream introduced the ros_environment package. Can you test if downgrading

Re: ROS: catkin and ROS_PACKAGE_PATH

Hi Jorg, * Jörg [2018-07-15 22:14]: When i recompiled my bigger workspaces (ros-desktop, moveit) suddenly cmake doesn't find all include directories (e.g Eigen and OGRE) anymore. For libeigen i could add ${EIGEN_INCLUDE_DIRS} to include_dirs() but for OGRE this doesn't work. That's an

Re: [ROS] Bringing ros-visualization to Debian

* Jochen Sprickerhof [2018-09-07 17:13]: If you reduce it to one it should work. This seems to be already fixed in the shiboken git. I'm not sure why it is generated like this, though. I've send a patch with a fix here: https://github.com/ros-visualization/python_qt_binding/pull/48

Re: [ROS] Bringing ros-visualization to Debian

* H. [2018-09-06 11:36]: Command line: --generatorSet=shiboken

Re: [ROS] Bringing ros-visualization to Debian

Hi Dino, * H. [2018-09-06 11:36]: During my experiments I encountered one problem: The shiboken generator wasn't able to find some include files, although they exist and the include paths are set correctly in the command line (according to the output of the generator which I attached).

Re: [ROS] librosconsole defective?

Hi Dino, * H. [2018-09-20 09:45]: To investigate the problem, I took the source of rosconsole from https://github.com/ros/rosconsole (as well as roscpp), compiled it and linked against it. The problem was gone, so I think this issue is caused by wrong linkage to log4cxx in Testing. Thanks a

Re: Multiple versions of Ignition libraries for different simulators

* Jose Luis Rivero [2021-08-17 14:05]: ignition-gazebo is a rewrite of the good old Gazebo (Gazebo classic) which is designed to supersede it. Can be seen as a ROS 1 vs ROS 2 evolution since they share some important aspects like the break of compatibility with the antecesor. It is hard to say

Re: Multiple versions of Ignition libraries for different simulators

Hi Jose, sorry for the late reply. I had a longer discussion with Timo about this today. * Jose Luis Rivero [2021-08-11 18:10]: Development upstream (Open Robotics) is now focused on the new ignition-gazebo simulator (considered like the sucesor of Gazebo) which depends on the whole

Re: Multiple versions of Ignition libraries for different simulators

* Jose Luis Rivero [2021-08-17 22:08]: Thanks, looks like a lot of features are there while a bunch is still missing. Not sure if it makes sense to update already, but I don't use Gazebo currently so your call. Your quick look I think is accurate. [..] A possible migration plan inside

Moving packages to new robotics team on Salsa

Hi science people, we have formed a new Debian robotics team and would like to move all the ros*-* packages to the new team on Salsa. This is only possible as owner, whereas I have maintainer status. Could someone do that for us or give me the rights to do it? Thanks! Jochen signature.asc

Re: MRs on salsa and letting janitor automate things

Hi Dima, * Dima Kogan [2022-12-02 13:53]: The reason is that a package that has Build-Depends: debhelper-compat (=13) will fail to build on any older distro. I maintain some tools where I provide packages for a number of distros, and adding such a Build-Depends would mean I need to do extra

Re: Bug#1040500: routine-update: Don't create d/salsa-ci.yml file

Hi Andreas, * Andreas Tille [2023-07-07 09:20]: Am Thu, Jul 06, 2023 at 09:03:23PM +0100 schrieb Christopher Obbard: routine-update adds a file under the path "debian/salsa-ci.yml". Yes, this is intended. According to the salsa-ci-team[1], the default recommendation is to set the pipeline

Re: Bug#1040500: routine-update: Don't create d/salsa-ci.yml file

* Andreas Tille [2023-07-07 11:24]: Thanks for your opinion about this. What I mean with de facto standard: We have about 2000 repositories configured to check debian/salsa-ci.yml. I have not yet found a way to set the according field via gitlab API to something else. If this is scriptable