reassign 235885 xlibs
severity 235885 wishlist
merge 233818 235885
tag 233818 - wontfix
thanks
On Wed, Mar 03, 2004 at 07:39:24PM +0100, Andreas Bach Aaen wrote:
> Onsdag den 3. marts 2004 19:02 skrev Branden Robinson:
> > On Wed, Mar 03, 2004 at 02:15:23PM +0100, Andreas Metzler wrote:
> > > Andreas Bach Aaen <abach@mail1.stofanet.dk> wrote:
> > > > Package: xlib6g
> > > > Severity: normal
> > > > Tags: sid
> > > >
> > > > I need xlib6g to be able to install netscape navigator 4.7x on
> > > > unstable.
> > >
> > > Use equivs.
> >
> > That doesn't work. I had thought it would, but I hadn't tried it.
> > See the archives of debian-x.
>
> I did have a look at debin-x archives, but didn't find any new
> information besides this thread. Any specific posting in your mind?
From: Branden Robinson <branden@debian.org>
To: 233867-submitter@bugs.debian.org, control@bugs.debian.org
Cc: 233818@bugs.debian.org
Subject: Bug#233818: Bug#233867: "Provides: xlib6g" needed in 4.3.0
Date: Fri, 20 Feb 2004 14:38:40 -0500
Message-ID: <20040220193839.GA16919@deadbeast.net>
X-Mailing-List: <debian-x@lists.debian.org> archive/latest/14432
You can find it in the list archives, as well as the bug logs of #233867 and
#233818.
...which is the information I needed to know to merge this duplicate bug.
[The following is a form letter.]
Hello,
You recently filed a duplicate bug report against a Debian package; 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=novice
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!
--
G. Branden Robinson | Don't use nuclear weapons to
Debian GNU/Linux | troubleshoot faults.
branden@debian.org | -- US Air Force Instruction 91-111
http://people.debian.org/~branden/ |
Attachment:
signature.asc
Description: Digital signature