From: lilmike <lilmike@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Tintin: update to 2.02.10_1
Date: Fri, 19 Mar 2021 13:55:02 +0100 [thread overview]
Message-ID: <20210319125502.MXkn_LGu8V6KT5S9F9bemTLBZWyC7k7OFekk_g4Msps@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29583@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1620 bytes --]
There is an updated pull request by lilmike against master on the void-packages repository
https://github.com/lilmike/void-packages tintin
https://github.com/void-linux/void-packages/pull/29583
Tintin: update to 2.02.10_1
<!-- 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?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] 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.)
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-musl (cross)
- [x] armv7l (cross)
- [x] armv6l-musl (cross)
-->
A patch file from https://github.com/void-linux/void-packages/pull/29583.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tintin-29583.patch --]
[-- Type: text/x-diff, Size: 1006 bytes --]
From 8df525ab26bb839a669beb9778afaf9be51474a1 Mon Sep 17 00:00:00 2001
From: Michael Taboada <michael@michaels.world>
Date: Fri, 19 Mar 2021 05:54:43 -0700
Subject: [PATCH] tintin: update to 2.02.10.
---
srcpkgs/tintin/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/tintin/template b/srcpkgs/tintin/template
index 4bedfe3ab047..5bbd8c71a616 100644
--- a/srcpkgs/tintin/template
+++ b/srcpkgs/tintin/template
@@ -1,6 +1,6 @@
# Template file for 'tintin'
pkgname=tintin
-version=2.02.05
+version=2.02.10
revision=1
wrksrc=tt
build_wrksrc=src
@@ -11,7 +11,7 @@ maintainer="Michael Taboada <voidpkgs@forwardme.email>"
license="GPL-2.0-or-later"
homepage="http://tintin.sourceforge.net"
distfiles="${SOURCEFORGE_SITE}/tintin/${pkgname}-${version}.tar.gz"
-checksum=63a70052122d24d69d7bc012395745f1a0412dffd456a8e8aab85704d44bd5a1
+checksum=079d316da0d5cfa2d737af647041e54dd00cd1b601a37f2bb127eb80251eaa1a
post_install() {
for i in FAQ SCRIPTS README; do
next prev parent reply other threads:[~2021-03-19 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 11:54 [PR PATCH] " lilmike
2021-03-19 12:55 ` lilmike [this message]
2021-03-19 12:56 ` lilmike
2021-03-19 17:24 ` [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=20210319125502.MXkn_LGu8V6KT5S9F9bemTLBZWyC7k7OFekk_g4Msps@z \
--to=lilmike@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).