Skip to content

Inconsistent version_prefix.txt #1385

Closed

Description

@wentasah

In version tagged 2.15.20 version_prefix.txt contains 2.15.19. In previous releases, it contained the same number as the git tag. This seems to be caused by the fact that 2.15.20 and 2.15.19 releases are exactly the same.

Activity

  1. jlblancoc commented on Aug 1, 2026

    @jlblancoc
    Member

    Oh, good catch!

    Yes, indeed it was an overlooked file...

    Let me explain the state of things:

    MRPT 2.x is deprecated, and the recommended branch to use is 3.x ("develop").

    This "old" 2.x re-release was needed as the only way to enforce ROS2 packages for mrpt-2 to catch up this update, so all MRPT 2-3 packages use consistently the system version (or rosdep-provided, when using ros) of nanoflann:

    MRPT/mrpt_ros@08896bd

    I expect not having to do any further release under the 2.x series, unless there are people claiming for them for some reason.

    mrpt-3.x (develop) is nowadays way better debugged, tested, and better designed for minimal dependencies (no opencv, no X or GUI packages for non headless libraries or apps, etc.).

  2. jlblancoc commented on Aug 1, 2026

    @jlblancoc
    Member

    If this broke something on your side, @wentasah , I could update version_prefix.txt and force update the tag... does it sound ok?

  3. wentasah commented on Aug 2, 2026

    @wentasah
    ContributorAuthor

    I'm maintaining nix-ros-overlay and this broke MRPT 2 packages in it and all dependencies. It's not a big deal, the workaround was simple. But if you ever release a new version, I'd appreciate if that file is updated as well :-) No need to update existing tag.

    I personally used MRPT 2 in an old project, but now, I'm trying to have most of the ROS packages build correctly under Nix for other potential users. But honestly, I don't know how many of them are there. So until MRPT 2 is a part of ROS, I just want to have it usable.

  4. jlblancoc commented on Aug 3, 2026

    @jlblancoc
    Member

    Thanks for the explanation! I have force-pushed an updated tag 2.15.20, if that helps on your pipeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions