From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] font-mplus-ttf: update to 063a
Date: Sun, 22 Sep 2019 15:45:03 +0200 [thread overview]
Message-ID: <20190922134503.CA6NurI6pYCqOfa2KmV4g_z8YFrenZbPc5wVqUYzNJ4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14641@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 316 bytes --]
There is an updated pull request by k4leg against master on the void-packages repository
https://github.com/k4leg/void-packages patch-3
https://github.com/void-linux/void-packages/pull/14641
font-mplus-ttf: update to 063a
A patch file from https://github.com/void-linux/void-packages/pull/14641.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-3-14641.patch --]
[-- Type: text/x-diff, Size: 2007 bytes --]
From da6ee191fb0a0ce2d8a76ee0e0edaec454e9791e Mon Sep 17 00:00:00 2001
From: k4leg <39882583+k4leg@users.noreply.github.com>
Date: Sun, 22 Sep 2019 15:51:10 +0300
Subject: [PATCH 1/2] font-mplus-ttf: update to 063a
---
srcpkgs/font-mplus-ttf/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/font-mplus-ttf/template b/srcpkgs/font-mplus-ttf/template
index 865d8fad9a9..5ea2f09967f 100644
--- a/srcpkgs/font-mplus-ttf/template
+++ b/srcpkgs/font-mplus-ttf/template
@@ -1,6 +1,6 @@
# Template file for 'font-mplus-ttf'
pkgname=font-mplus-ttf
-version=063
+version=063a
revision=1
archs=noarch
wrksrc="mplus-TESTFLIGHT-${version}"
@@ -10,7 +10,7 @@ maintainer="Satoshi Amemiya <amemiya@protonmail.com>"
license="custom"
homepage="https://mplus-fonts.osdn.jp/"
distfiles="http://jaist.dl.osdn.jp/mplus-fonts/62344/mplus-TESTFLIGHT-${version}.tar.xz"
-checksum=149a5c97c35624d79ffb3cbbdd56559319085229acaf72b49b56adc5ede0979c
+checksum=44eb973b4b6aff574de454db105ddc23e6749c2294734bd9cb1e0d734e4cdd79
font_dirs="/usr/share/fonts/TTF"
do_install() {
From 8493e81c04fd4774d84bd2bbafb3ce40f92fe25f Mon Sep 17 00:00:00 2001
From: k4leg <39882583+k4leg@users.noreply.github.com>
Date: Sun, 22 Sep 2019 16:45:01 +0300
Subject: [PATCH 2/2] Update template
---
srcpkgs/font-mplus-ttf/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/font-mplus-ttf/template b/srcpkgs/font-mplus-ttf/template
index 5ea2f09967f..102d839baac 100644
--- a/srcpkgs/font-mplus-ttf/template
+++ b/srcpkgs/font-mplus-ttf/template
@@ -7,7 +7,7 @@ wrksrc="mplus-TESTFLIGHT-${version}"
depends="fontconfig font-util"
short_desc="M+ Japanese outline fonts"
maintainer="Satoshi Amemiya <amemiya@protonmail.com>"
-license="custom"
+license="CC0-1.0"
homepage="https://mplus-fonts.osdn.jp/"
distfiles="http://jaist.dl.osdn.jp/mplus-fonts/62344/mplus-TESTFLIGHT-${version}.tar.xz"
checksum=44eb973b4b6aff574de454db105ddc23e6749c2294734bd9cb1e0d734e4cdd79
next prev parent reply other threads:[~2019-09-22 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 12:51 [PR PATCH] " voidlinux-github
2019-09-22 13:45 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-22 13:45 ` voidlinux-github [this message]
2019-09-22 13:46 ` voidlinux-github
2019-09-22 13:46 ` voidlinux-github
2019-09-23 18:45 ` voidlinux-github
2019-09-23 18:45 ` voidlinux-github
2019-09-25 10:44 ` [PR PATCH] [Merged]: " voidlinux-github
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=20190922134503.CA6NurI6pYCqOfa2KmV4g_z8YFrenZbPc5wVqUYzNJ4@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).