Your message dated Sun, 22 Jun 2008 09:35:02 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#487468: unsightly double slashes in Xorg.0.log paths
has caused the Debian Bug report #487468,
regarding unsightly double slashes in Xorg.0.log paths
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
487468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487468
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xserver-xorg-core
Version: 2:1.4.1~git20080517-2
Severity: wishlist
$ grep -c // /var/log/Xorg.0.log
22
21 of which are unsightly double slashes in paths. Please use only
single slashes, else looks sloppy.
P.S.,
$ grep xorg-server /var/log/Xorg.0.log
Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080517-2)
I wish you would use a real package ^^^^^^^^^^^ name here that one could
report bugs against. I had a hard time guessing what package this bug
belonged to. grep-status git20080517 gave the answer away though :-)
--- End Message ---
--- Begin Message ---
[EMAIL PROTECTED] wrote:
> Package: xserver-xorg-core
> Version: 2:1.4.1~git20080517-2
> Severity: wishlist
>
> $ grep -c // /var/log/Xorg.0.log
> 22
> 21 of which are unsightly double slashes in paths. Please use only
> single slashes, else looks sloppy.
>
If you don't know what // means in a path, you're not smart enough to
look at a Xserver log. Fixing this is completely useless.
> P.S.,
> $ grep xorg-server /var/log/Xorg.0.log
> Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080517-2)
>
> I wish you would use a real package ^^^^^^^^^^^ name here that one could
> report bugs against. I had a hard time guessing what package this bug
> belonged to. grep-status git20080517 gave the answer away though :-)
>
It's the source package name and versions number the Xserver has been
built from. And reportbug knows about it:
$ reportbug xorg-server
Getting status for xorg-server...
Which of the following packages is the bug in?
1 xdmx distributed multihead X server
2 xdmx-tools Distributed Multihead X tools
3 xnest Nested X server
4 xprint X11 print system (binary)
5 xprint-common Xprint - the X11 print system (configuration files)
6 xserver-xephyr nested X server
7 xserver-xfbdev Linux framebuffer device tiny X server
8 xserver-xorg-core Xorg X server - core server
9 xserver-xorg-core-dbg Xorg - the X.Org X server (debugging symbols)
10 xserver-xorg-dev Xorg X server - development files
11 xvfb Virtual Framebuffer 'fake' X server
12 xorg-server Source package
Select one of these packages:
Brice
--- End Message ---
