ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

max-krichenbauer's profile - activity

2021-08-26 03:30:28 -0500 received badge  Notable Question (source)
2021-01-18 07:43:01 -0500 received badge  Famous Question (source)
2020-12-18 13:40:30 -0500 received badge  Famous Question (source)
2020-06-18 10:55:08 -0500 received badge  Famous Question (source)
2020-06-18 10:55:08 -0500 received badge  Notable Question (source)
2020-04-11 05:36:20 -0500 received badge  Famous Question (source)
2020-02-18 05:01:40 -0500 received badge  Notable Question (source)
2020-01-22 04:27:15 -0500 received badge  Notable Question (source)
2020-01-12 05:38:23 -0500 received badge  Popular Question (source)
2020-01-10 13:37:33 -0500 commented answer bloom-release "pull request modifies a repository entry other than the one being released"

Thanks a lot! That indeed solved it!

2020-01-10 13:37:14 -0500 marked best answer bloom-release "pull request modifies a repository entry other than the one being released"

Hello!

Trying to release a new version (0.0.5) of ament_virtualenv for dashing, bloom-release ament_virtualenv --rosdistro dashing --track dashing aborted with the following message:

This generated pull request modifies a repository entry other than the one being released.
This likely occurred because the upstream rosdistro changed during this release.
This pull request will abort, please re-run this command with the -p option to try again.
  • I tried again with -p, but it fails every time.
  • I deleted everything in /tmp and tried again from scratch but it fails again with the same message.
  • I released it for crystal and that worked without problems.
  • I tried again for dashing and get the same error again.
  • I tried searching for solutions/answers but could not find any.

Does anybody have an idea as to what causes this? Thanks!

2020-01-10 13:31:29 -0500 commented question bloom-release "pull request modifies a repository entry other than the one being released"

Thanks, updated.

2020-01-10 13:31:19 -0500 edited question bloom-release "pull request modifies a repository entry other than the one being released"

bloom-release "pull request modifies a repository entry other than the one being released" Hello! Trying to release a n

2020-01-10 04:45:25 -0500 edited question bloom-release "pull request modifies a repository entry other than the one being released"

bloom-release "pull request modifies a repository entry other than the one being released" Hello! Trying to release a n

2020-01-10 04:44:44 -0500 asked a question bloom-release "pull request modifies a repository entry other than the one being released"

bloom-release "pull request modifies a repository entry other than the one being released" Hello! Trying to release a n

2020-01-10 04:43:09 -0500 asked a question bloom-release "pull request modifies a repository entry other than the one being released"

bloom-release "pull request modifies a repository entry other than the one being released" Hello! Trying to release a n

2019-12-24 06:09:56 -0500 received badge  Popular Question (source)
2019-12-24 04:40:54 -0500 commented answer How do I include the Python "packaging" library on build farm?

Thank you, now I understood. I'll try to get the key added.

2019-12-24 04:40:11 -0500 marked best answer How do I include the Python "packaging" library on build farm?

Hello!

I'm confused how to properly include a requirement for the Python packaging library into my package.

As far as I understand, that library is called python-packaging in ROS, so I added it to my package.xml. On my local system, it builds and runs without problems, but on the build farm, it fails with

05:55:04 Traceback (most recent call last):
05:55:04   File "/tmp/ws/install_isolated/ament_virtualenv/lib/python3.6/site-packages/ament_virtualenv/combine_requirements.py", line 30, in <module>
05:55:04     from packaging.requirements import Requirement, InvalidRequirement
05:55:04 ModuleNotFoundError: No module named 'packaging'

and

05:55:05 [1.060s]   File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 786, in resolve
05:55:05 [1.061s]     raise DistributionNotFound(req, requirers)
05:55:05 [1.061s] pkg_resources.DistributionNotFound: The 'packaging' distribution was not found and is required by ament-virtualenv

I've tried all forms of dependencies (build_depend, buildtool_depend, exec_depend, ...), and tried adding either packaging or python-packaging to the install_requires section in setup.py / setup.cgf.

Can someone please let me know the proper way to include packaging (the Python library) so that it'll build on the build farm as well?

Here is the build farm log for reference: http://build.ros2.org/job/Cdev__ament...

and the source code repository: https://github.com/esol-community/ame...

Thank you!

