Bug 267355 - devel/meson: update to 0.64.0
Summary: devel/meson: update to 0.64.0
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Jan Beich
URL: https://mesonbuild.com/Release-notes-...
Keywords: needs-qa, patch
Depends on:
Blocks:
 
Reported: 2022-10-26 09:39 UTC by Jan Beich
Modified: 2022-11-12 20:27 UTC (History)
2 users (show)

See Also:
tcberner: maintainer-feedback+
antoine: exp-run+


Attachments
v0 (RC1) (1.27 KB, patch)
2022-10-26 09:39 UTC, Jan Beich
no flags Details | Diff
vmaf workaround (1.71 KB, patch)
2022-10-30 10:21 UTC, Jan Beich
no flags Details | Diff
v0.1 (RC2 aka post-RC1 snapshot) (1.86 KB, patch)
2022-11-01 11:49 UTC, Jan Beich
no flags Details | Diff
v0.1 (RC2) (1.27 KB, patch)
2022-11-01 20:21 UTC, Jan Beich
no flags Details | Diff
v1 (apply via "git am") (1.26 KB, patch)
2022-11-06 17:28 UTC, Jan Beich
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Beich freebsd_committer freebsd_triage 2022-10-26 09:39:29 UTC
Created attachment 237643 [details]
v0 (RC1)

Previous dot-zero updates often had regressions, requiring to wait for a patch-level release. Let's try testing in advance.
Comment 1 Jan Beich freebsd_committer freebsd_triage 2022-10-26 10:13:42 UTC
Note, according to https://lists.freebsd.org/archives/freebsd-ports/2022-October/002788.html exp-runs moved from portmgr@ to pkgmgr@.
Comment 2 Antoine Brodin freebsd_committer freebsd_triage 2022-10-26 12:05:41 UTC
(In reply to Jan Beich from comment #1)
There must be something wrong in this announce.
Exp-runs are still received by portmgr@ as they may need some review.
Also, nobody receives those "pkgmgr@" bugs in bugzilla.
Comment 4 Jan Beich freebsd_committer freebsd_triage 2022-10-30 10:21:00 UTC
Created attachment 237718 [details]
vmaf workaround

Can you re-try with the attached workaround (to check those 80 previously skipped ports)? I've filed https://github.com/Netflix/vmaf/issues/1107 because I don't know how to fix it yet.
Comment 5 Jan Beich freebsd_committer freebsd_triage 2022-11-01 11:49:20 UTC
Created attachment 237781 [details]
v0.1 (RC2 aka post-RC1 snapshot)

Properly fixes everything in comment 3.
Comment 6 Jan Beich freebsd_committer freebsd_triage 2022-11-01 20:21:51 UTC
Created attachment 237795 [details]
v0.1 (RC2)

Proper RC2. No changes affecting FreeBSD since previous patch.

https://github.com/mesonbuild/meson/compare/21f86fa90209...0.64.0rc2
Comment 7 Jan Beich freebsd_committer freebsd_triage 2022-11-06 17:28:29 UTC
Created attachment 237905 [details]
v1 (apply via "git am")

Actual/stable release.

https://github.com/mesonbuild/meson/compare/0.64.0rc2...0.64.0
Comment 8 Tobias C. Berner freebsd_committer freebsd_triage 2022-11-07 06:38:34 UTC
lgtm after the exp-run.
Comment 9 Antoine Brodin freebsd_committer freebsd_triage 2022-11-07 18:16:26 UTC
Exp-run with rc2 looks fine
Comment 10 Antoine Brodin freebsd_committer freebsd_triage 2022-11-12 19:24:13 UTC
exp-run looks fine
Comment 11 commit-hook freebsd_committer freebsd_triage 2022-11-12 20:27:09 UTC
A commit in branch main references this bug:

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

commit c4f8add41d7a4a962dbac166ece36ae0ab71c127
Author:     Jan Beich <jbeich@FreeBSD.org>
AuthorDate: 2022-10-25 16:36:57 +0000
Commit:     Jan Beich <jbeich@FreeBSD.org>
CommitDate: 2022-11-12 20:26:24 +0000

    devel/meson: update to 0.64.0

    Changes:        https://mesonbuild.com/Release-notes-for-0-64-0.html
    PR:             267355
    Reported by:    GitHub (watch releases)
    Exp-run by:     antoine
    Approved by:    tcberner

 devel/meson/Makefile | 2 +-
 devel/meson/distinfo | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)