From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: caddy: upgrade to 2.4.3
Date: Fri, 16 Jul 2021 21:56:48 +0200 [thread overview]
Message-ID: <20210716195648.BOG1S_kSfX3xQYllFt2ayZlckCE5nCx72oof4uzywLo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29128@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
There's a merged pull request on the void-packages repository
caddy: upgrade to 2.4.3
https://github.com/void-linux/void-packages/pull/29128
Description:
As there is currently a bug with go build info
(https://github.com/golang/go/issues/29228) a patch is needed to
fix printing the correct version number of the binary. Once the bug is
fixed, the patch can be dropped.
Fix for #22092
#### Have the results of the proposed changes been tested?
- [ x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
<!--
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
-->
next prev parent reply other threads:[~2021-07-16 19:56 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 19:50 [PR PATCH] caddy: upgrade to 2.3.0 patrickpichler
2021-02-28 19:51 ` [PR PATCH] [Updated] " patrickpichler
2021-03-01 5:00 ` patrickpichler
2021-03-01 9:14 ` the-maldridge
2021-03-01 9:40 ` patrickpichler
2021-03-01 9:41 ` patrickpichler
2021-03-01 9:41 ` patrickpichler
2021-03-01 9:43 ` patrickpichler
2021-03-01 19:56 ` [PR REVIEW] " ericonr
2021-03-02 5:22 ` [PR PATCH] [Updated] " patrickpichler
2021-03-02 5:55 ` patrickpichler
2021-03-02 6:58 ` patrickpichler
2021-03-03 5:03 ` [PR PATCH] [Updated] " patrickpichler
2021-03-08 4:04 ` ericonr
2021-03-16 16:53 ` patrickpichler
2021-03-17 11:06 ` lemmi
2021-04-11 4:10 ` [PR REVIEW] " ericonr
2021-04-14 17:53 ` [PR PATCH] [Updated] " patrickpichler
2021-04-14 17:58 ` [PR REVIEW] " patrickpichler
2021-04-14 18:36 ` lemmi
2021-04-14 18:41 ` [PR PATCH] [Updated] " patrickpichler
2021-04-14 18:42 ` [PR REVIEW] " patrickpichler
2021-04-14 19:27 ` ericonr
2021-04-14 19:27 ` ericonr
2021-04-15 4:01 ` patrickpichler
2021-04-15 13:44 ` [PR PATCH] [Updated] " patrickpichler
2021-05-14 19:58 ` mkreu
2021-06-25 15:42 ` [PR REVIEW] " steinex
2021-06-25 15:42 ` steinex
2021-06-25 15:42 ` steinex
2021-06-25 15:44 ` steinex
2021-06-25 16:13 ` steinex
2021-06-30 18:16 ` [PR PATCH] [Updated] " patrickpichler
2021-06-30 18:18 ` caddy: upgrade to 2.4.3 patrickpichler
2021-06-30 18:39 ` [PR PATCH] [Updated] " patrickpichler
2021-06-30 18:39 ` patrickpichler
2021-06-30 18:40 ` [PR PATCH] [Updated] " patrickpichler
2021-06-30 18:44 ` steinex
2021-06-30 18:45 ` [PR PATCH] [Updated] " patrickpichler
2021-06-30 18:50 ` patrickpichler
2021-06-30 18:56 ` [PR PATCH] [Updated] " patrickpichler
2021-07-16 19:45 ` ericonr
2021-07-16 19:48 ` ericonr
2021-07-16 19:56 ` ericonr [this message]
2021-07-16 19:57 ` 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=20210716195648.BOG1S_kSfX3xQYllFt2ayZlckCE5nCx72oof4uzywLo@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).