2019-12-24 03:09:52 -0500 commented answer How do I include the Python "packaging" library on build farm?

Thanks @tfoote Sorry, but I don't understand what you mean with "With links how to resolve it."?

2019-12-24 03:07:07 -0500 commented answer How do I include the Python "packaging" library on build farm?

I looked on index.ros.org and it seems there is no python3-packaging: https://index.ros.org/search/?term=packaging&s

2019-12-24 03:01:10 -0500 commented answer How do I include the Python "packaging" library on build farm?

Thank you for your answer @marguedas ! I changed it, but now I'm getting KeyError: 'python3-packaging' and RuntimeError:

2019-12-24 00:23:54 -0500 asked a question How do I include the Python "packaging" library on build farm?

How do I include the Python "packaging" library on build farm? Hello! I'm confused how to properly include a requiremen

2019-12-13 11:42:51 -0500 received badge  Popular Question (source)
2019-12-13 05:25:29 -0500 commented question colcon: finding workspaces during build

Thank you @Dirk Thomas I've added more context to the question. I've tested for CMAKE_SOURCE_DIR and it is not set as an

2019-12-13 05:23:35 -0500 edited question colcon: finding workspaces during build

colcon: finding workspaces during build Hello! I'm running into some trouble trying to find the package.xml and other f

2019-12-12 00:01:59 -0500 commented question colcon: finding workspaces during build

Thank you @Dirk Thomas . The background is that for our package ament_virtualenv we need access to the information in wh

2019-12-11 23:30:49 -0500 commented question colcon: finding workspaces during build

@Dirk Thomas: It does NOT rely on other package's src/ folder, but: (1) it requires it's own files, which - on ament_cm

2019-12-11 23:30:23 -0500 commented question colcon: finding workspaces during build

@Dirk Thomas: It does NOT rely on other package's src/ folder, but: - it requires it's own files, which - on ament_cmak

2019-12-11 08:52:47 -0500 commented question colcon: finding workspaces during build

@slorenz Both (ament_cmake and ament_python) and both (same package and those packages that dependencies).

2019-12-11 08:52:47 -0500 received badge  Commentator
2019-12-11 02:43:34 -0500 asked a question colcon: finding workspaces during build

colcon: finding workspaces during build Hello! I'm running into some trouble trying to find the package.xml and other f

2019-12-11 02:42:30 -0500 asked a question colcon: finding workspaces during build

colcon: finding workspaces during build Hello! I'm running into some trouble trying to find the package.xml and other f

2019-10-12 14:06:14 -0500 received badge  Famous Question (source)
2019-10-12 13:54:42 -0500 received badge  Notable Question (source)
2019-10-09 16:49:53 -0500 received badge  Notable Question (source)
2019-09-03 10:54:00 -0500 received badge  Popular Question (source)
2019-08-29 18:31:51 -0500 marked best answer Could not resolve the rosdep key 'catkin'

Hello!

Building packages on a local build farm (not my own packages, the same packages as in the official ROS distros), yesterday everything worked fine, but today, all build jobs fail with:

reading in sources list data from /etc/ros/rosdep/sources.list.d
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml
Query rosdistro index http://mybuildfarm/rosdistro/index.yaml
Add distro "kinetic"
updated cache in /home/buildfarm/.ros/rosdep/sources.cache
Crawling for packages in workspace '/tmp/ws/src'

[INFO ABOUT THE PACKAGE TO BUILD]

Traceback (most recent call last):
  File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 272, in resolve_names
   rosdep_key, view, installer, os_name, os_code_name)
  File "/usr/lib/python3/dist-packages/rosdep2/catkin_support.py", line 87, in resolve_for_os
    d = view.lookup(rosdep_key)
  File "/usr/lib/python3/dist-packages/rosdep2/lookup.py", line 197, in lookup
   return self.rosdep_defs[rosdep_name]
KeyError: 'catkin'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 288, in <module>
    main()
  File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 125, in main
    debian_pkg_names += resolve_names(['catkin'], **context)
  File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 275, in resolve_names
    "Could not resolve the rosdep key '%s'" % rosdep_key)
RuntimeError: Could not resolve the rosdep key 'catkin'

It seems like the build cannot find catkin.

I tried clearing cashes and deleting and re-creating all jobs but the problem persists.

