From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] miniserve: update to 0.18.0
Date: Mon, 24 Jan 2022 18:14:31 +0100 [thread overview]
Message-ID: <20220124171431.nJk3_QizSStXj58cgetMEPcY97gLEDw8Zobmsg9rYTQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34964@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
There is an updated 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/34964
miniserve: update to 0.18.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
A patch file from https://github.com/void-linux/void-packages/pull/34964.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-mini-34964.patch --]
[-- Type: text/x-diff, Size: 1237 bytes --]
From 078ef7e728af327f1ae731ed8443404ae97f34a8 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Mon, 24 Jan 2022 12:14:11 -0500
Subject: [PATCH] miniserve: update to 0.18.0
---
srcpkgs/miniserve/template | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/miniserve/template b/srcpkgs/miniserve/template
index 6b55e67ad131..490cf222b733 100644
--- a/srcpkgs/miniserve/template
+++ b/srcpkgs/miniserve/template
@@ -1,6 +1,6 @@
# Template file for 'miniserve'
pkgname=miniserve
-version=0.14.0
+version=0.18.0
revision=1
build_style=cargo
checkdepends="curl"
@@ -8,8 +8,10 @@ short_desc="CLI tool to serve files and dirs over HTTP"
maintainer="Enno Boland <gottox@voidlinux.org>"
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=68e21c35a4577251f656f3d1ccac2de23abd68432810b11556bcc8976bb19fc5
+checksum=24860f103879fd881a522a7ad8f25f2c9dcd5e01287b0485bcabf3e88c719015
+make_check=no # tests pass locally but fail in CI
case "$XBPS_TARGET_MACHINE" in
x86_64*|i686*|arm*|aarch64*) ;;
next prev parent reply other threads:[~2022-01-24 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 16:44 [PR PATCH] " cinerea0
2022-01-11 20:40 ` ericonr
2022-01-12 0:27 ` cinerea0
2022-01-21 6:41 ` cinerea0
2022-01-24 17:14 ` cinerea0 [this message]
2022-01-24 23:53 ` [PR REVIEW] " paper42
2022-01-24 23:56 ` [PR PATCH] [Updated] " cinerea0
2022-01-25 10:24 ` [PR REVIEW] " paper42
2022-01-25 16:37 ` cinerea0
2022-01-25 23:33 ` [PR PATCH] [Merged]: " paper42
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=20220124171431.nJk3_QizSStXj58cgetMEPcY97gLEDw8Zobmsg9rYTQ@z \
--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).