Github messages for voidlinux
 help / color / mirror / Atom feed
From: natrys <natrys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] epub2txt: update to 2.04.
Date: Thu, 30 Jun 2022 11:51:23 +0200	[thread overview]
Message-ID: <20220630095123.pWCLjwxNXCr3cOmMnkKQk9NUHwEKe1WUeq-7kkLWc7k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37166@inbox.vuxu.org>

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

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

https://github.com/natrys/void-packages epub2txt-2.04
https://github.com/void-linux/void-packages/pull/37166

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

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### 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/37166.patch is attached

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

From 44024b6e42c0b633bdbc4b03db9836d450bf928a Mon Sep 17 00:00:00 2001
From: Imran Khan <imrankhan@teknik.io>
Date: Tue, 17 May 2022 14:12:01 +0000
Subject: [PATCH] epub2txt: update to 2.06.

---
 srcpkgs/epub2txt/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/epub2txt/template b/srcpkgs/epub2txt/template
index 5f37e28ade6e..961fa0157525 100644
--- a/srcpkgs/epub2txt/template
+++ b/srcpkgs/epub2txt/template
@@ -1,6 +1,6 @@
 # Template file for 'epub2txt'
 pkgname=epub2txt
-version=2.01
+version=2.06
 revision=1
 wrksrc=epub2txt2-$version
 build_style=gnu-makefile
@@ -9,4 +9,4 @@ maintainer="Paper <paper@tilde.institute>"
 license="GPL-3.0-only"
 homepage="https://github.com/kevinboone/epub2txt2"
 distfiles="https://github.com/kevinboone/epub2txt2/archive/v$version.tar.gz"
-checksum=82c96c713c8a6e10d7b37e96db83a9d5f50fcb4b65034b4a1df1024776b6591f
+checksum=d45ad76a1adca6b62bf0ccbc1aed3a527c3bc2a790516e8de82cc1e6545548b6

  parent reply	other threads:[~2022-06-30  9:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 14:24 [PR PATCH] " natrys
2022-05-19 18:37 ` Chocimier
2022-05-19 19:30 ` natrys
2022-06-29 19:52 ` Duncaen
2022-06-29 19:52 ` Duncaen
2022-06-29 20:18 ` natrys
2022-06-30  9:51 ` natrys [this message]
2022-06-30  9:54 ` epub2txt: update to 2.06 natrys
2022-06-30 11:22 ` [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=20220630095123.pWCLjwxNXCr3cOmMnkKQk9NUHwEKe1WUeq-7kkLWc7k@z \
    --to=natrys@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).