| Summary: | split systemd-analyze to a subpackage with proper dependencies | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | d. johnson <drjohnson1> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | atkac, bochecha, dmach, harald, jistone, johannbg, karsten, kay, lpoetter, metherid, mschmidt, notting, oliver.henshaw, plautrba |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | systemd-38-5.fc17 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-22 21:29:38 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Having the systemd package depend on dbus-python and pycairo is not a good idea. We could split systemd-analyze in a subpackage though. This is still an issue with systemd-33 from Fedora 16 (not sure it is appropriate for me to change the Fedora version for this bug). Would a patch to separate systemd-analyze in a separate package help? *** Bug 737940 has been marked as a duplicate of this bug. *** *** Bug 739913 has been marked as a duplicate of this bug. *** Moving to F16. Is anyone going to fix it or should I ask one of the proven packagers to do so? I can attach a patch if needed... Last time we discussed this with Lennart the plan was to create a separate source tree (and a source package) with systemd utilities. systemd-analyze would be moved there. It may have been Kay's idea. Kay, what is the status on this? (In reply to comment #6) > Kay, what is the status on this? We possibly like the move out systemadm to its own source package, and move gnome-password agent to gnome-setting-daemon, which lets us get rid of vala and gtk dependencies. I personally don't mind having these debugging/unimportant tools just fail if python or python libs aren't installed. It all sounds more like using a Recommends:, but we don't have that in rpm. We can not pull-in python from the init system. But if the current packaging is considered bad practice, we should probably move it to a sub-rpm. (In reply to comment #7) > We can not pull-in python from the init system. But if the current packaging > is considered bad practice, we should probably move it to a sub-rpm. It already pulls in python, thanks to the #!/usr/bin/python. Pulling in dbus-python too wouldn't be so bad IMO, but pycairo does probably pull in too much. I'd say moving to a subpackage is best. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Fixed in Rawhide in systemd-38-5.fc17. At this point I do not plan to do the split on the f16 branch. |
Description of problem: systemd-analyze fails to run due to missing deps. Version-Release number of selected component (if applicable): systemd-26-2.fc15.x86_64 dbus-python-0.83.0-8.fc15.x86_64 pycairo-1.8.8-2.fc14.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install minimium f15. 2. Boot. 3. Run "systemd-analyze plot > 20110604.svg" Actual results: # systemd-analyze plot > 20110604-d630.svg Traceback (most recent call last): File "/usr/bin/systemd-analyze", line 3, in <module> import dbus, sys ImportError: No module named dbus # yum install dbus-python # systemd-analyze plot > 20110604-d630.svg Traceback (most recent call last): File "/usr/bin/systemd-analyze", line 113, in <module> import cairo ImportError: No module named cairo # yum install pycairo # systemd-analyze plot > 20110604-d630.svg # # ls -l 20110604-d630.svg -rw-r--r--. 1 root root 193972 Jun 4 13:17 20110604-d630.svg Expected results: If systemd-analyze is installed, it should have all required deps installed along with it. Additional info: Adding 'Requires: dbus-python pycairo' to the spec would remedy this. If there are specific version requirements, I do not know what they would be.