Bug 2041056 - postfix package lacks some README_FILES (documentation)
Summary: postfix package lacks some README_FILES (documentation)
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: postfix
Version: 35
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-15 17:24 UTC by Matthias Andree
Modified: 2022-01-21 20:19 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-01-21 20:19:50 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2012600 1 unspecified CLOSED five README_FILES are missing from /usr/share/doc/postfix/README_FILES 2022-06-07 22:23:59 UTC

Description Matthias Andree 2022-01-15 17:24:14 UTC 
Description of problem:
postfix-3.6.2-5.fc35.x86_64 lacks, for instance, the MAILLOG_README file. It is referenced by the postfix(8) manual page (especially for in-container usage purposes) and included in the upstream tarball.

Other README files were not checked, I would ask to align the %files section of the .spec with the upstream README_FILES directory.

Version-Release number of selected component (if applicable):
postfix-3.6.2-5.fc35.x86_64

How reproducible:
always

Steps to Reproduce:
rpm -ql postfix | grep MAILLOG

Actual results:
empty response

Expected results:
/usr/share/doc/postfix/README_FILES/ gets the complete documentation file set.

Additional info:
-
Comment 1 Jaroslav Škarvada 2022-01-20 22:55:31 UTC 
It seems to be upstream problem:
$ grep MAILLOG conf/postfix-files

But for e.g. MAILDROP:
$ grep MAILDROP conf/postfix-files
$readme_directory/MAILDROP_README:f:root:-:644
$html_directory/MAILDROP_README.html:f:root:-:644

It seems the following files are not included:
BDAT_README
MAILLOG_README
POSTSCREEN_3_5_README
SMTPUTF8_README
Comment 2 Jaroslav Škarvada 2022-01-20 23:00:19 UTC 
Forwarded upstream.
Comment 3 Jaroslav Škarvada 2022-01-21 20:19:50 UTC 
The problem was confirmed by upstream and it should be fixed in the next upstream Postfix release. I am closing this with the resolution upstream.
Note You need to log in before you can comment on or make changes to this bug.