From: tranzystorekk <tranzystorekk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] fend: update to 1.4.1
Date: Sun, 07 Jan 2024 12:26:33 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48100@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
There is a new pull request by tranzystorekk against master on the void-packages repository
https://github.com/tranzystorekk/void-packages fend
https://github.com/void-linux/void-packages/pull/48100
fend: update to 1.4.1
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-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/48100.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fend-48100.patch --]
[-- Type: text/x-diff, Size: 1220 bytes --]
From d15afcdccecdb463c22522a4010c7f96d6637735 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Sun, 7 Jan 2024 12:24:40 +0100
Subject: [PATCH] fend: update to 1.4.1
---
srcpkgs/fend/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/fend/template b/srcpkgs/fend/template
index 2679558b60288..07498ac272c44 100644
--- a/srcpkgs/fend/template
+++ b/srcpkgs/fend/template
@@ -1,6 +1,6 @@
# Template file for 'fend'
pkgname=fend
-version=1.4.0
+version=1.4.1
revision=1
build_style=cargo
make_install_args="--path cli"
@@ -11,8 +11,8 @@ homepage="https://printfn.github.io/fend/"
changelog="https://raw.githubusercontent.com/printfn/fend/main/CHANGELOG.md"
distfiles="https://github.com/printfn/fend/archive/refs/tags/v${version}.tar.gz
https://github.com/printfn/fend/releases/download/v${version}/fend.1"
-checksum="1d3e37c2688846539b1666a924fdee5bdf60f54d94c8be6ccfd4364267f13af0
- b2a23e220473a9151f76bf18dc27c94ccc09afe4b7eacb49848d0a181bfdee38"
+checksum="eb40e376e1da00055112edc583e86ac3913536b35f2f7265de55dca52319a4e4
+ 4296b44f1d290125cf43114d4556c3cde1c4124e979a83f6aeb3e924678ed362"
skip_extraction="fend.1"
post_install() {
next reply other threads:[~2024-01-07 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 11:26 tranzystorekk [this message]
2024-01-12 18:12 ` [PR PATCH] [Merged]: " classabbyamp
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-48100@inbox.vuxu.org \
--to=tranzystorekk@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).