Your message dated Mon, 9 Jun 2003 11:52:23 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#196718: xfree86-common: After upgrading XFree crashes at
all attempts of starting it
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 9 Jun 2003 06:49:58 +0000
>From [EMAIL PROTECTED] Mon Jun 09 01:49:58 2003
Return-path: <[EMAIL PROTECTED]>
Received: from bgo1-bap1-217-191-204.adsl.tele2.no (ketil.homeunix.net)
[193.217.191.204]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19PGTd-0004GZ-00; Mon, 09 Jun 2003 01:49:57 -0500
Received: from ketil.homeunix.net ([EMAIL PROTECTED] [127.0.0.1])
by ketil.homeunix.net (8.12.9/8.12.9/Debian-3) with ESMTP id
h596oecL023455;
Mon, 9 Jun 2003 08:50:41 +0200
Received: (from [EMAIL PROTECTED])
by ketil.homeunix.net (8.12.9/8.12.9/Debian-3) id h596oePS023453;
Mon, 9 Jun 2003 08:50:40 +0200
Message-Id: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: ketil V <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject:
=?iso-8859-1?q?xfree86-common=3A_After_upgrading_XFree_crashes_at_all_att?=
=?iso-8859-1?q?empts_of_starting_it=0D=0Apackages_depending_on_X_=28Gnome=2C?=
=?iso-8859-1?q?_KDE=2C=2E=2E=2E=29=29?=
X-Mailer: reportbug 2.10.1
Date: Mon, 09 Jun 2003 08:50:40 +0200
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-5.1 required=4.0
tests=BAYES_30,HAS_PACKAGE,MSG_ID_ADDED_BY_MTA_3
version=2.53-bugs.debian.org_2003_05_24
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_05_24
(1.174.2.15-2003-03-30-exp)
Package: xfree86-common
Version: 4.2.1-7
Severity: critical
Justification: breaks unrelated software (more spesific: All software
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux ketil.homeunix.net 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002
i686
Locale: LANG=no_NO, LC_CTYPE=no_NO
Versions of packages xfree86-common depends on:
ii debconf 1.2.39 Debian configuration management sy
ii debianutils 2.5.2 Miscellaneous utilities specific t
-- debconf information:
xfree86-common/experimental_packages:
---------------------------------------
Received: (at 196718-done) by bugs.debian.org; 9 Jun 2003 16:52:27 +0000
>From [EMAIL PROTECTED] Mon Jun 09 11:52:24 2003
Return-path: <[EMAIL PROTECTED]>
Received: from dhcp065-026-182-085.indy.rr.com (redwald.deadbeast.net)
[65.26.182.85]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19PPse-0003Mt-00; Mon, 09 Jun 2003 11:52:24 -0500
Received: by redwald.deadbeast.net (Postfix, from userid 1000)
id 3445D64162; Mon, 9 Jun 2003 11:52:23 -0500 (EST)
Date: Mon, 9 Jun 2003 11:52:23 -0500
From: Branden Robinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#196718: xfree86-common: After upgrading XFree crashes at all
attempts of starting it
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="TakKZr9L6Hm6aLOc"
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-19.3 required=4.0
tests=BAYES_01,EMAIL_ATTRIBUTION,PGP_SIGNATURE_2,
QUOTED_EMAIL_TEXT,USER_AGENT_MUTT
autolearn=ham version=2.53-bugs.debian.org_2003_05_24
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_05_24
(1.174.2.15-2003-03-30-exp)
--TakKZr9L6Hm6aLOc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
packages depending on X (Gnome, KDE,...))
Reply-To:=20
In-Reply-To: <[EMAIL PROTECTED]>
On Mon, Jun 09, 2003 at 08:50:40AM +0200, ketil V wrote:
> Package: xfree86-common
> Version: 4.2.1-7
> Severity: critical
> Justification: breaks unrelated software (more spesific: All software
No, it doesn't break "all software". Please.
Anyway, this bug has already been filed about 1 billion times; see
#196554,#196575,#196621.
Closing this hysterical and redundant report.
[The following is a form letter.]
Hello,
You recently filed a duplicate bug report against Debian's XFree86
packages; that is, the problem had already been reported.
While there is often nothing inherently wrong with doing so, the filing of
duplicate reports can cause Debian package maintainers to spend time
performing triage and maintenance operations on bug reports (e.g.,
instructing the Debian Bug Tracking System to merge the duplicates) that
could otherwise be spent resolving problems and doing other work on the
package.
One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name. A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports. This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report. This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers. The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports. (If you've ever
gotten a "bounce" message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)
Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System.
One way to install reportbug is with "apt-get"; for
example:
# apt-get install reportbug
The "reportbug" command has a few different modes that cater to different
levels of user expertise. If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.
$ reportbug --mode=3Dnovice
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>
If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.
$ reportbug
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>
The reportbug command is extensively documented in its usage message and
manual page. Commands to view these pieces of documentation are:
$ reportbug --help | more
$ man reportbug
(The output of the above commands has been omitted from this message.)
Thanks for using the Debian system!
--=20
G. Branden Robinson | Q: How does a Unix guru have sex?
Debian GNU/Linux | A: unzip;strip;touch;finger;mount;
[EMAIL PROTECTED] | fsck;more;yes;fsck;fsck;fsck;
http://people.debian.org/~branden/ | umount;sleep
--TakKZr9L6Hm6aLOc
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iEYEARECAAYFAj7ku0YACgkQ6kxmHytGonwb6gCgkJ1X64YSVJsxOxhqyY6kMGbe
1PgAn1MWTcpi2eRQZfjGQvLvltzSeboT
=BT07
-----END PGP SIGNATURE-----
--TakKZr9L6Hm6aLOc--
