From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: mit-krb5: update to 1.20.1
Date: Wed, 08 Mar 2023 19:09:28 +0100 [thread overview]
Message-ID: <20230308180928.QbSNx8Trv8hikOcuk17EaGWusapxdbZrMaFsXNgzhhU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42633@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 666 bytes --]
There's a merged pull request on the void-packages repository
mit-krb5: update to 1.20.1
https://github.com/void-linux/void-packages/pull/42633
Description:
A rebuild triggered by #41948 had some errors in the test suite.
- remove patch for libressl
- follow distfiles convention.
#### 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 my native architecture, (x86_64-musl)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
- i686
prev parent reply other threads:[~2023-03-08 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 22:16 [PR PATCH] " klarasm
2023-03-08 18:09 ` paper42 [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=20230308180928.QbSNx8Trv8hikOcuk17EaGWusapxdbZrMaFsXNgzhhU@z \
--to=paper42@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).