-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing ros-iron-ros-gz installs Gazebo Garden instead of Fortress #454
Comments
Do you have any other PPAs or repositories installed? To me, it looks like you are using one of the "unofficial" binaries that we have packaged here: https://build.osrfoundation.org/job/ros_gzgarden_bridge-install-pkg_iron-ci-jammy-amd64/4/ Those should not be aviailable on packages.ros.org by default, though. |
I previously had Gazebo installed separately. Am I supposed to remove the Gazebo PPAs before trying to install Gazebo via ros-gz? As far as I see e.g. ros-iron-ros-gzgarden-image comes from the PPA: http://packages.osrfoundation.org/gazebo/ubuntu-stable jammy/main. |
When you want to use the ros_gz packages from a ros distribution (such as humble/iron/rolling), that will source the gazebo packages from The newest gazebo packages are always available from The |
I think
And
This shows that there's a Anyways, we should remove the version in our prereleases to avoid any confusion. cc @j-rivero |
This is a bug if this it is happening combining
This is correct. We are not generating packages with the same name than official ROS Iron ros_gz packages but change the name to use
Seems a bug indeed while I was producing the prerelease packages. I would prefer not to remove packages but override them with newer versions so the upgrade path is easier. There are some changes in |
The weird thing is that I didn't enable pre-releases on my system. If I run but for humble I get
|
This is wrong indeed. Could you please attach: |
I missed the pre-release PPA in my sources list. After removing the offending PPA, I indeed get and the output of I think that having the prerelease PPA active and trying to install |
You are right, the prerelease repository can host code that is not completely stable but should have not generated these kind of errors. |
Environment
Binary
Description
Steps to reproduce
sudo apt-get install ros-iron-ros-gz
Output
The text was updated successfully, but these errors were encountered: