From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libde265: update to 1.0.12.
Date: Fri, 16 Jun 2023 19:27:38 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44472@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]
There is a new pull request by mhmdanas against master on the void-packages repository
https://github.com/mhmdanas/void-packages libde265-1.0.12
https://github.com/void-linux/void-packages/pull/44472
libde265: update to 1.0.12.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
Fixes a couple of security issues: https://github.com/strukturag/libde265/releases/tag/v1.0.12
<!--
#### 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/44472.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libde265-1.0.12-44472.patch --]
[-- Type: text/x-diff, Size: 1184 bytes --]
From b4242ceb237d61cee6f8bfc0109a1b76507815f3 Mon Sep 17 00:00:00 2001
From: triallax <triallax@tutanota.com>
Date: Fri, 16 Jun 2023 18:11:21 +0100
Subject: [PATCH] libde265: update to 1.0.12.
---
srcpkgs/libde265/template | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/libde265/template b/srcpkgs/libde265/template
index a9c70c63a41c..1e3048f509b4 100644
--- a/srcpkgs/libde265/template
+++ b/srcpkgs/libde265/template
@@ -1,6 +1,6 @@
# Template file for 'libde265'
pkgname=libde265
-version=1.0.11
+version=1.0.12
revision=1
build_style=gnu-configure
hostmakedepends="pkg-config"
@@ -10,7 +10,12 @@ license="LGPL-3.0-or-later"
homepage="https://www.libde265.org"
changelog="https://github.com/strukturag/libde265/releases"
distfiles="https://github.com/strukturag/libde265/releases/download/v${version}/libde265-${version}.tar.gz"
-checksum=2f8f12cabbdb15e53532b7c1eb964d4e15d444db1be802505e6ac97a25035bab
+checksum=62185ea2182e68cf68bba20cc6eb4c287407b509cf0a827d7ddb75614db77b5c
+
+post_install() {
+ # Why is this installed anyway?
+ rm -f ${DESTDIR}/bin/tests
+}
libde265-devel_package() {
short_desc+=" - development files"
next reply other threads:[~2023-06-16 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 17:27 mhmdanas [this message]
2023-06-22 10:43 ` [PR PATCH] [Merged]: " Duncaen
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-44472@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).