Github messages for voidlinux
 help / color / mirror / Atom feed
From: Clos3y <Clos3y@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] ffuf: updated checksum and fixed import path
Date: Tue, 21 Mar 2023 20:16:28 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42904@inbox.vuxu.org> (raw)

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

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

https://github.com/Clos3y/void-packages ffuf-checksum-fix
https://github.com/void-linux/void-packages/pull/42904

ffuf: updated checksum and fixed import path
#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures:
  - aarch64-musl (cross)
  - armv7l (cross)
  - armv6l-musl (cross)
  - x86_64-musl (cross)

---

- **Briefly** means I ran `$ ffuf` and it didn't produce any stderr
- Fixes tracked package `ffuf` in #39072

A patch file from https://github.com/void-linux/void-packages/pull/42904.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ffuf-checksum-fix-42904.patch --]
[-- Type: text/x-diff, Size: 1035 bytes --]

From 3eab137624c5693b9e4173887937b615aa20bdea Mon Sep 17 00:00:00 2001
From: clos3y <sam.w.close@gmail.com>
Date: Tue, 21 Mar 2023 19:04:41 +0000
Subject: [PATCH] ffuf: updated checksum and fixed import path

---
 srcpkgs/ffuf/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/ffuf/template b/srcpkgs/ffuf/template
index 9b1fb612e6f9..677bb939a846 100644
--- a/srcpkgs/ffuf/template
+++ b/srcpkgs/ffuf/template
@@ -1,15 +1,15 @@
 # Template file for 'ffuf'
 pkgname=ffuf
 version=2.0.0
-revision=1
+revision=2
 build_style=go
-go_import_path="github.com/ffuf/ffuf"
+go_import_path="github.com/ffuf/ffuf/v2@latest"
 short_desc="Fast web fuzzer"
 maintainer="Andrew Benson <abenson+void@gmail.com>"
 license="MIT"
 homepage="https://github.com/ffuf/ffuf"
 distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=bc27b19ed78b31862b1922a3adb66839cdf58c9b799a715c206709a73e2583d0
+checksum=80b42fe3dda8b24e10bade7b18651d402d1acf5031baedd0b344985721f3d8cd
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2023-03-21 19:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 19:16 Clos3y [this message]
2023-03-22  4:16 ` [PR PATCH] [Merged]: " classabbyamp

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-42904@inbox.vuxu.org \
    --to=clos3y@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).