Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] cargo-about: update to 0.4.7.
Date: Sun, 20 Feb 2022 16:32:37 +0100	[thread overview]
Message-ID: <20220220153237.kJwwpSgBYtdmtMHJabYOO3CF0D3vNBET9BL1rTNmWxg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33959@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1638 bytes --]

There is an updated pull request by jcgruenhage against master on the void-packages repository

https://github.com/jcgruenhage/void-packages cargo-about-0.4.1_1
https://github.com/void-linux/void-packages/pull/33959

cargo-about: update to 0.4.7.
blocked by #32555 

<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/33959.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cargo-about-0.4.1_1-33959.patch --]
[-- Type: text/x-diff, Size: 1291 bytes --]

From 0aa43742c746250fc0f09b4014c0a0952f7005b6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Mon, 8 Nov 2021 12:46:19 +0100
Subject: [PATCH] cargo-about: update to 0.4.7.

---
 srcpkgs/cargo-about/template | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/cargo-about/template b/srcpkgs/cargo-about/template
index 27eddbd2cfc4..0335d3ab97b3 100644
--- a/srcpkgs/cargo-about/template
+++ b/srcpkgs/cargo-about/template
@@ -1,14 +1,15 @@
 # Template file for 'cargo-about'
 pkgname=cargo-about
-version=0.3.0
+version=0.4.7
 revision=1
 build_style=cargo
 short_desc="Cargo plugin to generate list of all licenses for a crate"
 maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
 license="MIT, Apache-2.0"
 homepage="https://github.com/EmbarkStudios/cargo-about"
+changelog="https://raw.githubusercontent.com/EmbarkStudios/cargo-about/main/CHANGELOG.md"
 distfiles="https://github.com/EmbarkStudios/cargo-about/archive/${version}.tar.gz"
-checksum=01c5c78e4486b6de5694c0f140cab4b0f6efb807736a64602636a2266e2f015b
+checksum=186e44af7edde48e682b2670ef52ef21687629900f5220bbd3742cb2d665bb49
 
 if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
 	broken="broken on architectures without atomic8"

  parent reply	other threads:[~2022-02-20 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 11:47 [PR PATCH] WIP: cargo-about: update to 0.4.1 jcgruenhage
2022-02-09 16:29 ` [PR PATCH] [Updated] " jcgruenhage
2022-02-09 17:14 ` jcgruenhage
2022-02-20  0:24 ` [PR REVIEW] cargo-about: update to 0.4.7 paper42
2022-02-20 15:32 ` jcgruenhage [this message]
2022-02-20 17:07 ` jcgruenhage
2022-02-20 18:03 ` [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=20220220153237.kJwwpSgBYtdmtMHJabYOO3CF0D3vNBET9BL1rTNmWxg@z \
    --to=jcgruenhage@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).