Revision history [back]

Arch moved to the new ABI in December. Thus it was required to rebuild all the packages depending on the old C++ ABI.

As for notifications through the AUR, I'm the one maintaining the ROS packages on Arch (see that project). When there is that kind of change (e.g. a new Boost release), I usually try to target the update by bumping the impacted packages. This takes time, and since I am quite busy at the moment, I relied on the user's know-how. Plus, some of the dependencies that I'm not maintaining have not been updated either, so the errors would still be propagated throughout the ROS packages if the user does not decide to reinstall the packages manually, and there's absolutely nothing I can do about that (except notifying the maintainers).

Also, I'm still using Indigo for work, so I haven't updated Jade packages in a long time. I'll try to do that during the next few weeks.

Arch moved to the new C++ ABI in December. Thus it was required to rebuild all the packages depending on the old C++ ABI.

As for notifications through the AUR, I'm the one maintaining the ROS packages on Arch (see that project). When there is that kind of change (e.g. a new Boost release), I usually try to target the update by bumping the impacted packages. This takes time, and since I am quite busy at the moment, I relied on the user's know-how. Plus, some of the dependencies that I'm not maintaining have not been updated either, so the errors would still be propagated throughout the ROS packages if the user does not decide to reinstall the packages manually, and there's absolutely nothing I can do about that (except notifying the maintainers).

Also, I'm still using Indigo for work, so I haven't updated Jade packages in a long time. I'll try to do that during the next few weeks.