Github messages for voidlinux
 help / color / mirror / Atom feed
From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libass: update to 0.16.0.
Date: Tue, 24 May 2022 20:13:39 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37274@inbox.vuxu.org> (raw)

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

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

https://github.com/mhmdanas/void-packages libass-0.16.0
https://github.com/void-linux/void-packages/pull/37274

libass: update to 0.16.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly** (with mpv)

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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/37274.patch is attached

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

From 993a2f8ca902a075e8a8c1b6f8114a83dfaf87a8 Mon Sep 17 00:00:00 2001
From: mhmdanas <triallax@tutanota.com>
Date: Tue, 24 May 2022 21:15:43 +0300
Subject: [PATCH] libass: update to 0.16.0.

---
 srcpkgs/libass/template | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/libass/template b/srcpkgs/libass/template
index 5aa7953b7be2..d0da16a66704 100644
--- a/srcpkgs/libass/template
+++ b/srcpkgs/libass/template
@@ -1,6 +1,6 @@
 # Template file for 'libass'
 pkgname=libass
-version=0.15.2
+version=0.16.0
 revision=1
 build_style=gnu-configure
 hostmakedepends="automake libtool yasm pkg-config"
@@ -9,8 +9,9 @@ short_desc="Portable library for SSA/ASS subtitles rendering"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
 homepage="https://github.com/libass/libass/"
+changelog="https://github.com/libass/libass/raw/master/Changelog"
 distfiles="https://github.com/libass/libass/archive/${version}.tar.gz"
-checksum=f96b7ce35f2b0bf430eb71c4c9dd5d8f0abf52499e08490d346608c837c98299
+checksum=246091cf034b097dbe362c72170e6996f8d2c19ffe664ce6768ec44eb9ca5c1c
 
 pre_configure() {
 	autoreconf -fi

             reply	other threads:[~2022-05-24 18:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 18:13 mhmdanas [this message]
2022-05-24 18:16 ` [PR PATCH] [Updated] " mhmdanas
2022-05-24 19:22 ` [PR PATCH] [Merged]: " Chocimier

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