From: heliocat <heliocat@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] acmetool: fix project homepage
Date: Wed, 10 Feb 2021 17:18:19 +0100 [thread overview]
Message-ID: <20210210161819.5rk4U3t63_hP4CuaHGGhbmDiwKfE37N9OLetuzEXDLM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28617@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]
There is an updated pull request by heliocat against master on the void-packages repository
https://github.com/heliocat/void-packages acmetool
https://github.com/void-linux/void-packages/pull/28617
acmetool: fix project homepage
<!-- Mark items with [x] where applicable -->
Not particularly sexy but I noticed that the homepage= pointed to a non-existent place.
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/28617.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-acmetool-28617.patch --]
[-- Type: text/x-diff, Size: 1234 bytes --]
From efc7f9fd7d59814a08b68ac145bc91e1467c2beb Mon Sep 17 00:00:00 2001
From: Colin Booth <colin@heliocat.net>
Date: Tue, 9 Feb 2021 23:42:48 -0800
Subject: [PATCH] acmetool: fix project homepage
---
srcpkgs/acmetool/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/acmetool/template b/srcpkgs/acmetool/template
index e9e3993b7fc..99da6d6c780 100644
--- a/srcpkgs/acmetool/template
+++ b/srcpkgs/acmetool/template
@@ -1,7 +1,7 @@
# Template file for 'acmetool'
pkgname=acmetool
version=0.2.1
-revision=1
+revision=2
build_style=go
go_import_path=github.com/hlandau/acme
go_package="github.com/hlandau/acme/cmd/acmetool"
@@ -9,8 +9,8 @@ hostmakedepends="git"
makedepends="libcap-devel"
short_desc="Tool to acquire certificates from ACME servers (such as Let's Encrypt)"
maintainer="Toyam Cox <Vaelatern@voidlinux.org>"
-license="RILTS-based"
-homepage="https://hlandau.github.io/acme/"
+license="MIT"
+homepage="https://hlandau.github.io/acmetool/"
distfiles="https://github.com/hlandau/acme/archive/v${version}.tar.gz
https://raw.githubusercontent.com/hlandau/rilts/master/licences/COPYING.MIT>COPYING"
checksum="54acffe7381696ecdc829f65810897075d17c5600c077f431eda5e5244189a74
next prev parent reply other threads:[~2021-02-10 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 7:47 [PR PATCH] " heliocat
2021-02-10 13:31 ` ericonr
2021-02-10 16:18 ` heliocat [this message]
2021-02-10 17:26 ` heliocat
2021-02-10 17:28 ` [PR PATCH] [Merged]: acmetool: fix project homepage and license 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=20210210161819.5rk4U3t63_hP4CuaHGGhbmDiwKfE37N9OLetuzEXDLM@z \
--to=heliocat@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).