From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] osv-scanner: update to 1.2.0.
Date: Thu, 23 Feb 2023 20:15:28 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42414@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
There is a new pull request by icp1994 against master on the void-packages repository
https://github.com/icp1994/void-packages osv-scanner
https://github.com/void-linux/void-packages/pull/42414
osv-scanner: update to 1.2.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture: **x86_64**
A patch file from https://github.com/void-linux/void-packages/pull/42414.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-osv-scanner-42414.patch --]
[-- Type: text/x-diff, Size: 1305 bytes --]
From f4522e036be829e03a6d0e962675a1b381927940 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Thu, 23 Feb 2023 11:24:59 +0530
Subject: [PATCH] osv-scanner: update to 1.2.0.
---
srcpkgs/osv-scanner/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/osv-scanner/template b/srcpkgs/osv-scanner/template
index 641d9605903e..b80f9f61c88a 100644
--- a/srcpkgs/osv-scanner/template
+++ b/srcpkgs/osv-scanner/template
@@ -1,6 +1,6 @@
# Template file for 'osv-scanner'
pkgname=osv-scanner
-version=1.1.0
+version=1.2.0
revision=1
build_style=go
go_import_path="github.com/google/osv-scanner"
@@ -9,10 +9,10 @@ go_ldflags="-X main.version=${version}"
short_desc="Vulnerability scanner which uses the data provided by https://osv.dev"
maintainer="icp <pangolin@vivaldi.net>"
license="Apache-2.0"
-homepage="https://github.com/google/osv-scanner"
+homepage="https://google.github.io/osv-scanner/"
changelog="https://raw.githubusercontent.com/google/osv-scanner/main/CHANGELOG.md"
distfiles="https://github.com/google/osv-scanner/archive/refs/tags/v${version}.tar.gz"
-checksum=c9e89ede6bb3945657192cdfecded355509d35eba39e74000f4e45f486df2c74
+checksum=c096df268d7d187eb54ae440fdb3baea534adcb3563c823c35a46d06f3ace029
do_check() {
go test ./...
next reply other threads:[~2023-02-23 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 19:15 icp1994 [this message]
2023-03-06 19:56 ` [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-42414@inbox.vuxu.org \
--to=icp1994@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).