Your message dated Tue, 10 May 2005 18:47:32 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#294697: fixed in reportbug 3.12
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; 11 Feb 2005 07:06:21 +0000
>From [EMAIL PROTECTED] Thu Feb 10 23:06:21 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dhcp065-026-182-085.indy.rr.com (sisyphus.deadbeast.net)
[65.26.182.85]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CzUsf-0007au-00; Thu, 10 Feb 2005 23:06:21 -0800
Received: by sisyphus.deadbeast.net (Postfix, from userid 1000)
id 69C0F68C02C; Fri, 11 Feb 2005 02:06:20 -0500 (EST)
Content-Type: multipart/mixed; boundary="===============1764217192=="
MIME-Version: 1.0
From: Branden Robinson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: reportbug: does not page presubj messages that are bigger than the tty
X-Mailer: reportbug 3.7.1
Date: Fri, 11 Feb 2005 02:06:20 -0500
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===============1764217192==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: reportbug
Version: 3.7.1
Severity: important
Hi,
I wrote a long -- well, some would say massive -- presubj message for
xserver-xfree86 (attached). It will definitely be longer than some
people's terminals are tall.
reportbug should invoke a pager (probably sensible-pager) to scroll the
presubj file. If you didn't want to do so unconditionally, you could count
the number of lines in it first, and compare it to the tty's number of
lines. I'm not sure how to do the latter in Python off the top of my head.
The former seems to be as easy as:
file = open("/usr/share/bug/%s/presubj" % (package,))
numlines = len(file.readlines())
-- Package-specific info:
** Environment settings:
EDITOR="/usr/bin/vim"
DEBEMAIL="[EMAIL PROTECTED]"
DEBFULLNAME="Branden Robinson"
** /home/branden/.reportbugrc:
reportbug_version "2.20"
mode expert
ui text
realname "Branden Robinson"
email "[EMAIL PROTECTED]"
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.9-powerpc-smp
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages reportbug depends on:
ii python2.3 2.3.5-1 An interactive high-level object-o
-- no debconf information
--===============1764217192==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="xserver-xfree86.bug.presubj"
Before filing a bug against the XFree86 X server, please note the
following:
1) The problem you are experiencing may be a known issue that is discussed
in the Debian X FAQ. If you are unfamiliar with this document, please
consult it before filing your report.
XHTML version: file:///usr/share/doc/xfree86-common/FAQ.xhtml
plain text version: file:///usr/share/doc/xfree86-common/FAQ.gz
2) Please be cautious with your bug severities. Most bugs in the XFree86 X
server are specific to particular drivers, and often manifest only on
particular models of display adapter. This means that while the X server
may be unusable for you, it typically is not for the majority of users.
Therefore, bug severities of "critical" or "grave" are seldom appropriate.
In general, if the X server crashes, hangs, or locks up your system, the
bug should be assigned a severity of "important". If you are in doubt
about what severity to use, choose "normal". The Debian package
maintainers will upgrade reports if they have severities that are too low
-- you need not fear that your report will be ignored because it was filed
with a lower severity than was appropriate.
3) Problems with the keyboard are almost always due to bugs in the XKB (X
Keyboard Extension) data files. Reports about such issues should be filed
against the "xlibs" package, not "xserver-xfree86".
4) Problems with 3D acceleration or DRI (Direct Rendering Infrastructure)
are usually problems with the Mesa GL library, the Mesa DRI modules, or
with the Linux kernel's direct rendering manager (DRM). Bugs in these
systems can even lock up the computer. Here's a table to help you choose
which package is the most appropriate for your report:
Situation Package
--------- -------
problem has nothing to do with GL/DRI xserver-xfree86
disabling Mesa DRI modules fixes problem xlibmesa-dri
GL-related problem not affected by DRI xlibmesa-gl
changing kernel version fixes problem kernel
Note that some hardware vendors provide their own GL library
implementations, which are not always compatible with XFree86. If you
think the problem lies in xlibmesa-gl but that package is not installed,
you may have just such a compatibility problem; try the command:
reportbug --file /usr/lib/libGL.so.1
5) If you are submitting a patch -- thank you! Please make sure, however,
that the code you are contributing is not under the XFree86 1.1 License.
Most of XFree86 4.4 and later, and most commits to XFree86 CVS after
2004-02-12, are under the XFree86 1.1 license. Debian unfortunately cannot
accept such patches. The reasons for this are discussed at length in the
Debian X FAQ, in the entry "What is the story with XFree86's license?"
We appreciate your patience with this message. By following the above
guidelines, you can help Debian help our users more effectively.
--===============1764217192==--
---------------------------------------
Received: (at 294697-close) by bugs.debian.org; 10 May 2005 22:54:27 +0000
>From [EMAIL PROTECTED] Tue May 10 15:54:27 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DVdcR-0004cT-00; Tue, 10 May 2005 15:54:27 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DVdVk-0003AP-00; Tue, 10 May 2005 18:47:32 -0400
From: Chris Lawrence <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#294697: fixed in reportbug 3.12
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 10 May 2005 18:47:32 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 5
Source: reportbug
Source-Version: 3.12
We believe that the bug you reported is fixed in the latest version of
reportbug, which is due to be installed in the Debian FTP archive:
reportbug_3.12.dsc
to pool/main/r/reportbug/reportbug_3.12.dsc
reportbug_3.12.tar.gz
to pool/main/r/reportbug/reportbug_3.12.tar.gz
reportbug_3.12_all.deb
to pool/main/r/reportbug/reportbug_3.12_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lawrence <[EMAIL PROTECTED]> (supplier of updated reportbug package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 10 May 2005 17:24:01 -0500
Source: reportbug
Binary: reportbug
Architecture: source all
Version: 3.12
Distribution: unstable
Urgency: low
Maintainer: Chris Lawrence <[EMAIL PROTECTED]>
Changed-By: Chris Lawrence <[EMAIL PROTECTED]>
Description:
reportbug - reports bugs in the Debian distribution
Closes: 289228 294697 294822 296421 297998 299172 299425 306370 306955 308293
308543
Changes:
reportbug (3.12) unstable; urgency=low
.
* Really install French man page. (Closes: #297998)
* Add Japanese man page, from Ippei Tamura. (Closes: #306955)
* Fix typo in querybts man page. (Closes: #306370)
* Include /bin/sh symlink's target. (Closes: #296421)
* Send presubj messages through the pager. (Closes: #294697)
* Add upgrade-reports pseudo package. (Closes: #294822)
* Add 'q' to the editor prompt. (Closes: #299425)
* Use dlocate if available instead of dpkg --search. (Closes: #289228)
* Nag novice users if they use vi. (Closes: #299172)
* When calling an MTA, separate addresses with spaces rather than
commas. (Closes: #308293, #308543)
Files:
14965f94ab221b391aae91fb66fe07ef 522 utils standard reportbug_3.12.dsc
ed9d5aac5cab93cb69ef9db82839ffdb 135069 utils standard reportbug_3.12.tar.gz
f72e2ea0f6ade776c3913dccd9a8899f 125288 utils standard reportbug_3.12_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCgTTq2wQKE6PXubwRAvanAKDnJV8/vx5JeDc04r2gAWOpd0EYZACeKWNH
w/LX+ZF7JgKjdy4rMxvTIHA=
=kbtE
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
