From: Idesmi <Idesmi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] font-cozette: update to 1.13.0, build natively, provide python3-crayons for makedepends
Date: Wed, 13 Apr 2022 22:29:42 +0200 [thread overview]
Message-ID: <20220413202942.uTYT6RzuyGzboSx969qJf020dsoC1dP96H07n3P85xM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36503@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
There is an updated pull request by Idesmi against master on the void-packages repository
https://github.com/Idesmi/void-packages master
https://github.com/void-linux/void-packages/pull/36503
font-cozette: update to 1.13.0, build natively, provide python3-crayons for makedepends
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
A patch file from https://github.com/void-linux/void-packages/pull/36503.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-36503.patch --]
[-- Type: text/x-diff, Size: 1273 bytes --]
From 117898e31f82ecf8e7c0bcc5202dff358652f8fc Mon Sep 17 00:00:00 2001
From: Enrico Belleri <idesmi@protonmail.com>
Date: Sun, 3 Apr 2022 16:14:08 +0200
Subject: [PATCH] font-cozette: update to 1.13.0
---
srcpkgs/font-cozette/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/font-cozette/template b/srcpkgs/font-cozette/template
index 7a2e57669380..ad6b3acd0d12 100644
--- a/srcpkgs/font-cozette/template
+++ b/srcpkgs/font-cozette/template
@@ -1,7 +1,7 @@
# Template file for 'font-cozette'
pkgname=font-cozette
-version=1.11.3
-revision=2
+version=1.13.0
+revision=1
create_wrksrc=yes
hostmakedepends="font-util bdftopcf"
depends="font-util"
@@ -9,8 +9,9 @@ short_desc="Bitmap programming font optimized for coziness"
maintainer="Isaac Freund <ifreund@ifreund.xyz>"
license="MIT"
homepage="https://github.com/slavfox/Cozette"
+changelog="https://github.com/slavfox/Cozette/raw/master/CHANGELOG.md"
distfiles="https://github.com/slavfox/Cozette/releases/download/v.${version}/CozetteFonts.zip"
-checksum=0976f61ba68b3a261568819bce0b89d43ae2892ad51e5da399dab8a5894cbbc8
+checksum=11590b29856d9ffb2dc6c606009168ea87a3ecde7bcbe9fe542bc34b406c868d
font_dirs="/usr/share/fonts/misc /usr/share/fonts/TTF"
do_install() {
next prev parent reply other threads:[~2022-04-13 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 14:49 [PR PATCH] " Idesmi
2022-04-03 15:08 ` [PR PATCH] [Updated] " Idesmi
2022-04-03 15:10 ` Idesmi
2022-04-06 21:23 ` Idesmi
2022-04-06 21:38 ` Chocimier
2022-04-07 8:22 ` Idesmi
2022-04-13 19:51 ` Chocimier
2022-04-13 20:25 ` [PR PATCH] [Updated] " Idesmi
2022-04-13 20:29 ` Idesmi [this message]
2022-04-13 20:33 ` [PR PATCH] [Merged]: " Chocimier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220413202942.uTYT6RzuyGzboSx969qJf020dsoC1dP96H07n3P85xM@z \
--to=idesmi@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).