Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: apr: update to 1.7.4
Date: Sat, 05 Aug 2023 03:48:17 +0200	[thread overview]
Message-ID: <20230805014817.ei9sBP8aiPp85C7sFkGx-ybNLsW_q3Cz2I-Kr26On34@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42972@inbox.vuxu.org>

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

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

apr: update to 1.7.4
https://github.com/void-linux/void-packages/pull/42972

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

<!--
#### 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, x86\_64-glibc
- I built this PR locally for these architectures:
  - aarch64

This also addresses #42441
- [x] apr

### Tests to fix

- [x]  `testatomic`: consistency failure on atomic (i686)
- [x]  `testsockets`: Socket bind failure (x86\_64, i686, x86\_64-musl)
- [x]  `testdso` failure (x86\_64-musl)

      parent reply	other threads:[~2023-08-05  1:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24  6:58 [PR PATCH] apr: update to 1.7.2 gmbeard
2023-03-24  7:45 ` [PR PATCH] [Updated] " gmbeard
2023-03-24  8:28 ` gmbeard
2023-03-24 17:49 ` gmbeard
2023-03-25  8:55 ` gmbeard
2023-03-25  8:58 ` gmbeard
2023-03-25 11:34 ` gmbeard
2023-03-25 12:00 ` gmbeard
2023-03-28 19:37 ` gmbeard
2023-03-28 20:08 ` gmbeard
2023-04-05  4:29 ` gmbeard
2023-04-19 19:46 ` [PR REVIEW] " paper42
2023-04-19 19:46 ` paper42
2023-04-19 19:54 ` nekopsykose
2023-04-21  6:21 ` [PR PATCH] [Updated] " gmbeard
2023-04-21  6:23 ` [PR REVIEW] apr: update to 1.7.4 gmbeard
2023-04-21  6:26 ` gmbeard
2023-04-21  6:28 ` gmbeard
2023-04-21  6:44 ` [PR REVIEW] " gmbeard
2023-04-21  6:45 ` gmbeard
2023-07-21  1:55 ` github-actions
2023-08-05  1:48 ` github-actions [this message]

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=20230805014817.ei9sBP8aiPp85C7sFkGx-ybNLsW_q3Cz2I-Kr26On34@z \
    --to=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).