Changeset 8169f4e


Ignore:
Timestamp:
07/31/2020 10:12:58 AM (15 months ago)
Author:
Pierre Labastie <pieere@…>
Branches:
10.0, 10.1, 11.0, ken/refactor-virt, lazarus, qt5new, trunk, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
Children:
ecac868
Parents:
3cdae40
Message:

Add a sed to sysv gsd, so that more tests pass

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23440 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • gnome/platform/gnome-settings-daemon.xml

    r3cdae40 r8169f4e  
    134134    <title>Installation of GNOME Settings Daemon</title>
    135135
     136    <para revision="sysv">
     137      First fix libelogind detection for tests:
     138    </para>
     139
     140<screen revision="sysv"><userinput>sed -e 's/libsystemd/libelogind/' \
     141    -i plugins/power/test.py</userinput></screen>
     142
    136143    <para>
    137144      Install <application>GNOME Settings Daemon</application> by running the
     
    151158ninja</userinput></screen>
    152159
    153     <!-- For some reason, on elogind, all tests passed. 8 failed on systemd.
    154          It could be kernel configuration, or any other package change.
    155          umockdev might be needed, but it works fine without it on elogind. -->
     160    <!-- [renodr, June 29th, 2019]: for some reason, on elogind, all tests
     161         passed. 8 failed on systemd. It could be kernel configuration, or
     162         any other package change. umockdev might be needed, but it works
     163         fine without it on elogind.
     164         [pierre, July 31st, 2020]: only one test passed on elogind. I
     165         have umockdev, but it does not look like it is used. Adding the
     166         sed allows 9 tests out of 10 to pass. -->
    156167    <para>
    157168      To check the results, execute: <command>ninja test</command>. Note that
    158169      you must have <application>python-dbusmock</application> installed in
    159       order for the tests to complete successfully. Some tests in the "power"
    160       testsuite may fail depending on the init system in use.
     170      order for the tests to complete successfully. Some tests
     171      may fail depending on the init system in use.
    161172    </para>
    162173
Note: See TracChangeset for help on using the changeset viewer.