From: cinerea0 <cinerea0@users.noreply.github.com> To: ml@inbox.vuxu.org Subject: Re: [PR PATCH] [Updated] starship: update to 1.1.1 Date: Fri, 14 Jan 2022 18:01:14 +0100 [thread overview] Message-ID: <20220114170114.pTPKwmu0S_9r-3ET8VXpb215L2Iaj0n9IPpNdYmW98c@z> (raw) In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34850@inbox.vuxu.org> [-- Attachment #1: Type: text/plain, Size: 1214 bytes --] There is an updated 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/34850 starship: update to 1.1.1 <!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO** --> <!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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/34850.patch is attached [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #2: github-pr-star-34850.patch --] [-- Type: text/x-diff, Size: 1019 bytes --] From 8ceb2df5b684d8607929139303c7ea06939431d2 Mon Sep 17 00:00:00 2001 From: cinerea0 <cinerea0@disroot.org> Date: Fri, 14 Jan 2022 12:01:01 -0500 Subject: [PATCH] starship: update to 1.2.0 --- srcpkgs/starship/template | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/srcpkgs/starship/template b/srcpkgs/starship/template index ea9b416552d9..60d2b0eed985 100644 --- a/srcpkgs/starship/template +++ b/srcpkgs/starship/template @@ -1,6 +1,6 @@ # Template file for 'starship' pkgname=starship -version=0.58.0 +version=1.2.0 revision=1 build_style=cargo build_helper=qemu @@ -13,7 +13,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=8bd4cfad4bcf9694633f228de0c7dc6cfab6bb6955e2a7299ed28dd8c4d6f5e4 +checksum=4b10562954e42e8e75b1a82fbe9484b8126735e610d8aec3366c7a98651e5898 post_build() { STARSHIP="target/${RUST_TARGET}/release/starship"
next prev parent reply other threads:[~2022-01-14 17:01 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-04 20:27 [PR PATCH] " cinerea0 2022-01-05 7:23 ` ericonr 2022-01-14 17:01 ` cinerea0 [this message] 2022-01-14 17:33 ` starship: update to 1.2.0 cinerea0 2022-01-15 17:39 ` [PR PATCH] [Updated] " cinerea0 2022-01-15 19:11 ` starship: update to 1.2.1 ericonr 2022-01-16 18:59 ` [PR PATCH] [Merged]: " ericonr
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=20220114170114.pTPKwmu0S_9r-3ET8VXpb215L2Iaj0n9IPpNdYmW98c@z \ --to=cinerea0@users.noreply.github.com \ --cc=ml@inbox.vuxu.org \ --subject='Re: [PR PATCH] [Updated] starship: update to 1.1.1' \ /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
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).