Github messages for voidlinux
 help / color / mirror / Atom feed
From: Barbaross93 <Barbaross93@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] font-cozette: update to 1.18.0
Date: Mon, 03 Oct 2022 05:07:30 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39649@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

There is a new pull request by Barbaross93 against master on the void-packages repository

https://github.com/Barbaross93/void-packages cozette
https://github.com/void-linux/void-packages/pull/39649

font-cozette: update to 1.18.0
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, (x86_64)


A patch file from https://github.com/void-linux/void-packages/pull/39649.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cozette-39649.patch --]
[-- Type: text/x-diff, Size: 1124 bytes --]

From 0c0251139e23ddc00949247e20e11259c56b8dfb Mon Sep 17 00:00:00 2001
From: Barbaross <cullen.ross@proton.me>
Date: Sun, 2 Oct 2022 23:05:57 -0400
Subject: [PATCH] font-cozette: update to 1.18.0

---
 srcpkgs/font-cozette/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/font-cozette/template b/srcpkgs/font-cozette/template
index ad6b3acd0d12..20bbdcff11e7 100644
--- a/srcpkgs/font-cozette/template
+++ b/srcpkgs/font-cozette/template
@@ -1,6 +1,6 @@
 # Template file for 'font-cozette'
 pkgname=font-cozette
-version=1.13.0
+version=1.18.0
 revision=1
 create_wrksrc=yes
 hostmakedepends="font-util bdftopcf"
@@ -11,7 +11,7 @@ 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=11590b29856d9ffb2dc6c606009168ea87a3ecde7bcbe9fe542bc34b406c868d
+checksum=710966cb1d310c1af2340bfe77e67741d92ac38d4060d284e0090495c1534b8b
 font_dirs="/usr/share/fonts/misc /usr/share/fonts/TTF"
 
 do_install() {

             reply	other threads:[~2022-10-03  3:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03  3:07 Barbaross93 [this message]
2022-10-03 11:11 ` [PR PATCH] [Merged]: " sgn

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39649@inbox.vuxu.org \
    --to=barbaross93@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).