Bug#646992: Package description unclear
Martin Eberhard Schauer wrote:
> Updating the German package description I found that the first sentence
> of the description might be simplified or rephrased.
Yes, it needs something; "provides [...] common operation" is
ungrammatical.
> What does "provides support and common operation" mean? If the library
> supports the format, I expect it to provide all necessary functionality
> to work with the format. Providing the ability to perform operations
> that are needed very often one could describe as "the ability to perform
> common operations". From this point of view in "support *and* common
> operations" and is wrong as common operations are a subset of full
> support:
> "and common operations" is superfluous. If the support is limited, I would
> like to know the limitations or an enumeration of the capabilities.
>
> So I would start the description with something like
> - This library provides support for the XPM image format, ...
> - This library supports the XPM image format, ...
> - This library enables your applications to handle the XPM image
> format, ...
I'd go for that first one. Or maybe the paragraph should just be
about XPM format, so it can serve as boilerplate for the other
packages in the set too, and the part specific to libxpm4 should just
say "This package provides runtime support for XPM format".
Looking at the whole description:
# Description: X11 pixmap library
# libXpm provides support and common operation for the XPM pixmap format, which
# is commonly used in legacy X applications. XPM is an extension of the
# monochrome XBM bitmap specificied in the X protocol.
# .
# More information about X.Org can be found at:
# http://www.X.org>
# .
# This module can be found at
# git://anongit.freedesktop.org/git/xorg/lib/libXpm
Paragraphs two and three of that look redundant now that there are
Homepage and Vcs-* fields.
Is it really correct for applications that use XPM format to be
described as "legacy"? XPM is my all-time favourite format for custom
desktop icons (since you can create them in a text editor), and I've
never seen any deprecation announcements. So maybe we can just say
"traditional" X applications...
Suggested patch attached.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- control.pristine2011-10-29 11:35:19.0 +0100
+++ control 2011-10-29 11:52:59.296548059 +0100
@@ -16,6 +16,7 @@
pkg-config,
ghostscript,
Standards-Version: 3.8.3
+Homepage: http://www.x.org
Vcs-Git: git://git.debian.org/git/pkg-xorg/lib/libxpm
Vcs-Browser: http://git.debian.org/?p=pkg-xorg/lib/libxpm.git
@@ -26,15 +27,11 @@
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: X11 pixmap library
- libXpm provides support and common operation for the XPM pixmap format, which
- is commonly used in legacy X applications. XPM is an extension of the
- monochrome XBM bitmap specified in the X protocol.
+ X PixMap format is an extension of the monochrome X BitMap format
+ specified in the X protocol, and is commonly used in traditional X
+ applications.
.
- More information about X.Org can be found at:
- http://www.X.org>
- .
- This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libXpm
+ This package provides runtime support for XPM format.
Package: libxpm4-dbg
Section: debug
@@ -43,18 +40,11 @@
Priority: extra
Depends: ${shlibs:Depends}, ${misc:Depends}, libxpm4 (= ${binary:Version})
Description: X11 pixmap library (debug package)
- libXpm provides support and common operation for the XPM pixmap format, which
- is commonly used in legacy X applications. XPM is an extension of the
- monochrome XBM bitmap specified in the X protocol.
- .
- This package contains the debug versions of the library found in libxpm4.
- Non-developers likely have little use for this package.
+ X PixMap format is an extension of the monochrome X BitMap format
+ specified in the X protocol, and is commonly used in traditional X
+ applications.
.
- More information about X.Org can be found at:
- http://www.X.org>
- .
- This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libXpm
+ This package provides debug symbols.
Package: libxpm-dev
Section: libdevel
@@ -62,32 +52,21 @@
Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}, libxpm4 (= ${binary:Version}),
libx11-dev, x11proto-core-dev
Description: X11 pixmap library (development headers)
- libXpm provides support and common operation for the XPM pixmap format, which
- is commonly used in legacy X applications. XPM is an extension of the
- monochrome XBM bitmap specified in the X protocol.
- .
- This package contains the development headers for the library found in
- libxpm4. Non-developers likely have little use for this package.
+ X PixMap format is an extension of the monochrome X BitMap format
+ specified in the X protocol, and is commonly us
Bug#646992: Package description unclear
Justin B Rye wrote:
> Martin Eberhard Schauer wrote:
>> Updating the German package description I found that the first sentence
>> of the description might be simplified or rephrased.
Oops, my first try at this
("http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646992#10";) didn't
(a) CC d-l-e or (b) mention that XPM is an image format. Second try.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- control.pristine2011-10-29 11:35:19.0 +0100
+++ control 2011-10-29 12:25:36.732547904 +0100
@@ -16,6 +16,7 @@
pkg-config,
ghostscript,
Standards-Version: 3.8.3
+Homepage: http://www.x.org
Vcs-Git: git://git.debian.org/git/pkg-xorg/lib/libxpm
Vcs-Browser: http://git.debian.org/?p=pkg-xorg/lib/libxpm.git
@@ -26,15 +27,11 @@
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: X11 pixmap library
- libXpm provides support and common operation for the XPM pixmap format, which
- is commonly used in legacy X applications. XPM is an extension of the
- monochrome XBM bitmap specified in the X protocol.
+ The X PixMap image format is an extension of the monochrome X BitMap
+ format specified in the X protocol, and is commonly used in traditional
+ X applications.
.
- More information about X.Org can be found at:
- http://www.X.org>
- .
- This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libXpm
+ This package provides runtime support for XPM format.
Package: libxpm4-dbg
Section: debug
@@ -43,18 +40,11 @@
Priority: extra
Depends: ${shlibs:Depends}, ${misc:Depends}, libxpm4 (= ${binary:Version})
Description: X11 pixmap library (debug package)
- libXpm provides support and common operation for the XPM pixmap format, which
- is commonly used in legacy X applications. XPM is an extension of the
- monochrome XBM bitmap specified in the X protocol.
- .
- This package contains the debug versions of the library found in libxpm4.
- Non-developers likely have little use for this package.
+ The X PixMap image format is an extension of the monochrome X BitMap
+ format specified in the X protocol, and is commonly used in traditional
+ X applications.
.
- More information about X.Org can be found at:
- http://www.X.org>
- .
- This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libXpm
+ This package provides debug symbols.
Package: libxpm-dev
Section: libdevel
@@ -62,32 +52,21 @@
Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}, libxpm4 (= ${binary:Version}),
libx11-dev, x11proto-core-dev
Description: X11 pixmap library (development headers)
- libXpm provides support and common operation for the XPM pixmap format, which
- is commonly used in legacy X applications. XPM is an extension of the
- monochrome XBM bitmap specified in the X protocol.
- .
- This package contains the development headers for the library found in
- libxpm4. Non-developers likely have little use for this package.
+ The X PixMap image format is an extension of the monochrome X BitMap
+ format specified in the X protocol, and is commonly used in traditional
+ X applications.
.
- More information about X.Org can be found at:
- http://www.X.org>
- .
- This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libXpm
+ This package contains the development headers for the libxpm4 library.
+ Non-developers likely have little use for this package.
Package: xpmutils
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: X11 pixmap utilities
- This package provides two tools, cxpm and sxpm.
- .
- cxpm is a tool to check the integrity of an XPM file.
- .
- sxpm is a tool to view XPM files, and takes a number of options.
- .
- More information about X.Org can be found at:
- http://www.X.org>
+ The X PixMap image format is an extension of the monochrome X BitMap
+ format specified in the X protocol, and is commonly used in traditional
+ X applications.
.
- This module can be found at
- git://anongit.freedesktop.org/git/xorg/lib/libXpm
+ This package provides two tools: cxpm (to check the integrity of an
+ XPM file) and sxpm (to view XPM files).
Bug#681981: Minor package description issues
Martin Eberhard Schauer wrote: > there are some minor (mainly orthographic) issues with the package > description (1): > > >Description: Compiz Fusion configuration system - gconf backend > Compiz Fusion is the result of the re-unification of the Beryl-project > and the community around the Compiz Window Manager. It seeks to provide > an easy and fun-to-use windowing environment, allowing use of the > graphics hardware to provide impressive effects, amazing speed and > unrivalled usefulness > . > This package provides the gconf-based configuration backend for the > compiz-fusion plugin system. > > > GNOME uses another spelling for GConf (2). Perhaps you meant reunion > instead of re-unification as well. And s/seeks/aims/ would sound better > for me. I'm generally with you on the capitalisation issues (and the full stop on the end of the first paragraph), but in fact "re-unification" is more likely as a synonym for "re-merger". I'd just wonder about the hyphen, and whether it's trying to say "the re-unification of the Beryl project *with* the community around the Compiz Window Manager." I'd also eliminate "allowing use", just because I see it too often, and I'm thoroughly unconvinced by its claims of "unrivalled usefulness" - I'd let it get away with "usability". My suggestion: Description: Compiz Fusion configuration system - GConf backend Compiz Fusion is the result of the reunification of the Beryl project with the community around the Compiz Window Manager. It seeks to provide an easy and fun-to-use windowing environment, taking advantage of the graphics hardware to provide impressive effects, amazing speed, and unrivalled usability. . This package provides the GConf configuration back-end for the Compiz Fusion plug-in system. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120718174020.ga3...@xibalba.demon.co.uk
Re: [RFR] templates://xorg-server/{xprint-common.templates}
Christian Perrier wrote:
> Your review should be sent as an answer to this mail.
> Description: Next Generation Nested X Server
Why all the caps? "X", fair enough, and "Next Generation" is
arguable, but since there's no such thing as an NGNXS I suggest:
Description: next generation nested X server
> - xserver-xephyr is an X server that can be run inside another X server,
> - much like xnest. xephyr though, is based on the kdrive X server, and as a
> + The xephyr server is an X server that can be run inside another X server,
> + much like xnest. It is based on the kdrive X server, and as a
>
>
> Avoids sentences beginning with a lowercase lettre which is ugly
The project (and even the /usr/bin executable name) is Xephyr;
likewise for Xnest.
Xephyr is an X server that can be run inside another X server, much like
Xnest. It is based on the kdrive X server, and as a result it supports
newer extensions than Xnest, including render and composite.
> -Description: Xprint - the X11 print system (binary)
> +Description: X11 print system (binary)
>
> repeating the package name in the description is discouraged
>
> The "the" then becomes discouraged style as well..:-)
(Incidentally, this synopsis is an example of the one exception
I've found for the rule of thumb I proposed last month for
validating short descriptions. The "X11 print system" part is in
effect a synopsis for a *family* of packages, and the bracketed
addendum explains the role of this particular package within its
family.)
> Xprint is an advanced printing system which enables X11 applications
> to use devices like printers, FAX or create documents in formats like
> PostScript, PDF, PCL, etc.
Fax is an irregular abbreviation for telefacsimile, not an acronym.
to use devices like printers or fax machines, or to create documents in
formats like PostScript, PDF, PCL, etc.
> This package provides Xprt, the Xprint server compiled from
> - xprint.mozdev.org, an X.org subproject. Xprint provides superior support
> - for printing from mozilla, including non-latin characters and MathML.
> + xprint.mozdev.org, an X.org subproject. Xprint provides superior support
> + for printing from Mozilla, including non-latin characters and MathML.
>
> Capital for "Mozilla"
Also for "Latin".
--
JBR
Ankh kak! (Ancient Egyptian blessing)
--- ../xorg-server.old/debian/xprint-common.templates 2007-08-28
19:48:27.0 +0100
+++ debian/xprint-common.templates 2007-09-01 09:32:13.0 +0100
@@ -1,12 +1,12 @@
Template: xprint-common/default_printer_resolution
Type: string
Default: 600
-_Description: Default printer resolution
- By default Xprint assumes a printer resolution of 600dpi. This should be fine
- for the majority of printers today.
+_Description: Default printer resolution:
+ By default, Xprint assumes a printer resolution of 600dpi. This should be
+ well suited for the majority of printers.
.
On certain 1200dpi printers, however, the image might appear squashed in the
corner of the page, or it might be blown up too large on 300dpi printers. If
- you are experiencing these kinds of printing problems, you may want to set
+ you are experiencing such printing problems, you may want to set
the default printer resolution to a more appropriate value. See
/usr/share/doc/xprint-common/README.printing-problems.gz for more details.
--- ../xorg-server.old/debian/control 2007-08-28 19:48:27.0 +0100
+++ debian/control 2007-09-01 10:02:13.0 +0100
@@ -43,7 +43,7 @@
Conflicts: xserver-xorg (<< 6.8.2-38), xserver-xfree86 (<< 1:7.0.0),
xserver-xorg-video, xserver-common, fglrx-driver (<< 8.37.6)
Replaces: xserver-xorg (<< 6.8.2-38), xserver-xfree86 (<< 1:7.0.0),
xserver-common
Provides: xserver
-Description: X.Org X server -- core server
+Description: X.Org X server - core server
The X.Org X server is an X server for several architectures and operating
systems, which is derived from the XFree86 4.x series of X servers.
.
@@ -52,8 +52,8 @@
.
The X.Org server either needs fonts installed on the local host, or needs to
know of a remote hosts that provides font services (with xfs, for instance).
- The former means that fonts packages are mandatory. The latter means that
- font packages may be gratuitous. To err on the side of caution, install at
+ The former means that fonts packages are mandatory. The latter means that
+ font packages may be gratuitous. To err on the side of caution, install at
least the xfonts-base, xfonts-100dpi or xfonts-75dpi, and xfonts-scalable
packages.
.
@@ -67,7 +67,7 @@
Package: xserver-xorg-dev
Architecture: any
Depends: ${misc:Depends}
-Description: X.Org X server -- development files
+Description: X.Org X server - development files
This package provides development files for the X.Org ('Xorg') X server.
This is not quite the same as the DDK (Driver Development Kit) from the
XFree86 4.x and X.Org 6.7, 6.8 and 6.9 series of serv
Re: Bug#864166: release-notes: proofreading sweep - issues.dbk
Julien Cristau wrote: > Niels Thykier wrote: >> Justin B Rye: >>> I was assuming otherwise because the first symptom I ran into was that >>> running startx in the absence of xserver-xorg-legacy gave me an X >>> session with non-functional mouse and keyboard. >>> >>> But when I check now, installing every available xserver-xorg-* >>> package in main including -legacy as well as -input-libinput makes no >>> difference to that. On a testbed stretch machine with functional >>> logind and so on but with an old KMS-incapable graphics card, I >>> haven't found any way of making startx usable. >> >> Not sure what is going there. But I haven't used startx for years until >> I learned of this feature, so I am probably not the right person to ask >> what is going on/why it doesn't work. >> >>> Switching over to lightdm I can get a usable session without -legacy >>> as long as I have -input-libinput. So I'm afraid I have no idea >>> what's going on, or even how many problems there are. >> >> As I understand it, lightdm will start X as root unconditionally, so >> that will work with or without -legacy. You want -legacy when using gdm >> (or startx) plus have "old drivers". >> >> * @debian-x: Is the above correct? >> > Yes, any reasonable (read: KMS) setup will work fine without -legacy. > In the absence of KMS (e.g. virtualbox, or new hardware not supported by > the drivers we ship), you'll need either -legacy or a DM that hasn't > been updated to starting X as non-root yet. So if I *do* have all the xserver-xorg-* packages installed (and logind and so on), it's expected that everything should work, even on an antique graphics card? For me, startx refuses to work on stretch - it starts, but won't accept input. Switching to lightdm fixes it. I hope this glitch isn't going to be a widespread result of 8-to-9 dist-upgrades, because the other mystery issue I keep encountering breaks networking, and dead console plus dead SSH is a pain. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Re: Bug#864166: release-notes: proofreading sweep - issues.dbk
Julien Cristau wrote: > On 06/05/2017 09:30 PM, Justin B Rye wrote: >> So if I *do* have all the xserver-xorg-* packages installed (and >> logind and so on), it's expected that everything should work, even on >> an antique graphics card? For me, startx refuses to work on stretch - >> it starts, but won't accept input. Switching to lightdm fixes it. > > "antique graphics card" isn't something I can work with, please give > actual details? An Intel 82945G/GZ (i.e. i945). It's an old machine, which is part of the reason it was using startx. Is that expected to make a difference that would let a display manager work where stretch startx doesn't? -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#547143: xserver-xorg: xorg/evdev/HAL versus serial mouse
Package: xserver-xorg Version: 1:7.4+4 Severity: wishlist I'm calling this wishlist because I've eventually managed to get X working again; it's essentially a documentation issue. As NEWS.Debian says, "devices configured in xorg.conf to use the mouse or kbd driver are ignored by the X server by default." I'm meant to switch over to HAL and evdev. That's all very well for you kids with your shiny twentyfirst-century laptops, but unfortunately, this old machine has no PS/2 ports. It uses an AT-port keyboard (which evdev is happy to recognise as an input device) and a serial mouse (which is apparently ignored). I don't see any mention of this issue in the docs, so I thought I'd better report it and the workaround I'm using. The xorg.conf below gets X to work as normal again with a minimum of complaining - though it also requires HAL to be disabled via an "exit 0" at the top of the init.d script. In principle there's probably some alternative involving writing appropriate custom .fdi files, but if I could work out how to do that sort of thing I'd be busy using my mutant psychic powers to fight superpowered criminals like the rest of you X-developers! HAL has no discernible reason for being present on this box, so I'm just nobbling it. Note that just disabling HAL and AutoAddDevices wasn't enough - I've had to put lots more lines back in my xorg.conf that I'd previously been leaving to the defaults. Many thanks for providing /usr/share/doc/xserver-xorg/examples/xorg.conf! If it has been decided that xorg no longer supports serial mice, that's fine; just make sure the announcement gets into the Squeeze release notes. Otherwise, please document somewhere the approved method for keeping them working - the obvious place would be a NEWS.Debian file for xserver-xorg-input-mouse. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2009-08-10 17:18 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1689976 2009-08-06 17:55 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400/G450 (rev 05) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1072 2009-09-16 14:55 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # comments like -*- sh -*- # cf: /usr/share/doc/xserver-xorg/examples/xorg.conf Section "ServerFlags" Option "AutoAddDevices""False" Option "AutoEnableDevices" "False" EndSection Section "InputDevice" Identifier "Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbLayout" "gb" EndSection Section "InputDevice" Identifier "Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/ttyS0" Option "Protocol" "MouseMan" EndSection Section "Device" Identifier "Video Card" Option "UseFBDev" "False" EndSection Section "Monitor" Identifier "Monitor" HorizSync 30-82 VertRefresh 30-100 EndSection Section "Screen" Identifier "Screen" Device "Video Card" Monitor "Monitor" SubSection "Display" Modes "1280x1024" EndSubSection EndSection Section "ServerLayout" Identifier "Layout" Screen "Screen" InputDevice "Keyboard" InputDevice "Mouse" EndSection # Xorg X server log files on system: -rw-r- 1 root adm 30175 2009-09-16 14:54 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.6.3 Release Date: 2009-7-31 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.30.4-dsa-ia32 i686 Debian Current Operating System: Linux xan 2.6.30.custom #1 Sun Aug 16 16:07:03 BST 2009 i586 Build Date: 06 August 2009 04:49:57PM xorg-server 2:1.6.3-1+b1 (bui...@murphy.debian.org) Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 16 14:47:02 2009 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Layout" (**) |-->Screen "Screen" (0) (**) | |-->Monitor "Monitor" (**) | |-->Device "Video Card" (**) |-->Input Device "Keyboard" (**) |-->Input Device "Mouse" (**) Option "AutoAddDevices" "False" (**) Option "AutoEnableDevices" "False" (**) Not automatically adding devices (**) Not automatically enabling devices (
Bug#547143: xserver-xorg: xorg/evdev/HAL versus serial mouse
Julien Cristau wrote: > On Thu, Sep 17, 2009 at 09:48:53 +0100, Justin B Rye wrote: [...] >> Note that just disabling HAL and AutoAddDevices wasn't enough - I've >> had to put lots more lines back in my xorg.conf that I'd previously >> been leaving to the defaults. Many thanks for providing >> /usr/share/doc/xserver-xorg/examples/xorg.conf! > > That's weird. I'd have expected that disabling AutoAddDevices would > make things work with the old xorg.conf InputDevice section (once that > is done, keeping hal running or stopping it shouldn't make a > difference). This machine's due to be decommissioned soon anyway, so I'm hurrying through some more tests while it's still available. I've switched to a standard Debian kernel in case there are any driver issues. Summarised findings: * I was getting interference from a buggy display manager * other display managers (or startx) allow hal+serialmouse * hal, the kbd driver, and Ctrl-Alt-Backspace interact badly Details: The first thing I tried was disabling my display manager, de-lobotomising HAL and running startx. This works! Well, except that DontZap appears to be in effect, contrary to my instructions. Yes, I edited the xorg.conf and reconfigured console-setup and restarted hal and rebooted for luck. Still nothing. But that's only a mild annoyance for now. It's only when I use wdm that everything goes haywire. My first ten tries go like this: * wdmLogin seems happy then segfaults halfway through launching a session, spewing some really strange syslog messages. * Works perfectly. * Works perfectly. * An amusing failure mode where my attempt to enter a username results in it doing that "shaking the box to indicate a wrong password" thing that gets more and more frenzied until it crashes. * Works except that it doesn't recognise the Enter key. Useless. Where's my goddamn Ctrl-Alt-Backspace?! * Works perfectly. * Works perfectly. * Segfaults on the middle letter of my username. * Logs me in rather slowly, but otherwise works. * Works perfectly. Plain xdm works fine too. So it looks as if switching from wdm to xdm would let me keep hal running on this hardware... if I had some reason to want hal. Now, if I temporarily move my xorg.conf out of the way and rely on the defaults (and hal), then startx, xdm, and wdm all work equally well. The resolution's hopeless, the serial mouse is missing, but nothing segfaults, I've got a GB keymap, and Ctrl-Alt-Backspace works. Hmmm. Whoops! On my last try of ten, wdmLogin segfaults with a rush of nasty kernel errors about secondary DMA buffers. So wdm seems to be just plain flaky, and I should go and submit a proper bugreport for it. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#549457: x11-apps: flawed package description
Package: x11-apps
Version: 7.4+2
Severity: wishlist
Tags: patch
The current package description has two problems.
Its first paragraph is a relic of the days when these apps were in
xbase-clients:
> An X client is a program that interfaces with an X server (almost always via
> the X libraries), and thus with some input and output hardware like a
> graphics card, monitor, keyboard, and pointing device (such as a mouse).
This explanation of what an X client is became pointless when the
word "client" disappeared from the package name, so I recommend just
throwing out the whole paragraph.
Second, three of the listed apps (bitmap, xcursorgen, and xmore)
have no descriptions. In the case of bitmap, this looks like the
result of an editing error, since the line ends with a comma and
trailing whitespace rather than a semicolon, and since its
associates atobm and bmtoa have fallen off the list entirely.
My patch gives them the following suggested descriptions:
- atobm, bitmap, and bmtoa, tools for manipulating bitmap images;
- xcursorgen, a tool for creating X cursor files from PNGs;
- xmore, a text pager;
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.30.custom
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages x11-apps depends on:
ii cpp 4:4.3.3-9 The GNU C preprocessor (cpp)
ii libc6 2.9-25 GNU C Library: Shared libraries
ii libpng12-01.2.39-1 PNG library - runtime
ii libsm62:1.1.1-1 X11 Session Management library
ii libx11-6 2:1.2.2-1 X11 client-side library
ii libxaw7 2:1.0.6-1 X11 Athena Widget library
ii libxcursor1 1:1.1.9-1 X cursor management library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii libxft2 2.1.13-3 FreeType-based font drawing librar
ii libxkbfile1 1:1.0.5-1 X11 keyboard file manipulation lib
ii libxmu6 2:1.0.4-2 X11 miscellaneous utility library
ii libxmuu1 2:1.0.4-2 X11 miscellaneous micro-utility li
ii libxrender1 1:0.9.4-2 X Rendering Extension client libra
ii libxt61:1.0.6-1 X11 toolkit intrinsics library
ii x11-common1:7.4+4X Window System (X.Org) infrastruc
x11-apps recommends no packages.
Versions of packages x11-apps suggests:
ii mesa-utils7.5.1-1Miscellaneous Mesa GL utilities
-- no debconf information
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru x11-apps-7.4+2.pristine/debian/control x11-apps-7.4+2/debian/control
--- x11-apps-7.4+2.pristine/debian/control 2009-07-27 18:20:42.0 +0100
+++ x11-apps-7.4+2/debian/control 2009-10-03 14:58:50.0 +0100
@@ -48,19 +48,15 @@
xcalc, xclipboard, xclock, xconsole, xcursorgen, xditview, xeyes, xgc,
xload, xlogo, xmag, xman, xmore, xwd, xwud
Description: X applications
- An X client is a program that interfaces with an X server (almost always via
- the X libraries), and thus with some input and output hardware like a
- graphics card, monitor, keyboard, and pointing device (such as a mouse).
- .
This package provides a miscellaneous assortment of X applications
that ship with the X Window System, including:
- - bitmap,
+ - atobm, bitmap, and bmtoa, tools for manipulating bitmap images;
- oclock and xclock, graphical clocks;
- xbiff, a tool which tells you when you have new email;
- xcalc, a scientific calculator desktop accessory;
- xclipboard, a tool to manage cut-and-pasted text selections;
- xconsole, which monitors system console messages;
- - xcursorgen;
+ - xcursorgen, a tool for creating X cursor files from PNGs;
- xditview, a viewer for ditroff output;
- xedit, a simple text editor for X;
- xeyes, a demo program in which a pair of eyes track the pointer;
@@ -69,7 +65,7 @@
- xlogo, a demo program that displays the X logo;
- xmag, which magnifies parts of the X screen;
- xman, a manual page browser;
- - xmore;
+ - xmore, a text pager;
- xwd, a utility for taking window dumps ("screenshots") of the X session;
- xwud, a viewer for window dumps created by xwd;
- Xmark, x11perf, and x11perfcomp, tools for benchmarking graphical
Bug#547143: xserver-xorg: xorg/evdev/HAL versus serial mouse
Justin B Rye wrote: > I'm calling this wishlist because I've eventually managed to get X > working again; it's essentially a documentation issue. The issue of serial mice not working via evdev is documented in the draft Squeeze releasenotes (along with a pointer to the package inputattach), so I'd say you're entitled to close this. -- JBR For trifling occasions it is better to accomplish things simply by yelling - _Hagakure_, Yamamoto Tsunetomo (1716) -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110131101836.ga7...@xibalba.demon.co.uk
