Created attachment 232375 [details] textproc/kepubify: update to 4.0.4 A bug fix release. Relevant pstream changes: - Allow the charset to be overridden, but default to utf-8. - Update koboutils for Libra2/Elipsa/Sage covergen support. Changelog: https://github.com/pgaskin/kepubify/releases/tag/v4.0.4
(In reply to Robert Clausecker from comment #0) There is no need to add such keywords to PRs. Thanks!
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=c9060e36560681073df3313b78af4e791d98c009 commit c9060e36560681073df3313b78af4e791d98c009 Author: Robert Clausecker <fuz@fuz.su> AuthorDate: 2022-03-10 23:10:47 +0000 Commit: Guangyuan Yang <ygy@FreeBSD.org> CommitDate: 2022-03-10 23:10:47 +0000 textproc/kepubify: Update to 4.0.4 Changelog: https://github.com/pgaskin/kepubify/releases/tag/v4.0.4 PR: 262475 MFH: 2022Q1 (bugfix release) textproc/kepubify/Makefile | 2 +- textproc/kepubify/distinfo | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-)
(In reply to Guangyuan Yang from comment #1) When would the "easy" keyword be appropriate then? I've added it because this is a PR that can be processed without having to solve any problem or writing code.
(In reply to Robert Clausecker from comment #3) Almost never, for a ports PR, in my opinion. Most of the ports PRs are about updating a port, and it is a pretty standard process with some testing but little debugging/writing code anyways. Adding "easy" won't trick the "system" (committers) into having the PR process faster. I am simply saying that there is no need for such keywords to be added to such standard occasions, it feels like a moot point. Thanks for the patch!