Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: c-ares: update to 1.30.0
Date: Thu, 13 Jun 2024 22:26:30 +0200	[thread overview]
Message-ID: <20240613202630.3CBEB22316@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50821@inbox.vuxu.org>

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

There's a closed pull request on the void-packages repository

c-ares: update to 1.30.0
https://github.com/void-linux/void-packages/pull/50821

Description:
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.

I've also fixed the problems that were brought up in my previous PR (#50739) for this change (changed the commit message, updated the homepage link).  Thanks for the pointers, that was my first attempt at submitting changes to upstream Void before, hopefully this is better.

#### 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):
  - (cross) i686
  - (cross) i686-musl
  - (cross) mips-musl
  - (cross) ppc
  - ppc
  - (cross) armv6l-musl
  - (cross) armv6l
  - (cross) aarch64-musl
  - (cross) aarch64

  parent reply	other threads:[~2024-06-13 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 20:24 [PR PATCH] " techflashYT
2024-06-13 20:26 ` classabbyamp
2024-06-13 20:26 ` classabbyamp [this message]
2024-06-13 20:30 ` techflashYT

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=20240613202630.3CBEB22316@inbox.vuxu.org \
    --to=classabbyamp@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).