From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] cargo-update: update to 13.0.4
Date: Sat, 20 May 2023 19:28:45 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43968@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
There is a new pull request by tranzystorek-io against master on the void-packages repository
https://github.com/tranzystorek-io/void-packages cargo-update
https://github.com/void-linux/void-packages/pull/43968
cargo-update: update to 13.0.4
<!-- 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/43968.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cargo-update-43968.patch --]
[-- Type: text/x-diff, Size: 1330 bytes --]
From 24eaf697823f35c93a803e94556e9e80ac07a7a0 Mon Sep 17 00:00:00 2001
From: Marcin Puc <tranzystorek.io@protonmail.com>
Date: Sat, 20 May 2023 19:27:24 +0200
Subject: [PATCH] cargo-update: update to 13.0.4
---
srcpkgs/cargo-update/template | 9 ++-------
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/srcpkgs/cargo-update/template b/srcpkgs/cargo-update/template
index 860dfe924247..086d3660bfaa 100644
--- a/srcpkgs/cargo-update/template
+++ b/srcpkgs/cargo-update/template
@@ -1,6 +1,6 @@
# Template file for 'cargo-update'
pkgname=cargo-update
-version=13.0.3
+version=13.0.4
revision=1
build_style=cargo
hostmakedepends="pkg-config go-md2man"
@@ -11,12 +11,7 @@ license="MIT"
homepage="https://github.com/nabijaczleweli/cargo-update"
changelog="https://github.com/nabijaczleweli/cargo-update/releases"
distfiles="https://github.com/nabijaczleweli/cargo-update/archive/refs/tags/v${version}.tar.gz"
-checksum=36643823e3dc5e7905ca6515ee5672799cbeb347ba9cb029ffc35265bd901fcb
-
-# on i686, unexpected index dir hashes are generated
-if [ "$XBPS_TARGET_MACHINE" == "i686" ]; then
- make_check_args="-- --skip ops::assert_index_path"
-fi
+checksum=cc07255dc6b7b61d7c54955ea33486b447f629564d9f3ebb88d421ab5bcdcdf6
post_patch() {
# Upstream does not ship a lockfile and is very vocal about that being
next reply other threads:[~2023-05-20 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 17:28 tranzystorek-io [this message]
2023-06-09 6:35 ` [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-43968@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).