Bug 2041056

Summary:	postfix package lacks some README_FILES (documentation)
Product:	[Fedora] Fedora	Reporter:	Matthias Andree <matthias.andree>
Component:	postfix	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	35	CC:	jskarvad, olysonek-foss, pgnet.dev
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-21 20:19:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.