From: ram02z <ram02z@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libuv: update to 1.43.0.
Date: Mon, 21 Mar 2022 12:06:48 +0100 [thread overview]
Message-ID: <20220321110648.KSOxXuDPodjlWBbn7TFFFngw_T3fAYL1xXwmmcOX4gc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35886@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
There is an updated pull request by ram02z against master on the void-packages repository
https://github.com/ram02z/void-packages libuv
https://github.com/void-linux/void-packages/pull/35886
libuv: update to 1.43.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### 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 [skip CI](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
-->
A patch file from https://github.com/void-linux/void-packages/pull/35886.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libuv-35886.patch --]
[-- Type: text/x-diff, Size: 1095 bytes --]
From 9f4272a86c213b2382192c8360f117d7f83b7707 Mon Sep 17 00:00:00 2001
From: Omar Zeghouani <omarzeghouanii@gmail.com>
Date: Mon, 28 Feb 2022 09:42:47 +0000
Subject: [PATCH] libuv: update to 1.43.0.
---
srcpkgs/libuv/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/libuv/template b/srcpkgs/libuv/template
index 76a36863f4b9..2575d92da2ad 100644
--- a/srcpkgs/libuv/template
+++ b/srcpkgs/libuv/template
@@ -1,6 +1,6 @@
# Template file for 'libuv'
pkgname=libuv
-version=1.41.0
+version=1.43.0
revision=1
build_style=gnu-configure
hostmakedepends="automake libtool pkg-config"
@@ -10,7 +10,7 @@ license="MIT, CC-BY-SA-4.0"
homepage="https://libuv.org/"
changelog="https://raw.githubusercontent.com/libuv/libuv/v1.x/ChangeLog"
distfiles="https://github.com/libuv/libuv/archive/v${version}.tar.gz"
-checksum=6cfeb5f4bab271462b4a2cc77d4ecec847fdbdc26b72019c27ae21509e6f94fa
+checksum=9e27825a55279de69a7c43e42d509fd1337c9bece2547c761e91a1592e91cc4d
# the tests fail when run as root and as such break in the CI containers
make_check="extended"
next prev parent reply other threads:[~2022-03-21 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 9:44 [PR PATCH] " ram02z
2022-03-21 11:06 ` ram02z [this message]
2022-03-27 18:32 ` [PR PATCH] [Merged]: " Vaelatern
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=20220321110648.KSOxXuDPodjlWBbn7TFFFngw_T3fAYL1xXwmmcOX4gc@z \
--to=ram02z@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).