self explanatory
I intended to skip that version, as the only change is, in my opinion, too small to invest the pagaging resources of a new release. I am waiting for a new more significant release since then. Are you affected by the one bug fixed in that release or is that request more out of the general desire to stay up to date?
(In reply to Jan Henke from comment #1) > I intended to skip that version, as the only change is, in my opinion, too > small to invest the pagaging resources of a new release. > > I am waiting for a new more significant release since then. Are you affected > by the one bug fixed in that release or is that request more out of the > general desire to stay up to date? It is mostly the latter, but idk what "resources" are you referring to, just have to update ebuild and merge it. It's not like one have to make binary package and upload and waste everyone's bandwidth for minor change.
There's really no problems with trivial bumps, and it does good figure to be up to date if there's no issues with the version. Being trivial usually means very little review work as far as proxy-maint is concerned too (e.g. we just add stuff like signal-desktop-bin bumps every 3-5 days on the sides with routine testing, no real time involved). prebuilt fonts don't take a while to update for users too :)
(In reply to Jan Henke from comment #1) > I intended to skip that version, as the only change is, in my opinion, too > small to invest the pagaging resources of a new release. > > I am waiting for a new more significant release since then. Are you affected > by the one bug fixed in that release or is that request more out of the > general desire to stay up to date? There is must be a reason behind why upstream tagged new version. even if change is minor, package should be updated just for sake of having "latest & greatest" in repos
Rahil, could you do a Github pull request bumping it, so we get it to everyone? (In reply to Jan Henke from comment #1) > too small to invest the pagaging resources of a new release. > This can be seen in a tragicomical way. I don't know what jhenke meant, but it's true we launch bunch of CI and tinderbox runs with "minor" bumps. But I'm sure Gentoo is not near amongst the top ones in this game. Where I come from, electricity can be produced in ecological way, and I'm sure watching Twitch for a short time is worse than compiling the same (small) package on 10 different systems.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=19462eddf6a1668082088cf5ef0d6c0a13fdd0ba commit 19462eddf6a1668082088cf5ef0d6c0a13fdd0ba Author: Jan Henke <Jan.Henke@taujhe.de> AuthorDate: 2022-05-01 15:58:17 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2022-05-02 12:46:33 +0000 media-fonts/cascadia-code: add 2111.01 Closes: https://bugs.gentoo.org/839534 Signed-off-by: Jan Henke <Jan.Henke@taujhe.de> Closes: https://github.com/gentoo/gentoo/pull/25276 Signed-off-by: Joonas Niilola <juippis@gentoo.org> media-fonts/cascadia-code/Manifest | 1 + .../cascadia-code/cascadia-code-2111.01.ebuild | 19 +++++++++++++++++++ 2 files changed, 20 insertions(+)
