Bug 287159 - sysutils/vtm: update 2025.05.21 -> 2025.05.28
Summary: sysutils/vtm: update 2025.05.21 -> 2025.05.28
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: Vladimir Druzenko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-30 10:23 UTC by Yusuf Yaman
Modified: 2025-05-30 17:03 UTC (History)
2 users (show)

See Also:


Attachments
sysutils/vtm.patch: update 2025.05.21 -> 2025.05.28 (1.61 KB, patch)
2025-05-30 10:25 UTC, Yusuf Yaman
nxjoseph: maintainer-approval+
Details | Diff
sysutils/vtm.patch: update 2025.05.21 -> 2025.05.28 (2.24 KB, patch)
2025-05-30 16:11 UTC, Yusuf Yaman
nxjoseph: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Yusuf Yaman 2025-05-30 10:23:34 UTC

    
Comment 1 Yusuf Yaman 2025-05-30 10:25:54 UTC
Created attachment 260803 [details]
sysutils/vtm.patch: update 2025.05.21 -> 2025.05.28

Poudriere testport do pass for both 142amd64 and 142i386.

Port{clippy,fmt,lint} are OK.

Also added a conditional to not run patch stage if it's not needed.

Thanks in advance.
Comment 2 Vladimir Druzenko freebsd_committer freebsd_triage 2025-05-30 12:59:36 UTC
There's not much point in this: .if ${LUA_VER} != "5.4"
But if you really want to, I can add it.
Comment 3 Yusuf Yaman 2025-05-30 13:49:28 UTC
(In reply to Vladimir Druzenko from comment #2)
> There's not much point in this: .if ${LUA_VER} != "5.4"
> But if you really want to, I can add it.

Hmm, actually I wrote the conditional because of the "reinplace_cmd ran but did not modify contents of ..." warning, so with this conditional, it won't run the patch if lua version didn't change and therefore no warning will be thrown i guess.

Thanks for giving a look quickly!
Comment 4 Vladimir Druzenko freebsd_committer freebsd_triage 2025-05-30 13:57:25 UTC
(In reply to Yusuf Yaman from comment #3)
I treat this warning as "are you absolutely sure that this is how it should be?"
That is, it does not indicate an error, but suggests rechecking whether everything is correct.
IMHO this code just complicates the port for no real reason.
Comment 5 Vladimir Druzenko freebsd_committer freebsd_triage 2025-05-30 13:59:05 UTC
BTW: "NOTE: This vtm release is not compatible with previous versions"
Something needs to be done about this.
Add record to pkg-message or/and to UPDATING.
Comment 6 Yusuf Yaman 2025-05-30 15:43:25 UTC
(In reply to Vladimir Druzenko from comment #4)
> I treat this warning as "are you absolutely sure that this is how it should be?"
> That is, it does not indicate an error, but suggests rechecking whether everything is correct.
> IMHO this code just complicates the port for no real reason.

Hmm, thanks for opinions. it's not a complicated conditional for me but anyways i will remove it back.



(In reply to Vladimir Druzenko from comment #5)
> BTW: "NOTE: This vtm release is not compatible with previous versions"
> Something needs to be done about this.
> Add record to pkg-message or/and to UPDATING.

I will research pkg-message files on ports tree that records something like this as i do have no idea how i could do it in pkg-message.

If i can't do it in pkg-message, i'll see if i can do it in UPDATING.

Is there something wrong with Bugzilla? I don't get emails from bugzilla for replies and this causing me to reply a while late.

Thanks.
Comment 7 Yusuf Yaman 2025-05-30 16:09:46 UTC
Does it look good? I am not well informed about changes so i can't recommend something for users of previous versions, i just gave a link to changelog.

# pkg upgrade
Updating Poudriere repository catalogue...
Poudriere repository is up to date.
All repositories are up to date.
Updating database digests format: 100%
Checking for upgrades (3 candidates): 100%
Processing candidates (3 candidates): 100%
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        vtm: 0.9.99.71 -> 2025.05.28

Number of packages to be upgraded: 1

Proceed with this action? [y/N]: y
[1/1] Upgrading vtm from 0.9.99.71 to 2025.05.28...
[1/1] Extracting vtm-2025.05.28: 100%
=====
Message from vtm-2025.05.28:

--
Upgrades to vtm 2025.05.28
=====================

vtm 2025.05.28 contains changes that are made to
configuration settings which are backward-incompatible
for previous versions of vtm. The configuration settings
file has changed significantly due to the introduction
of Pure XML with dynamic element referencing and templating.

See also: https://github.com/directvt/vtm/releases/tag/v2025.05.27
Comment 8 Yusuf Yaman 2025-05-30 16:11:31 UTC
Created attachment 260807 [details]
sysutils/vtm.patch: update 2025.05.21 -> 2025.05.28
Comment 9 commit-hook freebsd_committer freebsd_triage 2025-05-30 16:53:04 UTC
A commit in branch main references this bug:

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

commit 640e5969e0be2cf703b0b738ca84aeb160164b75
Author:     Yusuf Yaman <nxjoseph@protonmail.com>
AuthorDate: 2025-05-30 16:38:07 +0000
Commit:     Vladimir Druzenko <vvd@FreeBSD.org>
CommitDate: 2025-05-30 16:51:29 +0000

    sysutils/vtm: Update 2025.05.21 => 2025.05.28

    Changelogs:
    https://github.com/directvt/vtm/releases/tag/v2025.05.27
    https://github.com/directvt/vtm/releases/tag/v2025.05.28

    Add record to pkg-message about incompatibility with previous versions.

    PR:     287159

 sysutils/vtm/Makefile          |  5 ++---
 sysutils/vtm/distinfo          |  6 +++---
 sysutils/vtm/pkg-message (new) | 17 +++++++++++++++++
 3 files changed, 22 insertions(+), 6 deletions(-)
Comment 10 Vladimir Druzenko freebsd_committer freebsd_triage 2025-05-30 16:54:31 UTC
Thanks.
Comment 11 Yusuf Yaman 2025-05-30 17:03:48 UTC
(In reply to Vladimir Druzenko from comment #10)
Thanks to you, i learn new things in general.

Have a good one.