I checked the prerequisites: repository as specified in index.yaml which is http://packages.ros.org/ros/ubuntu/ and there were some changes last night, but I cannot tell if they are related.

Does anyone have a clue what could be causing this?

Thanks for your time!

Best regards, Max

2019-08-29 00:56:28 -0500 edited answer Could not resolve the rosdep key 'catkin'

Thanks to @nuclearsandwich for pointing me to the source of the issue: I wasn't aware even basic build tools like catkin

2019-08-29 00:56:28 -0500 received badge  Editor (source)
2019-08-29 00:13:41 -0500 received badge  Popular Question (source)
2019-08-28 22:40:23 -0500 answered a question Could not resolve the rosdep key 'catkin'

Thanks to @nuclearsandwich for pointing me to the source of the issue: I wasn't aware even basic build tools like catkin

2019-08-28 02:29:54 -0500 commented question Could not resolve the rosdep key 'catkin'

@nuclearsandwich Thank you for the comment! I checked the job's xml files and they use as --rosdistro-index-url the corr

2019-08-27 18:56:06 -0500 commented question Could not resolve the rosdep key 'catkin'

@nuclearsandwich Thank you for the comment! I checked the job's xml files and they use as --rosdistro-index-url the corr

2019-08-26 21:58:34 -0500 edited question Could not resolve the rosdep key 'catkin'

Could not resolve the rosdep key 'catkin' Hello! Building packages on a local build farm (not my own packages, the same

2019-08-26 21:58:03 -0500 asked a question Could not resolve the rosdep key 'catkin'

Could not resolve the rosdep key 'catkin' Hello! Building packages on a local build farm (not my own, the same ones as

2019-08-22 03:19:05 -0500 received badge  Enthusiast
2019-08-22 02:33:20 -0500 marked best answer Buildfarm jobs can't access ros_buildfarm, ros_buildfarm_config repos

Hello!

After setting deploying a buildfarm as outlined in the buildfarm_deployment and ros_buildfarm repository documentations, I noticed that most jobs fail with an error message similar to the following

python3 -u /home/jenkins-agent/workspace/Krel_arm_reconfigure-jobs/ros_buildfarm/scripts/release/run_release_reconfigure_job.py file:/tmp/deploy_ros_buildfarm/ros_buildfarm_config/index.yaml kinetic arm --distribution-repository-urls http://packages.ros.org/ros/ubuntu --distribution-repository-key-files /home/jenkins-agent/workspace/Krel_arm_reconfigure-jobs/keys/0.key --groovy-script /tmp/reconfigure_jobs/reconfigure_jobs.groovy --dockerfile-dir /home/jenkins-agent/workspace/Krel_arm_reconfigure-jobs/docker_generate_release_jobs

python3: can't open file '/home/jenkins-agent/workspace/Krel_arm_reconfigure-jobs/ros_buildfarm/scripts/release/run_release_reconfigure_job.py': [Errno 2] No such file or directory

It seems like the jobs require scripts from the ros_buildfarm repo but can't find it.

To test, I manually copied the repo into one of the job's workspace directories.

That overcame the previous error, but then the job fails with

docker run --rm --cidfile=/home/jenkins-agent/workspace/Krel_reconfigure-jobs/docker_generate_release_jobs/docker.cid -e=GIT_BRANCH= --net=host -v /home/jenkins-agent/workspace/Krel_reconfigure-jobs/ros_buildfarm:/tmp/ros_buildfarm:ro -v /home/jenkins-agent/.buildfarm:/home/buildfarm/.buildfarm:ro -v /home/jenkins-agent/workspace/Krel_reconfigure-jobs/reconfigure_jobs:/tmp/reconfigure_jobs release_reconfigure_jobs

Traceback (most recent call last):
    File "/usr/lib/python3.5/urllib/request.py", line 1410, in open_local_file
        stats = os.stat(localfile)

FileNotFoundError: [Errno 2] No such file or directory: '/tmp/deploy_ros_buildfarm/ros_buildfarm_config/index.yaml'

The file /tmp/deploy_ros_buildfarm/ros_buildfarm_config/index.yaml does exist (and contains the proper settings), but I assume it is not accessible from the docker container.

Can someone please explain to me how the jobs expect to access ros_buildfarm and ros_buildfarm_config?

Thanks in advance!

Max