From: UsernameRandomlyGenerated <UsernameRandomlyGenerated@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] tllist: update to 1.0.5.
Date: Sat, 13 Feb 2021 11:58:23 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28723@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]
There is a new pull request by UsernameRandomlyGenerated against master on the void-packages repository
https://github.com/UsernameRandomlyGenerated/void-packages tllist105
https://github.com/void-linux/void-packages/pull/28723
tllist: update to 1.0.5.
<!-- 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/28723.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-tllist105-28723.patch --]
[-- Type: text/x-diff, Size: 962 bytes --]
From 5981f0d2e3582fcf0ed916e3f24938342bba1b16 Mon Sep 17 00:00:00 2001
From: UsernameRandomlyGenerated <coredavid@tutanota.com>
Date: Sat, 13 Feb 2021 11:57:23 +0100
Subject: [PATCH] tllist: update to 1.0.5.
---
srcpkgs/tllist/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/tllist/template b/srcpkgs/tllist/template
index 7a9805571f1..5ebcb2d241c 100644
--- a/srcpkgs/tllist/template
+++ b/srcpkgs/tllist/template
@@ -1,6 +1,6 @@
# Template file for 'tllist'
pkgname=tllist
-version=1.0.4
+version=1.0.5
revision=1
wrksrc=$pkgname
build_style=meson
@@ -9,7 +9,7 @@ maintainer="Isaac Freund <ifreund@ifreund.xyz>"
license="MIT"
homepage="https://codeberg.org/dnkl/tllist"
distfiles="${homepage}/archive/${version}.tar.gz"
-checksum=a135934d4955902d67f75f3c542ace3bfb7be3be9c44796852e76ea9e1d82b33
+checksum=b0f32c9b2c2015c8d8dd068fd4e8b586aa91ca1670badc274ec962559ee0aadd
post_install() {
vlicense LICENSE
next reply other threads:[~2021-02-13 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 10:58 UsernameRandomlyGenerated [this message]
2021-02-13 22:07 ` ericonr
2021-02-13 22:07 ` [PR PATCH] [Closed]: " 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28723@inbox.vuxu.org \
--to=usernamerandomlygenerated@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).