Red Hat Bugzilla – Bug 172072
Numbers of inconsistency in man and xml files
Last modified: 2007-11-30 17:11:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.7.12) Gecko/20050919 Firefox/1.0.7
Description of problem:
Like bug 167374, there are numbers of inconsistent description in man
and xml files against the corresponding source files.
For exaple, in lmorph setting in xscreensaver-demo, the movement of slider
labeled "Lines" disables lmorph hack.
See the attached files below.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Example2: run "xscreensaver-demo" and select "mirrorblob"
2. Slide the bar labeled "Crossfade Duration"
Actual Results: mirrorblob hack becomes invalid.
Created attachment 120547 [details]
Fix inconsistency for xscreensaver rpm 4.22-19
Patch to fix inconsistency for xscreensaver-4.22-19.
This patch changes man and xml files but doesn't change the corresponding
Created attachment 120548 [details]
Summary of the patch above.
Summary of the patch above (id: 120547).
Created attachment 120549 [details]
Similar patch for xscreensaver 4.23
xscreensaver version 4.23 is released but lots of the inconsistency is left
unfixed (and another bug added) .
This is a patch for 4.23.
Created attachment 120550 [details]
Summary of the patch for 4.23
And the summary of the patch for 4.23.
Created attachment 120551 [details]
Patch to correct man entry for manual files
Patch to correct man entry in manual files.
Wow, thanks for all those patches! That must have been a lot of work... This will be in 4.24.
Created attachment 121832 [details]
Patch for 4.23 with new 4 fixes.
Sorry, the fixes for glhanoi.xml, juggler3d.xml, celtic.man,
glhanoi.man (all of these are added newly in 4.23; that is,
these files are not in 4.22) are added.
Created attachment 121833 [details]
Summary of the patch for 4.23 with 4 new fixes
And the summary of the patch above with 4 new (added) fixes.
Closing for fedora core devel for now, as 4.23-1 rpm included my patch.
I'll verify this issue again when upstream version 4.24 is released.