Bug 14522 - default of "spoolss: architecture" is wrong documented
Summary: default of "spoolss: architecture" is wrong documented
Status: RESOLVED FIXED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 4.12.6
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Karolin Seeger
QA Contact: Samba Documentation QA Contact~
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-06 18:23 UTC by Björn Jacke
Modified: 2020-11-05 10:01 UTC (History)
1 user (show)

See Also:

Attachments
cherry-picked patch for all release branches (1.35 KB, patch)
2020-10-07 05:42 UTC, Björn Jacke 		kseeger: review+
Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Björn Jacke 2020-10-06 18:23:39 UTC 
since 92fc6a6c254703b771dec0b56b598c2684b4278a in 2016 "spoolss: architecture" is "Windows x64" by default. The man page still says Windows NT x86.
Comment 1 Samba QA Contact 2020-10-06 23:07:05 UTC 
This bug was referenced in samba master:

c587685dde2448d1f68ada47ce5ad42b02a118ce
Comment 2 Björn Jacke 2020-10-07 05:42:46 UTC 
Created attachment 16274 [details]
cherry-picked patch for all release branches

Karo, can you review+ the backport patch and add it to the release branches, please?
Comment 3 Karolin Seeger 2020-10-26 11:31:33 UTC 
(In reply to Björn Jacke from comment #2)
Pushed to autobuild-v4-{13,12}-test.
Comment 4 Samba QA Contact 2020-10-26 14:43:30 UTC 
This bug was referenced in samba v4-12-test:

ae4d3932cfb107725ea052f9ac0dca8c9a52b162
Comment 5 Samba QA Contact 2020-10-27 10:51:47 UTC 
This bug was referenced in samba v4-13-test:

ff781ba4682ded42142ace6e8634fff57788819e
Comment 6 Karolin Seeger 2020-10-30 12:11:04 UTC 
Closing out bug report.

Thanks!
Comment 7 Samba QA Contact 2020-11-03 12:37:07 UTC 
This bug was referenced in samba v4-13-stable (Release samba-4.13.2):

ff781ba4682ded42142ace6e8634fff57788819e
Comment 8 Samba QA Contact 2020-11-05 10:01:57 UTC 
This bug was referenced in samba v4-12-stable (Release samba-4.12.10):

ae4d3932cfb107725ea052f9ac0dca8c9a52b162