From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] miniserve: update to 0.19.5
Date: Wed, 08 Jun 2022 21:02:49 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37461@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]
There is a new pull request by cinerea0 against master on the void-packages repository
https://github.com/cinerea0/void-packages mini
https://github.com/void-linux/void-packages/pull/37461
miniserve: update to 0.19.5
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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
-->
Pinging @Gottox since this is his package.
A patch file from https://github.com/void-linux/void-packages/pull/37461.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mini-37461.patch --]
[-- Type: text/x-diff, Size: 1063 bytes --]
From 32c9dc93e5589fadf7b5c0c9f6bb54fbedc00184 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Wed, 8 Jun 2022 15:01:46 -0400
Subject: [PATCH] miniserve: update to 0.19.5
---
srcpkgs/miniserve/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/miniserve/template b/srcpkgs/miniserve/template
index 9711efc4e566..fe4a47a4501f 100644
--- a/srcpkgs/miniserve/template
+++ b/srcpkgs/miniserve/template
@@ -1,6 +1,6 @@
# Template file for 'miniserve'
pkgname=miniserve
-version=0.18.0
+version=0.19.5
revision=1
build_style=cargo
checkdepends="curl"
@@ -10,7 +10,7 @@ license="MIT"
homepage="https://github.com/svenstaro/miniserve"
changelog="https://raw.githubusercontent.com/svenstaro/miniserve/master/CHANGELOG.md"
distfiles="https://github.com/svenstaro/miniserve/archive/v${version}.tar.gz"
-checksum=24860f103879fd881a522a7ad8f25f2c9dcd5e01287b0485bcabf3e88c719015
+checksum=6c758467bd546327505717ecab1a0f78a07226509dd5de098112065221882474
make_check=ci-skip
case "$XBPS_TARGET_MACHINE" in
next reply other threads:[~2022-06-08 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 19:02 cinerea0 [this message]
2022-06-08 19:51 ` [PR PATCH] [Updated] " cinerea0
2022-06-08 20:25 ` cinerea0
2022-06-11 5:07 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37461@inbox.vuxu.org \
--to=cinerea0@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).