Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#64283 - Change dependencies on gnome-keyring
Attached to Project:
Community Packages
Opened by Bruno Pagani (ArchangeGabriel) - Sunday, 27 October 2019, 10:32 GMT
Last edited by Antonio Rojas (arojas) - Monday, 28 October 2019, 11:24 GMT
Opened by Bruno Pagani (ArchangeGabriel) - Sunday, 27 October 2019, 10:32 GMT
Last edited by Antonio Rojas (arojas) - Monday, 28 October 2019, 11:24 GMT
|
DetailsWe have some packages with dependency on gnome-keyring, like Geary, that actually do not require strictly gnome-keyring but a service implementing org.freedesktop.secrets, which we now have at least two of them (gnome-keyring and keepassxc).
Maybe we should create a virtual provides `org.freedesktop.secrets` and add it to both keepassxc and gnome-keyring, and then switch all dependencies on gnome-keyring to this virtual package. Any opinion? Should I start a TODO for this? |
This task depends upon
But if you prefer 'secrets-service', fine. I’ll push keepassxc again.
@heftig: The advantage of the dot name is to avoid any potential naming conflict for the foreseeable future.
Note that xdg-desktop-portal-gtk will gain a hard dependency on gnome-keyring in the future, as it will be the only implementor of org.freedesktop.portal.Secret.