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-tamzen: update to 1.11.5
Date: Wed, 26 Oct 2022 19:58:27 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40169@inbox.vuxu.org> (raw)

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

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

https://github.com/Barbaross93/void-packages tamzen
https://github.com/void-linux/void-packages/pull/40169

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

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

<!--
#### 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, (amd64)

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

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

From a5d94b6536eee11f13345aa8b74e3a12172029ac Mon Sep 17 00:00:00 2001
From: Barbaross <cullen.ross@proton.me>
Date: Wed, 26 Oct 2022 13:57:36 -0400
Subject: [PATCH] font-tamzen: update to 1.11.5

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

diff --git a/srcpkgs/font-tamzen/template b/srcpkgs/font-tamzen/template
index 819fb4dd9ecb..f12138d25d88 100644
--- a/srcpkgs/font-tamzen/template
+++ b/srcpkgs/font-tamzen/template
@@ -1,7 +1,7 @@
 # Template file for 'font-tamzen'
 pkgname=font-tamzen
-version=1.11.4
-revision=3
+version=1.11.5
+revision=1
 wrksrc="tamzen-font-Tamzen-${version}"
 makedepends="font-util"
 depends="$makedepends"
@@ -10,12 +10,12 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="custom:Tamzen"
 homepage="https://sunaku.github.io/tamsyn-1.7b-font-review.html"
 distfiles="https://github.com/sunaku/tamzen-font/archive/Tamzen-${version}.tar.gz"
-checksum=da677aaa4bb7a30fd23f92c0e93b6a3e66ca27817561390ec78a476cee3bcde7
+checksum=78d39f481bcb1011ea6c2f80259c4f2cd08147f9948f4d19e42c418c23b8518d
 
 font_dirs="/usr/share/fonts/misc"
 
 do_install() {
-	for f in pcf/Tamzen*.pcf; do
+	for f in pcf/Tamzen*.pcf otb/Tamzen*.otb; do
 		vinstall "$f" 644 usr/share/fonts/misc
 	done
 	for f in psf/Tamzen*.psf; do

             reply	other threads:[~2022-10-26 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 17:58 Barbaross93 [this message]
2022-10-26 18:01 ` [PR PATCH] [Updated] " Barbaross93
2022-10-27 22:28 ` [PR PATCH] [Merged]: " classabbyamp

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-40169@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).