ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
it said that roswtf not found and can be installed by
sudo apt install python3-roswtf
It's unfortunate, but following that advice -- which comes from Ubuntu itself btw -- you've most likely broken your ROS install.
The package you've installed is an UpstreamPackage, not the version which is part of ROS Noetic.
Note that name of the package you installed: python3-roswtf
. The regular package is called ros-noetic-roswtf
.
As the upstream version depends on other upstream packages and conflicts with the regular ROS packages, the regular ROS packages get uninstalled. This is most likely the cause of roslaunch
no longer working.
You'll want to reinstall the regular ROS packages.
I expect things to start working again after that.
2 | No.2 Revision |
it said that roswtf not found and can be installed by
sudo apt install python3-roswtf
It's unfortunate, but following that advice -- which comes from Ubuntu itself btw -- you've most likely broken your ROS install.
The package you've installed is an UpstreamPackage, not the version which is part of ROS Noetic.
Note that name of the package you installed: python3-roswtf
. .
The regular package is called ros-noetic-roswtf
.
As the upstream version depends on other upstream packages and conflicts with the regular ROS packages, the regular ROS packages get uninstalled. This is most likely the cause of roslaunch
no longer working.
You'll want to reinstall the regular ROS packages.
I expect things to start working again after that.
3 | No.3 Revision |
it said that roswtf not found and can be installed by
sudo apt install python3-roswtf
It's unfortunate, but following that advice -- which comes from Ubuntu itself btw -- you've most likely broken your ROS install.
The package you've installed is an UpstreamPackage, not the version which is part of ROS Noetic.
Note that the name of the package you installed: python3-roswtf
.
The regular package is called ros-noetic-roswtf
.
As the upstream version depends on other upstream packages and conflicts with the regular ROS packages, the regular ROS packages get uninstalled. This is most likely the cause of roslaunch
no longer working.
You'll want to reinstall the regular ROS packages.
I expect things to start working again after that.
4 | No.4 Revision |
it said that roswtf not found and can be installed by
sudo apt install python3-roswtf
It's unfortunate, but following that advice -- which comes from Ubuntu itself btw -- you've most likely broken your ROS install.
The package you've installed is an UpstreamPackage, not the version which is part of ROS Noetic.
Note the name of the package you installed: python3-roswtf
.
The regular package is called ros-noetic-roswtf
.
As the upstream version depends on other upstream packages and conflicts with the regular ROS packages, the regular ROS packages get uninstalled. This is most likely the cause of roslaunch
no longer working.
You'll want to reinstall the regular ROS packages.
I expect things to start working again after that.
Edit:
I had also run
sudo apt install puthon3-rosdep2
which seems to have removed all the packages. It removed 49 packages.
then it might be prudent to just try a reinstall. Unless you can figure out from the apt
log which packages specifically were removed.
5 | No.5 Revision |
it said that roswtf not found and can be installed by
sudo apt install python3-roswtf
It's unfortunate, but following that advice -- which comes from Ubuntu itself btw -- you've most likely broken your ROS install.
The package you've installed is an UpstreamPackage, not the version which is part of ROS Noetic.
Note the name of the package you installed: python3-roswtf
.
The regular package is called ros-noetic-roswtf
.
As the upstream version depends on other upstream packages and conflicts with the regular ROS packages, the regular ROS packages get uninstalled. This is most likely the cause of roslaunch
no longer working.
You'll want to reinstall the regular ROS packages.
I expect things to start working again after that.
Edit:
I had also run
sudo apt install puthon3-rosdep2
which seems to have removed all the packages. It removed 49 packages.
then it might be prudent to just try a reinstall. Unless you can figure out from the apt
log which packages specifically were removed.
Edit 2:
I looked up in
/var/log/apt/history.log
and found out that runningsudo apt install python3-rosdep2
removed 49 packages, which seems to have caused all the problems:
you should be able to restore your ROS install to a working state by reinstalling those packages.
apt
will likely complain about those packages conflicting with the upstream packages, but you should just let it remove those.