while testing some upgrades (3.27 seems worth upgrading) I’ve found
a behavior that might cause some headaches.
When I upgrade a ROS with an enabled test-package and forgot to place the
new test-package along with the main ros-package the package is disabled.
So ROS 3.18 with wireless-test enabled. Upgrade to 3.27. wireless package
is disabled completely. So if upgrading via wireless I shoot myself into the knee.
I cant reach the router and the settings for wlan are gone.
MT: If upgrade procedure does not find a test-package, please use the
normal version.
well, wireless or no wireless, it does what it’s supposed to do - replace old packages with new ones. if there is no old one - there is no new one. the upgrader doesn’t have any idea of the meaning of these packages. it just compares names and versions.
Yes. This was not to blame the behavior. But it leads to unexpected problems nevertheless.
If the human upgrader is not very carefully and inspects the installed packages he ran into
trouble. So making the non human upgrader a bit smarter (if packagenotfound and packagename ends
in “-test” try package without “-test”) helps saving some administrator-knees.