Bug 1319152 - incorrect use of Requires(pre)?
Summary: incorrect use of Requires(pre)?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: cyrus-sasl
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-18 15:56 UTC by Honza Silhan
Modified: 2016-09-13 10:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-01 07:07:59 UTC
Type: ---


Attachments (Terms of Use)

Description Honza Silhan 2016-03-18 15:56:11 UTC
We've identified your package for having `Requires(pre)` RPM flag without `Requires` [1]. `Requires(pre)` rpm tag could be interpreted wrongly, so to prevent any harm to Fedora users I am notifying you about this fact.

Any package that is specified in `Requires(pre)` could be freely removed. Citing from RPM pages:
```
If there are no other dependencies on the package providing /usr/sbin/useradd, that package is permitted to be removed from the system after installation(!)
``` [2]

If you really rely on dependency just during the installation process and your package don't necessary require the dependency for the proper run of your application then ignore this bug report and close it as NOTABUG. Otherwise add to your spec file additional `Requires` for the dependency, please.


[1] paste.fedoraproject.org/341611/82208431
[2] http://www.rpm.org/wiki/PackagerDocs/MoreOnDependencies

Comment 1 Petr Lautrbach 2016-03-18 20:42:02 UTC
SRPM:  cyrus-sasl-2.1.26-26.2.fc24.src.rpm       RPM:  cyrus-sasl.x86_64         Require(pre):  /sbin/service

What does it mean? 

$ grep 'Requires(pre)' cyrus-sasl.spec 
Requires(pre): /usr/sbin/useradd /usr/sbin/groupadd systemd-units

Is this wrong? Why?

Comment 2 Honza Silhan 2016-09-13 10:27:49 UTC
Requires(pre) for `/usr/abin/useradd` is fine. I am sorry for late response.


Note You need to log in before you can comment on or make changes to this bug.