| Summary: | systemd should not enable by default ystemd-repart or is should require systemd-home package | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | GG HH <boulshet> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Normal | CC: | boulshet, tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | systemd-245-2.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
GG HH
2020-03-07 22:21:52 CET
CC:
(none) =>
boulshet Yeah, there is two bugs here, is should not be enabled by default, and systemd-repart binary should be in main systemd package. I pushed a new mageia-release that disables it by default, and will fix up the systemd package CC:
(none) =>
tmb and systemd fixed with systemd-245-3.mga8 currently building thanks for the report Status:
NEW =>
RESOLVED |
Description of problem: 245-2 enables "homed support as separate package to be able to experiment with it". It enables systemd-repart.service which relies on /usr/bin/systemd-repart systemd-repart is expected to be provided by systemd-homed but thi package is not required by systemd Version-Release number of selected component (if applicable): 245-2 How reproducible: 1/ upgrade to current systemd 2/ systemctl status systemd-repart.service ● systemd-repart.service - Repartition Root Disk Loaded: loaded (/usr/lib/systemd/system/systemd-repart.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2020-03-07 20:10:51 CET; 2h 5min ago Docs: man:systemd-repart.service(8) Process: 11317 ExecStart=/usr/bin/systemd-repart --dry-run=no (code=exited, status=203/EXEC) Main PID: 11317 (code=exited, status=203/EXEC) mars 07 20:10:51 uranus systemd[1]: Starting Repartition Root Disk... mars 07 20:10:51 uranus systemd[11317]: systemd-repart.service: Failed to execute command: No such file or directory mars 07 20:10:51 uranus systemd[11317]: systemd-repart.service: Failed at step EXEC spawning /usr/bin/systemd-repart: No such file or directory mars 07 20:10:51 uranus systemd[1]: systemd-repart.service: Main process exited, code=exited, status=203/EXEC mars 07 20:10:51 uranus systemd[1]: systemd-repart.service: Failed with result 'exit-code'. mars 07 20:10:51 uranus systemd[1]: Failed to start Repartition Root Disk. i can't see any side effect beside a bad systemd status. Hence the severity i propose. regards