Bug 266063 - archivers/liblz4: Update to v1.9.4
Summary: archivers/liblz4: Update to v1.9.4
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Po-Chuan Hsieh
URL: https://github.com/lz4/lz4/releases/t...
Keywords: patch
Depends on:
Blocks:
 
Reported: 2022-08-27 09:24 UTC by Martin Waschbüsch
Modified: 2022-11-09 11:42 UTC (History)
2 users (show)

See Also:
martin: maintainer-feedback+


Attachments
Update to v1.9.4 (1.66 KB, application/mbox)
2022-08-27 09:24 UTC, Martin Waschbüsch
martin: maintainer-approval+
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Waschbüsch 2022-08-27 09:24:07 UTC
Created attachment 236141 [details]
Update to v1.9.4
Comment 1 Martin Waschbüsch 2022-08-27 09:26:58 UTC
QA
portlint -AC: OK
poudriere testport on 13.1/amd64: OK
Comment 2 commit-hook freebsd_committer freebsd_triage 2022-08-27 10:50:48 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=efa005214e4254e1b2ee468c09009c71d5622e33

commit efa005214e4254e1b2ee468c09009c71d5622e33
Author:     Martin Waschbusch <martin@waschbuesch.de>
AuthorDate: 2022-08-27 10:49:53 +0000
Commit:     Po-Chuan Hsieh <sunpoet@FreeBSD.org>
CommitDate: 2022-08-27 10:50:04 +0000

    archivers/liblz4: Update to 1.9.4

    Changes:        https://github.com/lz4/lz4/releases
    PR:             266063

 archivers/liblz4/Makefile | 6 +++---
 archivers/liblz4/distinfo | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)
Comment 3 Daniel Engberg freebsd_committer freebsd_triage 2022-08-27 10:59:52 UTC
Hi,

It would've been nice if we could've waited on https://github.com/lz4/lz4/pull/1139 to land so unit tests works as expected.

Best regards,
Daniel
Comment 4 Martin Waschbüsch 2022-08-27 12:44:44 UTC
(In reply to Daniel Engberg from comment #3)
Noted. I'll try to keep an eye on that.
Should this not warrant a version bump from upstream's point of view, I may include the pull and update the port revision. If it does, an update will happen anyway.
Is that a reasonable approach?
Comment 5 Daniel Engberg freebsd_committer freebsd_triage 2022-08-27 12:50:07 UTC
Bump PORTREVISION as it does touch some things in the build process too. Sounds fine otherwise, thanks!
Comment 6 Daniel Engberg freebsd_committer freebsd_triage 2022-10-25 10:09:03 UTC
It has now landed
https://github.com/lz4/lz4/commit/214bfb325bd4db112b73859912b919aa35e12d61
Comment 7 Martin Waschbüsch 2022-10-25 12:19:43 UTC
(In reply to Daniel Engberg from comment #6)
Thanks. I followed that GH issue.

Question: Is it safe to use the state of affairs (in the dev branch) as of the commit you referenced? Or would the right approach be to stay with https://github.com/lz4/lz4/releases/tag/v1.9.4 and cherry-pick the commits relating to testing / meson?
Comment 8 Daniel Engberg freebsd_committer freebsd_triage 2022-10-25 15:48:50 UTC
(In reply to Martin Waschbüsch from comment #7)
Cherry-pick, if it piles up a lot I guess we should wait until next release to fix tests etc.
Comment 9 Martin Waschbüsch 2022-11-09 11:42:13 UTC
(In reply to Daniel Engberg from comment #8)

See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267667

Tests build, but one of the tests fails. Any help with that is appreciated.