Overview
Request 445689 accepted
- Move the procps BuildRequires into the systemd conditional block.
procps is only used during the test suite (some tests run 'ps';
even if we ignore a failure for this in util-linux, we catch the
same in util-linux-systemd, which is sufficient.
- Move the procps BuildRequires into the systemd conditional block.
procps is only used during the test suite (some tests run 'ps';
even if we ignore a failure for this in util-linux, we catch the
same in util-linux-systemd, which is sufficient.
- Move the procps BuildRequires into the systemd conditional block.
procps is only used during the test suite (some tests run 'ps';
even if we ignore a failure for this in util-linux, we catch the
same in util-linux-systemd, which is sufficient.
- Created by dimstar
- In state accepted
- 4 package maintainers
Request History
dimstar created request
- Move the procps BuildRequires into the systemd conditional block.
procps is only used during the test suite (some tests run 'ps';
even if we ignore a failure for this in util-linux, we catch the
same in util-linux-systemd, which is sufficient.
- Move the procps BuildRequires into the systemd conditional block.
procps is only used during the test suite (some tests run 'ps';
even if we ignore a failure for this in util-linux, we catch the
same in util-linux-systemd, which is sufficient.
- Move the procps BuildRequires into the systemd conditional block.
procps is only used during the test suite (some tests run 'ps';
even if we ignore a failure for this in util-linux, we catch the
same in util-linux-systemd, which is sufficient.
dirkmueller accepted request
Sorry this makes no sense.
The test where ps is used does not run in util-linux-systemd. So now we require psproc for a package which does not need it.
Even if the test would run in util-linux-systemd then it would still test a binary which we build aready in another package.