Package: gcr / 3.41.2-5
Metadata
| Package | Version | Patches format |
|---|---|---|
| gcr | 3.41.2-5 | 3.0 (quilt) |
Patch series
view the series file| Patch | File delta | Description |
|---|---|---|
| systemd Start with graphical session instead of default.patch | (download) |
gcr/gcr-ssh-agent.service.in |
2 1 + 1 - 0 ! |
systemd: start with graphical-session instead of default https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/91 |
| Fix FTBFS on x32.patch | (download) |
egg/egg-asn1x.c |
6 3 + 3 - 0 ! |
fix ftbfs on x32 This patch is inspired from Simon proposal on the upstream bug: https://gitlab.gnome.org/GNOME/gcr/-/issues/45 |
| gck disable parallel tests using gck mock module.patch | (download) |
gck/meson.build |
1 1 + 0 - 0 ! |
gck: disable parallel tests using gck-mock module Our tests are regularly failing when run in parallel, since the tests are all loading the gck-mock module and changing objects there, racing with each other. Explicitly prevent this by marking the tests as not parallel in meson. (cherry picked from commit 9aeff4c3851b35338a812ebc05a4c46d486e1fa5) |
| disable test which segfaults.patch | (download) |
gck/test-gck-object.c |
2 1 + 1 - 0 ! |
disable test which segfaults on some systems On some systems, the test below aborts with segfault, like this: 18/43 gcr:gck / object FAIL 0.02s killed by signal 11 SIGSEGV This apparently happens on single-CPU systems with very high probability, but it has been also observed on machines with 2 CPUs. Bug-Debian: https://bugs.debian.org/1057562 |
1
