Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Go package clean up
Date: Sun, 18 Apr 2021 23:01:19 +0200	[thread overview]
Message-ID: <20210418210119.KGCHdWrKRycPtUQ5dTqLepdy1Znir5O-oDAj9mKYsJA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26377@inbox.vuxu.org>

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

There is an updated pull request by ericonr against master on the void-packages repository

https://github.com/ericonr/void-packages gorebuild
https://github.com/void-linux/void-packages/pull/26377

Go package clean up
While I get ready to do a full go rebuild, I found packages with various issues. Some broken ones and some had changed paths.

ping @the-maldridge @thypon @Vaelatern @misuchiru03 @renatoaguiar @steinex @CameronNemo 

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

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

From 9d3a5943b087e62d2416fbebfbfa9db7e9d7c04e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89rico=20Rolim?= <erico.erc@gmail.com>
Date: Sat, 14 Nov 2020 00:46:35 -0300
Subject: [PATCH] gfuzz: fix checksum, homepage and module paths.

---
 srcpkgs/gfuzz/template | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/gfuzz/template b/srcpkgs/gfuzz/template
index a51ea912896f..3925f06c9500 100644
--- a/srcpkgs/gfuzz/template
+++ b/srcpkgs/gfuzz/template
@@ -1,14 +1,14 @@
 # Template file for 'gfuzz'
 pkgname=gfuzz
 version=0.2
-revision=1
-wrksrc="gfuzz-${version}"
+revision=2
+wrksrc="gfz-${version}"
 build_style=go
-go_import_path=github.com/braaaax/gfuzz
+go_import_path=github.com/braaaax/gfz
 hostmakedepends="git"
 short_desc="Web fuzzer like wfuzz written in Golang"
 maintainer="Alex Childs <misuchiru03+void@gmail.com>"
 license="Apache-2.0"
-homepage="https://github.com/braaaax/gfuzz"
-distfiles="https://github.com/braaaax/gfuzz/archive/v${version}.tar.gz"
-checksum=054163243181db528715bf904ee7656aa0a12e9feb120c8afbfd43bd6504ccd1
+homepage="https://github.com/braaaax/gfz"
+distfiles="${homepage}/archive/v${version}.tar.gz"
+checksum=8b6a3df0c385fe993ead673df53daa290943220f2cde73e6b1c706ef94aa4e5f

  parent reply	other threads:[~2021-04-18 21:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14 17:22 [PR PATCH] " ericonr
2020-11-14 17:26 ` [PR PATCH] [Updated] " ericonr
2020-11-14 17:28 ` ericonr
2020-11-14 17:34 ` ericonr
2020-11-14 19:25 ` ericonr
2020-11-14 20:54 ` pullmoll
2020-11-14 22:34 ` [PR REVIEW] " the-maldridge
2020-11-14 22:34 ` the-maldridge
2020-11-14 22:59 ` ericonr
2020-11-14 23:07 ` ericonr
2020-11-15 17:04 ` sgn
2020-11-15 17:05 ` sgn
2020-11-15 17:06 ` sgn
2020-11-15 17:08 ` sgn
2020-11-15 21:01 ` ericonr
2020-11-15 23:22 ` [PR PATCH] [Updated] " ericonr
2020-11-17  1:24 ` ericonr
2020-12-30  7:01 ` the-maldridge
2021-01-04  2:16 ` [PR PATCH] [Updated] " ericonr
2021-02-14  3:52 ` ericonr
2021-04-18 21:01 ` ericonr [this message]
2021-04-18 21:05 ` [PR PATCH] [Merged]: " ericonr

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=20210418210119.KGCHdWrKRycPtUQ5dTqLepdy1Znir5O-oDAj9mKYsJA@z \
    --to=ericonr@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).