Bug 1671374 - Optimize iscsi-initiator-utils RPM spec for systemd requirements when installing it in containers
Summary: Optimize iscsi-initiator-utils RPM spec for systemd requirements when install...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: iscsi-initiator-utils
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bogdan Dobrelya
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-31 13:55 UTC by Bogdan Dobrelya
Modified: 2019-02-11 13:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of: 1671362
Environment:
Last Closed: 2019-02-11 13:15:00 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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 1 Bogdan Dobrelya 2019-01-31 14:15:16 UTC 
A PR against master https://src.fedoraproject.org/rpms/iscsi-initiator-utils/pull-request/4

plus f29 backport https://src.fedoraproject.org/rpms/iscsi-initiator-utils/pull-request/5
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
Note You need to log in before you can comment on or make changes to this bug.