Github messages for voidlinux
 help / color / mirror / Atom feed
From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] ccextractor: update to 0.89
Date: Thu, 17 Jun 2021 17:41:16 +0200	[thread overview]
Message-ID: <20210617154116.LMJFwfFxlRqRmbj3plWt7jbh9GjczOOv6hbrUnO_XnQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31543@inbox.vuxu.org>

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

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

https://github.com/newbluemoon/void-packages ccextractor
https://github.com/void-linux/void-packages/pull/31543

ccextractor: update to 0.89
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR


<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/31543.patch is attached

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

From a767139b0ca416b587e985db5f6058af660528db Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Thu, 17 Jun 2021 17:06:56 +0200
Subject: [PATCH] ccextractor: update to 0.89

---
 srcpkgs/ccextractor/patches/disable_arm_neon.patch | 6 +++---
 srcpkgs/ccextractor/template                       | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/ccextractor/patches/disable_arm_neon.patch b/srcpkgs/ccextractor/patches/disable_arm_neon.patch
index 76dcada659d7..0eb114e1ddc0 100644
--- a/srcpkgs/ccextractor/patches/disable_arm_neon.patch
+++ b/srcpkgs/ccextractor/patches/disable_arm_neon.patch
@@ -1,6 +1,6 @@
---- src/libpng/pngpriv.h.orig	2017-01-24 01:56:17.000000000 +0100
-+++ src/libpng/pngpriv.h	2018-02-23 14:33:41.864333473 +0100
-@@ -105,6 +105,7 @@
+--- src/thirdparty/libpng/pngpriv.h.orig	2021-06-13 21:05:33.000000000 +0200
++++ src/thirdparty/libpng/pngpriv.h	2021-06-17 17:35:17.217940102 +0200
+@@ -107,6 +107,7 @@
   * this in $(CC), e.g. "CC=gcc -mfpu=neon", but people who build libpng rarely
   * do this.
   */
diff --git a/srcpkgs/ccextractor/template b/srcpkgs/ccextractor/template
index d4bdf07d6f76..fe27e68b04f5 100644
--- a/srcpkgs/ccextractor/template
+++ b/srcpkgs/ccextractor/template
@@ -1,7 +1,7 @@
 # Template file for 'ccextractor'
 pkgname=ccextractor
-version=0.88
-revision=2
+version=0.89
+revision=1
 build_wrksrc="linux"
 build_style=gnu-configure
 configure_args="--enable-ocr --enable-hardsubx"
@@ -13,7 +13,7 @@ license="GPL-2.0-or-later"
 homepage="https://www.ccextractor.org/"
 changelog="https://raw.githubusercontent.com/CCExtractor/ccextractor/master/docs/CHANGES.TXT"
 distfiles="https://github.com/CCExtractor/${pkgname}/archive/v${version}.tar.gz"
-checksum=e0bfad4c7cf5d8a05305107ab53829a33b209446aaec515d5c51b72392b1eda7
+checksum=bbe8d95347d0cf31bd26489b733fd959a7b98c681f14c59309bff54713fd539d
 CFLAGS="-I${XBPS_CROSS_BASE}/usr/include/tesseract -DPNG_POWERPC_VSX_OPT=0 -fcommon"
 
 pre_configure() {

  reply	other threads:[~2021-06-17 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17 15:09 [PR PATCH] " newbluemoon
2021-06-17 15:41 ` newbluemoon [this message]
2021-06-17 15:52 ` [PR PATCH] [Merged]: " 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=20210617154116.LMJFwfFxlRqRmbj3plWt7jbh9GjczOOv6hbrUnO_XnQ@z \
    --to=newbluemoon@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).