Github messages for voidlinux
 help / color / mirror / Atom feed
From: filiprojek <filiprojek@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] acme-client: update to 1.3.1, adopt
Date: Thu, 16 Mar 2023 14:52:41 +0100	[thread overview]
Message-ID: <20230316135241.Ab-s7oOC9RxTXYEOM8ri63I_hOn1NwhTMjGPPEfDhkY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42741@inbox.vuxu.org>

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

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

https://github.com/filiprojek/void-packages acme-client
https://github.com/void-linux/void-packages/pull/42741

acme-client: update to 1.3.1, adopt
Tagging the maintainer @lotheac 
#### 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)
- I built this PR locally for these architectures:
  - x86_64-musl

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

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

From 40d18c6d3f0ae764dad85d368259c1ed0ab92645 Mon Sep 17 00:00:00 2001
From: Filip Rojek <filip@filiprojek.cz>
Date: Mon, 13 Mar 2023 13:44:32 +0100
Subject: [PATCH] acme-client: update to 1.3.1, adopt

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

diff --git a/srcpkgs/acme-client/template b/srcpkgs/acme-client/template
index da8fd65f1f4c..0012110ca9b1 100644
--- a/srcpkgs/acme-client/template
+++ b/srcpkgs/acme-client/template
@@ -1,17 +1,17 @@
 # Template file for 'acme-client'
 pkgname=acme-client
-version=1.3.0
+version=1.3.1
 revision=1
 build_style=gnu-configure
 hostmakedepends="pkg-config sed"
 makedepends="openssl-devel"
 checkdepends="nginx curl"
 short_desc="Portable version of OpenBSD's acme-client"
-maintainer="Lauri Tirkkonen <lauri@hacktheplanet.fi>"
+maintainer="Emil Miler <em@0x45.cz>"
 license="GPL-2.0-only"
 homepage="https://git.sr.ht/~graywolf/acme-client-portable/"
 distfiles="https://data.wolfsden.cz/sources/acme-client-${version}.tar.gz"
-checksum=ac8796652393fa73f32dfda60ed3a437fc260867df1b81fa3c241bd95c5bc719
+checksum=94c0838ace0265017a630646cdd583f76fd2d724f67040175e54c08a9618c6ba
 make_check=no # requires https://github.com/letsencrypt/pebble which isn't packaged
 
 pre_install() {

  parent reply	other threads:[~2023-03-16 13:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13 12:50 [PR PATCH] acme-client: update to 1.3.1 filiprojek
2023-03-13 13:18 ` [PR PATCH] [Updated] " filiprojek
2023-03-13 13:18 ` filiprojek
2023-03-16 13:52 ` filiprojek [this message]
2023-03-16 13:55 ` acme-client: update to 1.3.1, adopt filiprojek
2023-03-29  6:10 ` [PR REVIEW] " classabbyamp
2023-03-29  8:40 ` [PR PATCH] [Updated] " filiprojek
2023-03-29  8:49 ` [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=20230316135241.Ab-s7oOC9RxTXYEOM8ri63I_hOn1NwhTMjGPPEfDhkY@z \
    --to=filiprojek@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).