From: mhmdanas <mhmdanas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] c-ares: update to 1.19.0.
Date: Mon, 06 Feb 2023 23:32:16 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42122@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
There is a new pull request by mhmdanas against master on the void-packages repository
https://github.com/mhmdanas/void-packages c-ares-1.19.0
https://github.com/void-linux/void-packages/pull/42122
c-ares: update to 1.19.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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-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
-->
A patch file from https://github.com/void-linux/void-packages/pull/42122.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-c-ares-1.19.0-42122.patch --]
[-- Type: text/x-diff, Size: 1160 bytes --]
From 2590a0f116fb9a8f5ad94d07a562e3eb7914d77e Mon Sep 17 00:00:00 2001
From: mhmdanas <triallax@tutanota.com>
Date: Mon, 6 Feb 2023 22:31:17 +0000
Subject: [PATCH] c-ares: update to 1.19.0.
---
srcpkgs/c-ares/template | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/c-ares/template b/srcpkgs/c-ares/template
index e60de7e93fcd..c5fd155e1a03 100644
--- a/srcpkgs/c-ares/template
+++ b/srcpkgs/c-ares/template
@@ -1,6 +1,6 @@
# Template file for 'c-ares'
pkgname=c-ares
-version=1.18.1
+version=1.19.0
revision=1
build_style=gnu-configure
checkdepends="iana-etc"
@@ -9,9 +9,8 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://c-ares.haxx.se/"
changelog="https://c-ares.haxx.se/changelog.html"
-distfiles="${homepage}/download/${pkgname}-${version}.tar.gz"
-checksum=1a7d52a8a84a9fbffb1be9133c0f6e17217d91ea5a6fa61f6b4729cda78ebbcf
-make_check=ci-skip # segfaults only on CI
+distfiles="https://c-ares.haxx.se/download/c-ares-${version}.tar.gz"
+checksum=bfceba37e23fd531293829002cac0401ef49a6dc55923f7f92236585b7ad1dd3
pre_configure() {
export CFLAGS=${CFLAGS/-D_FORTIFY_SOURCE=?/}
next reply other threads:[~2023-02-06 22:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 22:32 mhmdanas [this message]
2023-02-15 21:44 ` [PR PATCH] [Updated] " mhmdanas
2023-04-09 15:29 ` mhmdanas
2023-04-09 15:29 ` [PR PATCH] [Closed]: " mhmdanas
2023-04-09 15:29 ` mhmdanas
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-42122@inbox.vuxu.org \
--to=mhmdanas@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).