Github messages for voidlinux
 help / color / mirror / Atom feed
From: techflashYT <techflashYT@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] c-ares: Update to 1.30.0, apply new download link
Date: Sat, 08 Jun 2024 00:27:51 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50739@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

There is a new pull request by techflashYT against master on the void-packages repository

https://github.com/techflashYT/void-packages fix-and-update-c-ares
https://github.com/void-linux/void-packages/pull/50739

c-ares: Update to 1.30.0, apply new download link
c-ares' new version is 1.30.0, and the current 1.29.0 doesn't build due to a now-missing download link. Fix both problems at once to get the package building again.

I've tested these changes on several architectures for glibc and musl.

#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - i686
  - i686-musl
  - mips-musl
  - ppc
  - armv6l-musl
  - armv6l
  - aarch64-musl
  - aarch64

A patch file from https://github.com/void-linux/void-packages/pull/50739.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix-and-update-c-ares-50739.patch --]
[-- Type: text/x-diff, Size: 1349 bytes --]

From cb1b3e14e6d9a140f1107a4b6936641461d25b5d Mon Sep 17 00:00:00 2001
From: techflashYT <officialTechflashYT@gmail.com>
Date: Fri, 7 Jun 2024 15:19:52 -0700
Subject: [PATCH] c-ares: Update to 1.30.0, apply new download link

c-ares' new version is 1.30.0, and the current 1.29.0 doesn't build due to a missing download link.
Fix both problems at once to get the package building again.
---
 srcpkgs/c-ares/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/c-ares/template b/srcpkgs/c-ares/template
index 32a0b0420f1292..9cc99625d14d09 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.29.0
+version=1.30.0
 revision=1
 build_style=gnu-configure
 checkdepends="iana-etc"
@@ -9,8 +9,8 @@ maintainer="Duncaen <duncaen@voidlinux.org>"
 license="MIT"
 homepage="https://c-ares.haxx.se/"
 changelog="https://c-ares.haxx.se/changelog.html"
-distfiles="https://c-ares.haxx.se/download/c-ares-${version}.tar.gz"
-checksum=0b89fa425b825c4c7bc708494f374ae69340e4d1fdc64523bdbb2750bfc02ea7
+distfiles="https://github.com/c-ares/c-ares/releases/download/v${version}/c-ares-${version}.tar.gz"
+checksum=4fea312112021bcef081203b1ea020109842feb58cd8a36a3d3f7e0d8bc1138c
 make_check=ci-skip # segfaults only on CI
 
 post_install() {

             reply	other threads:[~2024-06-07 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07 22:27 techflashYT [this message]
2024-06-08  0:02 ` techflashYT
2024-06-09 17:08 ` [PR REVIEW] " classabbyamp
2024-06-09 17:09 ` classabbyamp
2024-06-10 11:32 ` [PR PATCH] [Closed]: " Duncaen

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-50739@inbox.vuxu.org \
    --to=techflashyt@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).