Github messages for voidlinux
 help / color / mirror / Atom feed
From: gspe <gspe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Mediainfo
Date: Fri, 15 Jan 2021 09:05:29 +0100	[thread overview]
Message-ID: <20210115080529.1tj42qQbT3Fx3Xa8axpif6wenhl3agexauiR1_S0H8c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27936@inbox.vuxu.org>

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

There is an updated pull request by gspe against master on the void-packages repository

https://github.com/gspe/void-packages mediainfo
https://github.com/void-linux/void-packages/pull/27936

Mediainfo
This fix a thread safety problem present in  `libzen`
https://github.com/sbraz/pymediainfo/issues/105
https://github.com/MediaArea/ZenLib/commit/70868fe21d8c58373389dd318a76695136580a4b

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

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

From a1fdbf1a8aaa75cb30308d42c01632c364feaf73 Mon Sep 17 00:00:00 2001
From: Giuseppe Fierro <gspe@ae-design.ws>
Date: Thu, 14 Jan 2021 21:48:51 +0100
Subject: [PATCH] libzen: upgrade to 0.4.38

This version solve thread safety problem
https://github.com/sbraz/pymediainfo/issues/105
---
 srcpkgs/libzen/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/libzen/template b/srcpkgs/libzen/template
index 9294962da97..5c4472c857a 100644
--- a/srcpkgs/libzen/template
+++ b/srcpkgs/libzen/template
@@ -1,14 +1,14 @@
 # Template build file for 'libzen'.
 pkgname=libzen
-version=0.4.37
-revision=2
+version=0.4.38
+revision=1
 short_desc="Shared library for libmediainfo and mediainfo"
 homepage="http://mediaarea.net/MediaInfo"
 maintainer="Georg Schabel <gescha@posteo.de>"
 license="zlib"
 
 distfiles="https://mediaarea.net/download/source/${pkgname}/${version}/${pkgname}_${version}.tar.gz"
-checksum=8c4323bd3f1a286a565b634cb00c9877922296679f49ac55b05f7c6e56d77c43
+checksum=ad98fccec235ed76a40e7da8856f0bcc9c8d07cafe4c3ce30c47407760add786
 
 build_style=gnu-configure
 hostmakedepends="automake libtool pkg-config"

  parent reply	other threads:[~2021-01-15  8:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 20:55 [PR PATCH] Mediainfo gspe
2021-01-14 20:59 ` Mediainfo q66
2021-01-14 21:19 ` Mediainfo ericonr
2021-01-14 21:21 ` Mediainfo ericonr
2021-01-14 21:21 ` Mediainfo ericonr
2021-01-14 21:33 ` Mediainfo ericonr
2021-01-14 21:42 ` Mediainfo ericonr
2021-01-14 21:42 ` Mediainfo ericonr
2021-01-14 21:43 ` Mediainfo ericonr
2021-01-15  8:05 ` gspe [this message]
2021-01-26  3:05 ` Mediainfo ericonr
2021-01-27 21:39 ` Mediainfo JeromeMartinez
2021-01-27 22:25 ` Mediainfo ericonr
2021-01-27 22:56 ` Mediainfo ericonr
2021-02-15  3:47 ` [PR PATCH] [Closed]: Mediainfo ericonr

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=20210115080529.1tj42qQbT3Fx3Xa8axpif6wenhl3agexauiR1_S0H8c@z \
    --to=gspe@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).