Your message dated Fri, 29 Aug 2003 18:58:54 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#207809: xserver-xfree86: postrm script hangs
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; 29 Aug 2003 22:29:01 +0000
>From [EMAIL PROTECTED] Fri Aug 29 17:28:59 2003
Return-path: <[EMAIL PROTECTED]>
Received: from gluck.debian.org [192.25.206.10]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19spKo-0005ny-00; Fri, 29 Aug 2003 14:55:02 -0500
Received: from extavgw4.ball.com [162.18.103.211]
by gluck.debian.org with smtp (Exim 3.35 1 (Debian))
id 19sioh-0003wJ-00; Fri, 29 Aug 2003 06:57:27 -0600
Received: from APPMSG3.AERO.BALL.COM ([162.18.82.43]) by 162.18.103.211 with
InterScan Messaging Security Suite; Fri, 29 Aug 2003 06:53:25 -0600
Received: from mammoth.ball.com ([162.18.180.78]) by APPMSG3.AERO.BALL.COM with
Microsoft SMTPSVC(5.0.2195.2966);
Fri, 29 Aug 2003 06:57:21 -0600
Received: from mammoth.ball.com ([EMAIL PROTECTED] [127.0.0.1])
by mammoth.ball.com (8.12.9/8.12.9/Debian-5) with ESMTP id
h7TCvK8U010438;
Fri, 29 Aug 2003 06:57:20 -0600
Received: (from [EMAIL PROTECTED])
by mammoth.ball.com (8.12.9/8.12.9/Debian-5) id h7TCvK5h010436;
Fri, 29 Aug 2003 06:57:20 -0600
Message-Id: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Thomas E. Vaughan" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xserver-xfree86: postrm script hangs
X-Mailer: reportbug 2.26.1
Date: Fri, 29 Aug 2003 06:57:19 -0600
X-OriginalArrivalTime: 29 Aug 2003 12:57:21.0132 (UTC)
FILETIME=[159732C0:01C36E2D]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-5.0 required=4.0
tests=HAS_PACKAGE
version=2.53-bugs.debian.org_2003_8_27
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_8_27
(1.174.2.15-2003-03-30-exp)
Package: xserver-xfree86
Version: unavailable; reported 2003-08-29
Severity: normal
It's hard to uninstall this package because xserver-xfree86.postrm
hangs.
-- System Information:
Debian Release: testing/unstable
Architecture: sparc
Kernel: Linux mammoth 2.4.21 #1 Thu Aug 7 20:30:12 EDT 2003 sparc64
Locale: LANG=C, LC_CTYPE=C
---------------------------------------
Received: (at 207809-done) by bugs.debian.org; 29 Aug 2003 23:58:58 +0000
>From [EMAIL PROTECTED] Fri Aug 29 18:58:55 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 19st8p-0007mv-00; Fri, 29 Aug 2003 18:58:55 -0500
Received: by redwald.deadbeast.net (Postfix, from userid 1000)
id 43FA46411E; Fri, 29 Aug 2003 18:58:54 -0500 (EST)
Date: Fri, 29 Aug 2003 18:58:54 -0500
From: Branden Robinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#207809: xserver-xfree86: postrm script hangs
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="iBwuxWUsK/REspAd"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.4i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-20.8 required=4.0
tests=EMAIL_ATTRIBUTION,IN_REP_TO,PGP_SIGNATURE_2,
QUOTED_EMAIL_TEXT,REFERENCES,REPLY_WITH_QUOTES,
USER_AGENT_MUTT
autolearn=ham version=2.53-bugs.debian.org_2003_8_27
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_8_27
(1.174.2.15-2003-03-30-exp)
--iBwuxWUsK/REspAd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Aug 29, 2003 at 06:57:19AM -0600, Thomas E. Vaughan wrote:
> Package: xserver-xfree86
> Version: unavailable; reported 2003-08-29
> Severity: normal
>=20
> It's hard to uninstall this package because xserver-xfree86.postrm
> hangs.
It's hard to do much about bugs that have already been fixed.
Namely, in xfree86 4.2.1-11.
[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 | People are equally horrified at
Debian GNU/Linux | hearing the Christian religion
[EMAIL PROTECTED] | doubted, and at seeing it
http://people.debian.org/~branden/ | practiced. -- Samuel Butler
--iBwuxWUsK/REspAd
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iEYEARECAAYFAj9P6L0ACgkQ6kxmHytGonwYHACeP9nqjEH2eKSBZZuFLx1BLNIL
qOkAni6A82vmFYTXYPfT3wmr/h39ROEy
=21ei
-----END PGP SIGNATURE-----
--iBwuxWUsK/REspAd--
