From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libgnome-keyring is deprecated
Date: Thu, 28 Apr 2022 12:36:54 +0200 [thread overview]
Message-ID: <20220428103654.7bBMC5XZ51jzLjq3HiPYuEno2CLNOn73tup91K6uv0o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26333@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/26333#issuecomment-1112049558
Comment:
* nothing links against libgnome-keyring anymore
* mate-power-manager doesn't use libgnome-keyring in 1.26.0 which we have packaged, so the build dep should be removed
* cinnamon doesn't use gnome-keyring since 3.6, so the build dep can also be removed: https://github.com/linuxmint/cinnamon/commit/f912db7f8e8ad3ab73219af18693d07f4c0f6dd1
* libgda 5.1.1:
> - Use Libsecret instead of Libgnome-keyring if available
* libpurple-steam doesn't link against libgnome-keyring, do we have the part disabled and the build dep is unnecessary? We have 1.6.1 packaged, 1.7+ can use libsecret:
> Switch to use libsecret instead of gnome-keyring for Telepathy-Haze users
I didn't check other packages yet.
next prev parent reply other threads:[~2022-04-28 10:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 22:52 [ISSUE] " yopito
2020-11-13 4:00 ` CameronNemo
2020-11-13 4:02 ` CameronNemo
2020-11-13 4:05 ` CameronNemo
2020-11-13 4:05 ` CameronNemo
2020-11-13 4:11 ` CameronNemo
2020-11-13 4:11 ` CameronNemo
2020-11-13 4:15 ` CameronNemo
2020-11-14 11:18 ` sgn
2022-04-27 2:13 ` github-actions
2022-04-28 10:36 ` paper42 [this message]
2022-07-28 2:15 ` github-actions
2022-11-05 2:13 ` github-actions
2024-04-18 7:57 ` [ISSUE] [CLOSED] " sgn
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=20220428103654.7bBMC5XZ51jzLjq3HiPYuEno2CLNOn73tup91K6uv0o@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).