Skip to content

request: backport msgpack 1.2.4 support to stable branch #10585

Closed

Description

@craftyguy

Alpine Linux recently upgraded msgpack to 1.2.4 and now borgbackup (1.4.5) will not run[1]. Rather than require distros to pin msgpack to some old version in the past just for borgbackup, it would be nice if the recent patches for supporting the latest version were backported to the stable release branch since it seems like borg 2.0 is still a ways out.

  1. https://gitlab.alpinelinux.org/alpine/aports/-/work_items/18540

Activity

  1. infectormp commented on Nov 2, 2026

    @infectormp
    Contributor

    it's already there #10552

  2. craftyguy commented on Nov 2, 2026

    @craftyguy
    Author

    nice. it's just not in a tagged release yet. are there any plans to tag a new stable release soon? :)

  3. ThomasWaldmann commented on Nov 2, 2026

    @ThomasWaldmann
    Member

    I am still waiting for some CVE numbers from github, but after that, there will be a 1.4.6 release.

  4. nijel commented on Nov 2, 2026

    @nijel

    In my experience waiting for CVE from GitHub can be around two months now for unpublished advisories. So consider if waiting is good approach.

  5. ThomasWaldmann commented on Nov 3, 2026

    @ThomasWaldmann
    Member

    @nijel That sounds like gh cve assignment is too slow to fulfill its purpose. :-( Any way to speed it up?

  6. nijel commented on Nov 3, 2026

    @nijel

    They are just overloaded. Publishing the advisory will prioritize the assignment in my experience. I use GHSA links in the release notes when publishing the release and accomply them with CVEs once they are available.

    PS: With some projects we also started to publish advisories for high and critical vulnerabilities only to reduce noise for users and load on CNA.

  7. ThomasWaldmann commented on Nov 3, 2026

    @ThomasWaldmann
    Member

    Yeah, I will also just use the GHSA id or link in the release note and won't wait for the CVE.

  8. ThomasWaldmann commented on Nov 3, 2026

    @ThomasWaldmann
    Member

    Closing this, already fixed in 1.4-maint.

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