Package: udisks2 / 2.8.1-4

Metadata

Package Version Patches format
udisks2 2.8.1-4 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
Move D Bus policy file to usr share dbus 1 system.d.patch | (download)

data/Makefile.am | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 move d-bus policy file to /usr/share/dbus-1/system.d/

This is supported since dbus 1.9.18.
The old location in /etc/dbus-1/system.d/ has been deprecated.

https://lists.freedesktop.org/archives/dbus/2015-July/016746.html

https://github.com/storaged-project/udisks/pull/597

integration test Sync after creating our fake devices.patch | (download)

src/tests/integration-test | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 integration-test: sync after creating our fake devices

On Ubuntu ppc64el, the integration tests are almost always failing like
this:

  Traceback (most recent call last):
    File "src/tests/integration-test", line 1788, in test_md_raid_methods
      self.assertNotProperty(block_interface, 'mdraid-member', '/')
    File "src/tests/integration-test", line 542, in assertNotProperty
      self.assertNotEqual(obj.get_property(name), value)
  AssertionError: '/' == '/'

Upon investigation, it turns out that this is due to a race condition in
the tests - when we use targetcli to create the devices, they are not
seen by udev immediately, and consequently are not visible to udisks
either. If an array is created in this period, this causes the
MDRaidMember property to not be set. We can fix this problem by calling
`sync()` before running any tests, to ensure that our devices are fully
visible - as they would be if they were real devices.