From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] transifex-cli: update to 1.4.1
Date: Wed, 19 Oct 2022 10:08:57 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40036@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
There is a new pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages transifex
https://github.com/void-linux/void-packages/pull/40036
transifex-cli: 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: **briefly**
<!--
#### 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/40036.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-transifex-40036.patch --]
[-- Type: text/x-diff, Size: 1085 bytes --]
From fa70ab455bf0f17daa90a457d5187b26163e5167 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Wed, 19 Oct 2022 10:05:12 +0200
Subject: [PATCH] transifex-cli: update to 1.4.1
---
srcpkgs/transifex-cli/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/transifex-cli/template b/srcpkgs/transifex-cli/template
index d05980454366..008f601fb2ad 100644
--- a/srcpkgs/transifex-cli/template
+++ b/srcpkgs/transifex-cli/template
@@ -1,6 +1,6 @@
# Template file for 'transifex-cli'
pkgname=transifex-cli
-version=1.4.0
+version=1.4.1
revision=1
wrksrc="cli-${version}"
build_style=go
@@ -12,7 +12,7 @@ license="Apache-2.0"
homepage="https://github.com/transifex/cli"
changelog="https://github.com/transifex/cli/releases"
distfiles="https://github.com/transifex/cli/archive/refs/tags/v${version}.tar.gz"
-checksum=44f4dcf9a2be0c3b73456a4465d2b24601734a8bb21f564f4ebd702b7fedab67
+checksum=5a0f868f4ec05f99d2c1189d56a42591a827470f180e0d6c6a54038561513445
post_install() {
mv ${DESTDIR}/usr/bin/{cli,transifex}
next reply other threads:[~2022-10-19 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 8:08 tranzystorek-io [this message]
2022-10-20 5:23 ` [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-40036@inbox.vuxu.org \
--to=tranzystorek-io@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).