From: josegpt <josegpt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] font-iosevka: update to 11.2.6.
Date: Wed, 19 Jan 2022 01:57:27 +0100 [thread overview]
Message-ID: <20220119005727.6B_wylYgtmitAJn4500Tkc9B-wnQrOIYga_8CQMKiDU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35113@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
There is an updated pull request by josegpt against master on the void-packages repository
https://github.com/josegpt/void-packages iosevka
https://github.com/void-linux/void-packages/pull/35113
font-iosevka: update to 11.2.6.
Testing the changes
- I tested the changes in this PR: **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/35113.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-iosevka-35113.patch --]
[-- Type: text/x-diff, Size: 1340 bytes --]
From 75e768e7e7e69e9da5261f3212ce2944a92b2c52 Mon Sep 17 00:00:00 2001
From: Jose G Perez Taveras <josegpt27@gmail.com>
Date: Tue, 18 Jan 2022 14:47:33 -0500
Subject: [PATCH] font-iosevka: update to 11.2.6.
---
srcpkgs/font-iosevka/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/font-iosevka/template b/srcpkgs/font-iosevka/template
index 894ad7e45211..f76d1f137166 100644
--- a/srcpkgs/font-iosevka/template
+++ b/srcpkgs/font-iosevka/template
@@ -1,6 +1,6 @@
# Template file for 'font-iosevka'
pkgname=font-iosevka
-version=11.0.0
+version=11.2.6
revision=1
create_wrksrc=yes
depends="font-util"
@@ -13,8 +13,8 @@ distfiles="https://raw.githubusercontent.com/be5invis/Iosevka/v${version}/LICENS
https://github.com/be5invis/Iosevka/releases/download/v${version}/super-ttc-iosevka-${version}.zip
https://github.com/be5invis/Iosevka/releases/download/v${version}/super-ttc-iosevka-slab-${version}.zip"
checksum="72c3d557ff41d871680652f56afd565ba6834c90eadc45a4ec15410dce1c0c80
- 71416d2112cf6b934c5518fbbf3ecdcc9933effcb24995030add6a3153782792
- 453901626f47deb25e20fd77ddbe85d705e1550c5172b7878772aa9319c70306"
+ cab61bc7330c9b1be40eea082b5a11b573e19ea3509330bd3f2d9ffdadb9cd5b
+ d62edfa62e95df1e93469285c16f9505e23aa99fc88f1e9811d9f88f5d2ad740"
font_dirs="/usr/share/fonts/TTF"
next prev parent reply other threads:[~2022-01-19 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 19:52 [PR PATCH] " josegpt
2022-01-19 0:03 ` [PR PATCH] [Updated] " josegpt
2022-01-19 0:57 ` josegpt [this message]
2022-01-19 14:51 ` [PR PATCH] [Merged]: " leahneukirchen
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=20220119005727.6B_wylYgtmitAJn4500Tkc9B-wnQrOIYga_8CQMKiDU@z \
--to=josegpt@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).