From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: gnome-keyring: fix libcap-ng usage
Date: Thu, 17 Dec 2020 14:50:02 +0100 [thread overview]
Message-ID: <20201217135002.hbtJ5AnQz6fkEcwva3jL9B4cAgU4OkZ0kcX6h_C1wp4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27220@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 335 bytes --]
There's a closed pull request on the void-packages repository
gnome-keyring: fix libcap-ng usage
https://github.com/void-linux/void-packages/pull/27220
Description:
The new libcap-ng 0.8.2 recently committed to master breaks this package. I pulled the commit patch from the project repo and bumped the revision.
Refer to:
#27216
next prev parent reply other threads:[~2020-12-17 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 7:12 [PR PATCH] " lane-brain
2020-12-17 13:50 ` ericonr [this message]
2020-12-17 13:50 ` ericonr
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=20201217135002.hbtJ5AnQz6fkEcwva3jL9B4cAgU4OkZ0kcX6h_C1wp4@z \
--to=ericonr@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).