desktop: Remove obsolete Bugzilla entries

See merge request !55

The `X-GNOME-Bugzilla-*` entries were for use by bug-buddy, a GNOME 2
technology that's been gone for over a decade. These entries are
obsolete and can be removed from the desktop files.

The desktop files then have no variables so do not need to be
configured. They are renamed from `*.in.in` to `*.in` to reflect that
and build files are updated for this change.

Sveinn í Felli authored Sep 05, 2022 and Administrator committed Sep 05, 2022

(cherry picked from commit bb785db0)

Sveinn í Felli authored Sep 05, 2022 and Administrator committed Sep 05, 2022

(cherry picked from commit c2ce16ef)

Sveinn í Felli authored Sep 05, 2022 and Administrator committed Sep 05, 2022

(cherry picked from commit 43589601)

configure.ac: Stop using deprecated pkgconfig variable in p11-kit

See merge request !54

p11_system_config_modules has been deprecated for a long time, in
favor of p11_module_configs.

Signed-off-by: Daiki Ueno <dueno@src.gnome.org>

Matt Turner authored May 22, 2022 and Niels De Graef committed May 31, 2022

Using strncpy produces the following warning, which indicates that the
destination string could be left unterminated.

  CC       daemon/control/gkd-control-server.lo
  CCLD     libgkd-control.la
  CC       pkcs11/rpc-layer/libgkm_rpc_layer_la-gkm-rpc-dispatch.lo
In file included from /usr/include/string.h:519,
                 from /usr/include/glib-2.0/glib/galloca.h:33,
                 from /usr/include/glib-2.0/glib.h:30,
                 from ./egg/egg-error.h:24,
                 from pkcs11/rpc-layer/gkm-rpc-dispatch.c:31:
In function ‘strncpy’,
    inlined from ‘gkm_rpc_layer_startup’ at pkcs11/rpc-layer/gkm-rpc-dispatch.c:2382:2:
/usr/include/bits/string_fortified.h:95:10: warning: ‘__builtin_strncpy’ specified bound 108 equals destination size [-Wstringop-truncation]
   95 |   return __builtin___strncpy_chk (__dest, __src, __len,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   96 |                                   __gl...

Pawan Chitrakar authored May 24, 2022 and Administrator committed May 24, 2022

(cherry picked from commit 8e43ecc3)

Otherwise they don't get included into the tarball and autotools screams
at us.

Niels De Graef authored May 13, 2022 and Niels De Graef committed May 21, 2022

Fixes: #107

When enabling fatal warnings (like in our CI), the
`-Werror=format-truncation=` flag is complaining about us using
`snprintf()` in a way that can theoretically truncate its arguments,
even though this will not happen in practice, unless people are still
running gnome-keyring in the year 100000.

Solve the warning by doing a dumb check that aborts if `snprintf`
returns an error

Stef has been inactive on GNOME development for quite a while now, and
the email address listed in the doap is no longer in use even, so remove
him.

That being said, I'm probably the closest to a co-maintainer with Daiki
as I'm maintaining libsecret anyway, so I get to deal with gnome-keyring
whether I like it or not.

Simon McVittie authored Sep 26, 2021 and Niels De Graef committed May 21, 2022

As discussed in <glib#600>,
the volatile qualifier rarely has the semantics that are desired in C/C++.
With recent gcc versions, combining pointers to volatile-qualified types
with the __atomic_foo() family of builtins causes compiler warnings.

http://c.isvolatileusefulwiththreads.com/

 has some other useful
references.

Signed-off-by: Simon McVittie <smcv@debian.org>

Quentin PAGÈS authored Aug 11, 2021 and Administrator committed Aug 11, 2021

(cherry picked from commit 08695936)

readme: Mention libsecret instead of deprecated libgnome-keyring

See merge request !37

daemon: Make it systemd-activatable through the control socket

See merge request !35

Daiki Ueno authored Feb 12, 2021 and Daiki Ueno committed Mar 26, 2021

This enables gnome-keyring-daemon to be launched through the systemd
socket activation mechanism, rather than through pam_gnome_keyring.so.

Fix CI runs

See merge request !36

This ports the commits 572a35626625d0a2cd0be54124e402d6bcb43898 and
5b69e07be75ee5f43df0d734eaee007033a33647 from gcr, by Niels De Graef.

See
https://mail.gnome.org/archives/desktop-devel-list/2020-February/msg00055.html
for more context.

Also only deploy coverage information when built on the master branch.