Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] syft: update to 0.60.1.
Date: Wed, 02 Nov 2022 11:26:54 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40296@inbox.vuxu.org> (raw)

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

There is a new pull request by jcgruenhage against master on the void-packages repository

https://github.com/jcgruenhage/void-packages syft-0.60.1_1
https://github.com/void-linux/void-packages/pull/40296

syft: update to 0.60.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 [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/40296.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-syft-0.60.1_1-40296.patch --]
[-- Type: text/x-diff, Size: 1022 bytes --]

From 17b4b3b79c33ff4e5717499c1137d23efd5e2697 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Wed, 2 Nov 2022 11:25:36 +0100
Subject: [PATCH] syft: update to 0.60.1.

---
 srcpkgs/syft/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/syft/template b/srcpkgs/syft/template
index fd7a65c00683..e34761a28654 100644
--- a/srcpkgs/syft/template
+++ b/srcpkgs/syft/template
@@ -1,6 +1,6 @@
 # Template file for 'syft'
 pkgname=syft
-version=0.60.0
+version=0.60.1
 revision=1
 build_style=go
 go_import_path="github.com/anchore/syft/cmd/syft"
@@ -9,4 +9,4 @@ maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
 license="Apache-2.0"
 homepage="https://github.com/anchore/syft"
 distfiles="https://github.com/anchore/syft/archive/refs/tags/v${version}.tar.gz"
-checksum=b20634a8e7cdaf8b6fd741390800ae8fe2eead9d468a75437a7cae2712777ba3
+checksum=ca5017eb9f4211ee6b53043998e4f1144df48427077ebf900941f548f3e6accf

             reply	other threads:[~2022-11-02 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 10:26 jcgruenhage [this message]
2022-11-03 12:31 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-03 19:52 ` [PR REVIEW] syft: update to 0.60.2 classabbyamp
2022-11-05 10:53 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-14 16:42 ` [PR PATCH] [Merged]: syft: update to 0.60.3 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-40296@inbox.vuxu.org \
    --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).