From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] starship: update to 1.10.2
Date: Sat, 20 Aug 2022 06:48:25 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38788@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
There is a new pull request by cinerea0 against master on the void-packages repository
https://github.com/cinerea0/void-packages star
https://github.com/void-linux/void-packages/pull/38788
starship: update to 1.10.2
<!-- 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/38788.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-star-38788.patch --]
[-- Type: text/x-diff, Size: 1021 bytes --]
From 4078ef353622482591519f07e19b123d14980ad1 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Sat, 20 Aug 2022 00:45:32 -0400
Subject: [PATCH] starship: update to 1.10.2
---
srcpkgs/starship/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/starship/template b/srcpkgs/starship/template
index 0a8e73cef9b1..297ff2de1a92 100644
--- a/srcpkgs/starship/template
+++ b/srcpkgs/starship/template
@@ -1,6 +1,6 @@
# Template file for 'starship'
pkgname=starship
-version=1.10.1
+version=1.10.2
revision=1
build_style=cargo
build_helper=qemu
@@ -12,7 +12,7 @@ maintainer="cinerea0 <cinerea0@protonmail.com>"
license="ISC"
homepage="https://starship.rs"
distfiles="https://github.com/starship/starship/archive/refs/tags/v${version}.tar.gz"
-checksum=0dcf3a087748c241207a8c86a8c7b6e4d5558916d22deb4348942797d58c3ed9
+checksum=b3833c3b23906db778bd0d9a7d87ed232745739e47ce59bcfa8e92c7f0f930e9
post_build() {
STARSHIP="target/${RUST_TARGET}/release/starship"
next reply other threads:[~2022-08-20 4:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 4:48 cinerea0 [this message]
2022-08-20 5:16 ` cinerea0
2022-09-08 18:42 ` tranzystorek-io
2022-09-09 0:49 ` [PR PATCH] [Updated] " cinerea0
2022-09-09 1:20 ` starship: update to 1.10.3 cinerea0
2022-09-10 13:19 ` [PR PATCH] [Merged]: " paper42
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-38788@inbox.vuxu.org \
--to=cinerea0@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).