Created attachment 254156 [details] patch.diff Hi, Please commit the patch.diff to upgrade topgrade to 16.0.1 Thanks in advance. Best, C.
Hi, Would it not be make sense to implement an auto upgrade process for such of ports like this, or does it already exists ? Best, C.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=17784cbc27aa4f335daa4664e519876d10472957 commit 17784cbc27aa4f335daa4664e519876d10472957 Author: Rodrigo Osorio <rodrigo@FreeBSD.org> AuthorDate: 2024-10-18 08:57:07 +0000 Commit: Rodrigo Osorio <rodrigo@FreeBSD.org> CommitDate: 2024-10-18 12:48:18 +0000 sysutils/topgrade: update to 16.0.1 Changelog: https://github.com/topgrade-rs/topgrade/releases/tag/v16.0.1 PR: 282010 Reported by: <freebsd@scd-systems.net> (maintainer) sysutils/topgrade/Makefile | 3 +-- sysutils/topgrade/Makefile.crates | 30 ++++++++++++++++++++-- sysutils/topgrade/distinfo | 54 ++++++++++++++++++++++++++++++++++----- 3 files changed, 76 insertions(+), 11 deletions(-)
Committed with minor changes, thanks. I close the PR but we can still discussing. What do you mean by "auto upgrade process" for ports ? A process who perform port upgrades on user computers for dedicated application ? cheers, -- rodrigo
(In reply to Rodrigo Osorio from comment #3) Hi Rodrigo, Thank you very much for the merge. Regarding "auto upgrade process". My question is about why I do need to create a merge request ticket manually just for a simple patch which can be done by a cronjob or task which can be run in background. The patch it self was generated by just some make and git commands (always the same). This could also be done by a CI job, right ? The idea whould be to trigger a job runner to generate the patches automatically when the port-scout detects a new program version. Best, Cliff