Bug 1671374

Summary: Optimize iscsi-initiator-utils RPM spec for systemd requirements when installing it in containers
Product: [Fedora] Fedora Reporter: Bogdan Dobrelya <bdobreli>
Component: iscsi-initiator-utilsAssignee: Bogdan Dobrelya <bdobreli>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: agrover, cleech, mchristi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1671362 Environment:
Last Closed: 2019-02-11 13:15:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bogdan Dobrelya 2019-01-31 13:55:07 UTC
Description of problem:

When installing iscsi-initiator-utils into a container image, it is preferable to use the systemd_ordering macro.

According to https://fedoraproject.org/wiki/Packaging:Scriptlets:
If a package is suitable for installation without systemd (in a
container image, for example) and does not require any of the
systemd mechanisms such as tmpfiles.d, then the systemd_ordering macro
MAY be used instead of the systemd_requires macro. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Bogdan Dobrelya 2019-02-05 16:30:32 UTC
Hello.
Any updates for this please?
Is it OK, or shall I resubmit it by some other upstream loc, like  https://github.com/rpm-software-management or something?

Comment 3 Bogdan Dobrelya 2019-02-11 13:15:00 UTC
Closing because of https://github.com/rpm-software-management/dnf/pull/1315#issuecomment-462321911