Package: xnest Version: 2:1.1.1-9 Severity: minor Tags: patch The Xnest manpage contains the string __mansuffix__ in several places where it looks like there should be a man section, for example:
> SEE ALSO > Xserver(__mansuffix__), xdpyinfo(__mansuffix__), X(7) It seems to be because these strings are never replaced, and should be __appmansuffix__ instead. I have attached a patch which should fix this, however I have not tested it. The patch patches the file <debian/patches/03_xnest_manpage_overhaul.diff>. -Ted -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-2-686 Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Versions of packages xnest depends on: ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libx11-6 2:1.0.0-9 X11 client-side library ii libxau6 1:1.0.1-2 X11 authorisation library ii libxdmcp6 1:1.0.1-2 X11 Display Manager Control Protoc ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfont1 1:1.2.2-1 X11 font rasterisation library xnest recommends no packages. -- no debconf information
--- debian/patches/03_xnest_manpage_overhaul.diff 2006-10-02 12:45:02.000000000 +1000 +++ debian/patches/03_xnest_manpage_overhaul.diff-new 2006-10-02 12:54:21.000000000 +1000 @@ -37,7 +37,7 @@ .\" $XFree86: xc/programs/Xserver/hw/xnest/Xnest.man,v 1.6 2001/01/27 18:21:00 dawes Exp $ .\" -.TH XNEST 1 __xorgversion__ -+.TH Xnest __mansuffix__ __xorgversion__ ++.TH Xnest __appmansuffix__ __xorgversion__ .SH NAME Xnest \- a nested X server .SH SYNOPSIS @@ -74,7 +74,7 @@ +.B Xnest +supports all standard options of the sample server implementation. +For more details, please see -+.BR Xserver (__mansuffix__). ++.BR Xserver (__appmansuffix__). +The following additional arguments are supported as well. +.TP +.BI "\-display " string @@ -172,7 +172,7 @@ +class of the default visual of the real server, but it must be supported by the +real server. +Use -+.BR xdpyinfo (__mansuffix__) ++.BR xdpyinfo (__appmansuffix__) +to obtain a list of supported visual classes on the real server before starting +.BR Xnest . +If the user chooses a static class, all the colors in the default color map will @@ -192,7 +192,7 @@ +depth of the default visual of the real server, but it must be supported by the +real server. +Use -+.BR xdpyinfo (__mansuffix__) ++.BR xdpyinfo (__appmansuffix__) +to obtain a list of supported visual depths on the real server before starting +.BR Xnest . +.TP @@ -305,7 +305,7 @@ +For example, +.B xterm \-display :1.1 +will open an -+.BR xterm (__mansuffix__) ++.BR xterm (__appmansuffix__) +client in the nested server with the display number +.B :1 +on the second screen. @@ -451,7 +451,7 @@ +Starting up +.B Xnest +is just as simple as starting up -+.BR xclock (__mansuffix__) ++.BR xclock (__appmansuffix__) +from a terminal emulator. +If a user wishes to run +.B Xnest @@ -607,7 +607,7 @@ +Thus, if there is a font in the local font path of the nested server, there is +no guarantee that this font exists in the remote font path of the real server. +The -+.BR xlsfonts (__mansuffix__) ++.BR xlsfonts (__appmansuffix__) +client, if run on the nested server, will list fonts in the local font path and, +if run on the real server, will list fonts in the remote font path. +Before a font can be successfully opened by the nested server, it has to exist @@ -648,6 +648,6 @@ Davor Matic, MIT X Consortium - +.SH "SEE ALSO" -+.BR Xserver (__mansuffix__), -+.BR xdpyinfo (__mansuffix__), ++.BR Xserver (__appmansuffix__), ++.BR xdpyinfo (__appmansuffix__), +.BR X (__miscmansuffix__)
