Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: osv-scanner-1.0.2
Date: Thu, 12 Jan 2023 13:51:34 +0100	[thread overview]
Message-ID: <20230112125134.OsdVyD3zpiilKxj7wYVT887Fpo63u7CXBKc5k5oLtC0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41390@inbox.vuxu.org>

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

There is an updated 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/41390

New package: osv-scanner-1.0.2
#### Description
OSV-Scanner provides an officially supported frontend to the [OSV database](https://osv.dev/) that connects a project’s list of dependencies with the vulnerabilities that affect them.

#### 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**

#### 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/41390.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-osv-scanner-41390.patch --]
[-- Type: text/x-diff, Size: 1242 bytes --]

From 5f92c785014b7010eb3c45703eef46fa4bbbbd1d Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Sat, 31 Dec 2022 01:16:16 +0530
Subject: [PATCH] New package: osv-scanner-1.1.0

---
 srcpkgs/osv-scanner/template | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 srcpkgs/osv-scanner/template

diff --git a/srcpkgs/osv-scanner/template b/srcpkgs/osv-scanner/template
new file mode 100644
index 000000000000..641d9605903e
--- /dev/null
+++ b/srcpkgs/osv-scanner/template
@@ -0,0 +1,19 @@
+# Template file for 'osv-scanner'
+pkgname=osv-scanner
+version=1.1.0
+revision=1
+build_style=go
+go_import_path="github.com/google/osv-scanner"
+go_package="${go_import_path}/cmd/osv-scanner"
+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"
+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
+
+do_check() {
+	go test ./...
+}

  parent reply	other threads:[~2023-01-12 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-01  6:35 [PR PATCH] " icp1994
2023-01-01  6:45 ` [PR PATCH] [Updated] " icp1994
2023-01-12 12:51 ` icp1994 [this message]
2023-01-22 21:21 ` [PR PATCH] [Merged]: " Piraty

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=20230112125134.OsdVyD3zpiilKxj7wYVT887Fpo63u7CXBKc5k5oLtC0@z \
    --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).