Bug 690216

Summary: 3.5.8 update has corrupted smb.conf manpage
Product: [Fedora] Fedora Reporter: Guenther Deschner <gdeschner>
Component: sambaAssignee: Guenther Deschner <gdeschner>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 13CC: gdeschner, jlayton, j, ssorce
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: samba-3.5.8-75.fc13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 689605 Environment:
Last Closed: 2011-05-19 04:31:39 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:
Bug Depends On: 689605    
Bug Blocks:    

Description Guenther Deschner 2011-03-23 16:01:58 UTC
+++ This bug was initially created as a clone of Bug #689605 +++

The samba 3.5.7 manpage for smb.conf had a proper explanation of the possible parameters.  After the 3.5.8 update, I see the following:

       locally, i.e. directly accessing the database file, circumventing the server.

EXPLANATION OF EACH PARAMETER
       <xi:include></xi:include>.SH "WARNINGS"

       Although the configuration file permits service names to contain spaces, your client software may not. Spaces will be ignored in comparisons


And the actual parameter descriptions are missing.

--- Additional comment from updates on 2011-03-23 12:00:27 EDT ---

samba-3.5.8-75.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/samba-3.5.8-75.fc14

Comment 1 Fedora Update System 2011-03-23 16:27:24 UTC
samba-3.5.8-75.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/samba-3.5.8-75.fc13

Comment 2 Fedora Update System 2011-05-19 04:31:34 UTC
samba-3.5.8-75.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.