From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] grype: update to 0.68.1
Date: Mon, 18 Sep 2023 19:40:59 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46116@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
There is a new pull request by cinerea0 against master on the void-packages repository
https://github.com/cinerea0/void-packages grype
https://github.com/void-linux/void-packages/pull/46116
grype: update to 0.68.1
#### Testing the changes
- I tested the changes in this PR: **YES**
A patch file from https://github.com/void-linux/void-packages/pull/46116.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-grype-46116.patch --]
[-- Type: text/x-diff, Size: 1958 bytes --]
From b912bd78981325957674e280bf550367520a4c54 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Mon, 18 Sep 2023 13:40:18 -0400
Subject: [PATCH] grype: update to 0.68.1
---
srcpkgs/grype/patches/fix-go-version.patch | 13 +++++++++++++
srcpkgs/grype/template | 6 ++----
2 files changed, 15 insertions(+), 4 deletions(-)
create mode 100644 srcpkgs/grype/patches/fix-go-version.patch
diff --git a/srcpkgs/grype/patches/fix-go-version.patch b/srcpkgs/grype/patches/fix-go-version.patch
new file mode 100644
index 0000000000000..746a67a0a6b22
--- /dev/null
+++ b/srcpkgs/grype/patches/fix-go-version.patch
@@ -0,0 +1,13 @@
+# Requirement for v1.21.1 has nothing to do with program capabilities, see https://github.com/anchore/grype/pull/1484
+diff --git a/go.mod b/go.mod
+index 3d72c07fa9..efdc329286 100644
+--- a/go.mod
++++ b/go.mod
+@@ -1,6 +1,6 @@
+ module github.com/anchore/grype
+
+-go 1.21.1
++go 1.21.0
+
+ require (
+ github.com/CycloneDX/cyclonedx-go v0.7.1
diff --git a/srcpkgs/grype/template b/srcpkgs/grype/template
index e5af3b550f65c..89d5a909b69b7 100644
--- a/srcpkgs/grype/template
+++ b/srcpkgs/grype/template
@@ -1,19 +1,17 @@
# Template file for 'grype'
pkgname=grype
-version=0.66.0
+version=0.68.1
revision=1
build_style=go
build_helper=qemu
go_import_path="github.com/anchore/grype"
go_package="github.com/anchore/grype/cmd/grype"
-hostmakedepends="go1.20"
short_desc="Vulnerability scanner for container images and filesystems"
maintainer="Jan Christian Grünhage <jan.christian@gruenhage.xyz>"
license="Apache-2.0"
homepage="https://github.com/anchore/grype"
distfiles="https://github.com/anchore/grype/archive/refs/tags/v${version}.tar.gz"
-checksum=b0e38671975c0871f1b9a7bacba376f90ecb429973cb4b5b9cf90a3f4e072304
-export GOTOOLCHAIN=go1.20
+checksum=cd8bc7eadd8ab4a9ff872dc30142e8451f0580380f292360d020cea3f9d51309
post_install() {
grype="${DESTDIR}/usr/bin/grype"
next reply other threads:[~2023-09-18 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 17:40 cinerea0 [this message]
2023-09-21 16:47 ` [PR PATCH] [Updated] " cinerea0
2023-09-22 21:58 ` [PR PATCH] [Merged]: grype: update to 0.69.0 Duncaen
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-46116@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).