From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: glib: update to 2.70.0, patch out warning about deprecated scheme paths
Date: Wed, 29 Sep 2021 22:34:15 +0200 [thread overview]
Message-ID: <20210929203415.lfqNIZyyDVzEqyIEQijGvtH2oNnz5uVqMznEKkQ60Jk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33017@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
There's a merged pull request on the void-packages repository
glib: update to 2.70.0, patch out warning about deprecated scheme paths
https://github.com/void-linux/void-packages/pull/33017
Description:
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
Adds a patch to remove the annoying warnings about deprecated paths on each glib-compile-schemas call (for example xbps updates). Other distributions also have this patch.
This PR needs a bit more testing especially on musl before it can be merged.
prev parent reply other threads:[~2021-09-29 20:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 22:37 [PR PATCH] " paper42
2021-09-18 22:37 ` [PR PATCH] [Updated] " paper42
2021-09-20 10:54 ` paper42
2021-09-20 16:04 ` paper42
2021-09-20 16:04 ` paper42
2021-09-27 20:18 ` [PR PATCH] [Updated] " paper42
2021-09-27 20:46 ` paper42
2021-09-27 20:50 ` paper42
2021-09-27 22:10 ` [PR PATCH] [Updated] " paper42
2021-09-29 7:47 ` paper42
2021-09-29 20:34 ` 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=20210929203415.lfqNIZyyDVzEqyIEQijGvtH2oNnz5uVqMznEKkQ60Jk@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).