Package: dbus / 1.12.12-1

Metadata

Package Version Patches format
dbus 1.12.12-1 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
dbus daemon test Don t test fd limits if in an unprivileg.patch | (download)

test/dbus-daemon.c | 30 28 + 2 - 0 !
1 file changed, 28 insertions(+), 2 deletions(-)

 dbus-daemon test: don't test fd limits if in an unprivileged
 container

In an unprivileged container, uid 0 doesn't have CAP_SYS_RESOURCE, so
we can't expect the dbus-daemon to be able to escalate its fd limit.

This can be reproduced using bubblewrap:

    sudo bwrap \
        --cap-drop CAP_SYS_RESOURCE \
        --ro-bind / / \
        --dev /dev \
    env \
        DBUS_TEST_DAEMON=.../bus/dbus-daemon \
        DBUS_TEST_DATA=.../test/data \
    .../test/test-dbus-daemon \
        -p /fd-limit \
        --verbose

Bug-Debian: https://bugs.debian.org/908092
debian/session.conf system.conf include legacy files as .dpkg ba.patch | (download)

bus/session.conf.in | 5 3 + 2 - 0 !
bus/system.conf.in | 5 3 + 2 - 0 !
2 files changed, 6 insertions(+), 4 deletions(-)

 session.conf, system.conf: include legacy files as *.dpkg-bak

The Debian maintainer scripts used while upgrading from jessie to stretch
delete the legacy files if they have not been modified, or move them to
*.dpkg-bak if they were modified. This allows the plain session.conf and
system.conf names to be replaced with symbolic links, which is enough
to let the old dbus-daemon reload its configuration during upgrades in
most cases.

This patch also avoids circular inclusion of the configuration file
via those symlinks before they are cleaned up by dbus.postinst.

This change can be removed after Debian 10 is released.

debian/tests Multiply timeouts by 20 on riscv64.patch | (download)

test/test-utils-glib.c | 7 7 + 0 - 0 !
1 file changed, 7 insertions(+)

 tests: multiply timeouts by 20 on riscv64

Real riscv64 hardware has performance comparable to Debian's slower
buildds such as arm and mips, but the port is currently being
bootstrapped using qemu-system-riscv64, and that's too slow to run some
of our tests successfully. For each test that "should" take no more than
a minute on real hardware, allow 20 minutes instead.