From: tranzystorekk <tranzystorekk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] fend: update to 1.4.6
Date: Sun, 31 Mar 2024 20:37:21 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49633@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/49633
fend: update to 1.4.6
<!-- 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/49633.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fend-49633.patch --]
[-- Type: text/x-diff, Size: 1223 bytes --]
From 94561b1f9d46f01a673a5e8da8137c7e699b865c Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Sun, 31 Mar 2024 20:36:35 +0200
Subject: [PATCH] fend: update to 1.4.6
---
srcpkgs/fend/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/fend/template b/srcpkgs/fend/template
index 76893258c9dd19..844b8cffc500d0 100644
--- a/srcpkgs/fend/template
+++ b/srcpkgs/fend/template
@@ -1,6 +1,6 @@
# Template file for 'fend'
pkgname=fend
-version=1.4.5
+version=1.4.6
revision=1
build_style=cargo
make_install_args="--path cli"
@@ -13,8 +13,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="1bf65941f690ef6f0c95cf2485e6675bd35c3a46725fe9d1ed06c810c1a05b22
- 0161a89e36e93b558e253bfb9daef2ebf85c82ed7f992b72963edbf63350e9be"
+checksum="88fe4abf2caf96241a2964f510fd8801ac22f5c1511a4817361e676e931b0ce0
+ 6a4d2ce5593ea4d5b61be4712c93024d7658a2da514f1cb385f808eefed528cc"
skip_extraction="fend.1"
post_install() {
next reply other threads:[~2024-03-31 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 18:37 tranzystorekk [this message]
2024-04-02 15:28 ` [PR PATCH] [Merged]: " cinerea0
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-49633@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).