Github messages for voidlinux
 help / color / mirror / Atom feed
From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libfontenc: update to 1.1.7.
Date: Sat, 06 May 2023 21:18:09 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43772@inbox.vuxu.org> (raw)

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

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

https://github.com/mhmdanas/void-packages libfontenc-1.1.7
https://github.com/void-linux/void-packages/pull/43772

libfontenc: update to 1.1.7.
<!-- 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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


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

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

From fde9c51cb7f7a038d6b5f048b5a2cc1104faf252 Mon Sep 17 00:00:00 2001
From: mhmdanas <triallax@tutanota.com>
Date: Wed, 29 Mar 2023 21:22:57 +0100
Subject: [PATCH] libfontenc: update to 1.1.7.

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

diff --git a/srcpkgs/libfontenc/template b/srcpkgs/libfontenc/template
index 02e28e72510e..f4935199d9de 100644
--- a/srcpkgs/libfontenc/template
+++ b/srcpkgs/libfontenc/template
@@ -1,6 +1,6 @@
 # Template file for 'libfontenc'
 pkgname=libfontenc
-version=1.1.4
+version=1.1.7
 revision=1
 build_style=gnu-configure
 configure_args="--with-fontrootdir=/usr/share/fonts/X11"
@@ -9,9 +9,9 @@ makedepends="xorgproto zlib-devel"
 short_desc="Fontenc Library from X.org"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
-homepage="http://xorg.freedesktop.org/"
-distfiles="${XORG_SITE}/lib/${pkgname}-${version}.tar.bz2"
-checksum=2cfcce810ddd48f2e5dc658d28c1808e86dcf303eaff16728b9aa3dbc0092079
+homepage="https://xorg.freedesktop.org/"
+distfiles="${XORG_SITE}/lib/libfontenc-${version}.tar.xz"
+checksum=c0d36991faee06551ddbaf5d99266e97becdc05edfae87a833c3ff7bf73cfec2
 
 post_install() {
 	vlicense COPYING

             reply	other threads:[~2023-05-06 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 19:18 mhmdanas [this message]
2023-05-19 15:34 ` [PR PATCH] [Merged]: " ahesford

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-43772@inbox.vuxu.org \
    --to=mhmdanas@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).