From: tranzystorekk <tranzystorekk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] fend: update to 1.4.0
Date: Wed, 27 Dec 2023 09:56:59 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47921@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/47921
fend: update to 1.4.0
<!-- 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/47921.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fend-47921.patch --]
[-- Type: text/x-diff, Size: 1446 bytes --]
From 757e158ad829048748f70b602f4af52cbfe47d5a Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Wed, 27 Dec 2023 09:55:37 +0100
Subject: [PATCH] fend: update to 1.4.0
---
srcpkgs/fend/template | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/fend/template b/srcpkgs/fend/template
index 0d620c9929353..2679558b60288 100644
--- a/srcpkgs/fend/template
+++ b/srcpkgs/fend/template
@@ -1,21 +1,20 @@
# Template file for 'fend'
pkgname=fend
-version=1.3.3
+version=1.4.0
revision=1
build_style=cargo
make_install_args="--path cli"
short_desc="Arbitrary-precision unit-aware calculator"
maintainer="Marcin Puc <tranzystorek.io@protonmail.com>"
-license="MIT"
+license="GPL-3.0-or-later"
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="90364fab29b51e1c359ff72f8ccfc3e8a3c96bbc8b38d0646c28c489a8071084
- 758527c10e18c573f1f6e76b9ea15aae10de9defb3ecb01e2a2495f47cd927d9"
+checksum="1d3e37c2688846539b1666a924fdee5bdf60f54d94c8be6ccfd4364267f13af0
+ b2a23e220473a9151f76bf18dc27c94ccc09afe4b7eacb49848d0a181bfdee38"
skip_extraction="fend.1"
post_install() {
- vlicense LICENSE.md
vman ${XBPS_SRCDISTDIR}/${pkgname}-${version}/fend.1
}
next reply other threads:[~2023-12-27 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 8:56 tranzystorekk [this message]
2024-01-06 20:34 ` [PR PATCH] [Merged]: " ahesford
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-47921@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).