Bug#210060: marked as done (The package description does not follow Debian policy)
Your message dated Wed, 10 Sep 2003 08:27:43 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#210060: The package description does not follow Debian
policy
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 Sep 2003 22:25:28 +
>From [EMAIL PROTECTED] Tue Sep 09 17:25:26 2003
Return-path: <[EMAIL PROTECTED]>
Received: from dat.etsit.upm.es [138.100.17.73]
by master.debian.org with smtp (Exim 3.35 1 (Debian))
id 19wowJ-0006jg-00; Tue, 09 Sep 2003 15:18:15 -0500
Received: (qmail 7255 invoked by uid 1013); 9 Sep 2003 20:18:14 -
Date: Tue, 9 Sep 2003 22:18:14 +0200
From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: The package description does not follow Debian policy
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-8.0 required=4.0
tests=BAYES_01,HAS_PACKAGE,USER_AGENT_MUTT
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: libobjc1
Version: 1:3.3.1-0pre0
Severity: important
Justification: section 2.3.3
Your package does not comply with the policy as it does not provide
a proper extended descrition. Policy section 2.3.3 states:
The description should be written so that it gives the system
administrator enough information to decide whether to install the
package.
Take in account that package descriptions are very important to administrators
to determine wether a package is (or isn't) useful for them and are
used by package frontends in order to implement keyword-based searchs
(samples include command line tools such as 'apt-cache search X'
or 'grep-dctrl -F Description X' or even fancier interfaces such as
'dpkg-iasearch').
If you need help to provide a proper description for your package you
are advised to digest the README/manpages/HTML files provided by the package
or, as a last resort, request help at the debian-devel mailing list.
If this package is being generated from a single source package and
you already provide a full description in your control file for the
main package, you might want to use it automatically in sub-packages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the Debian Policy or the thread
at debian-devel started by
Message-ID: <[EMAIL PROTECTED]>
which is available at
http://lists.debian.org/debian-devel/2003/debian-devel-200306/msg01257.html
---
Received: (at 210060-done) by bugs.debian.org; 10 Sep 2003 06:28:05 +
>From [EMAIL PROTECTED] Wed Sep 10 01:27:55 2003
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19wySJ-Ln-00; Wed, 10 Sep 2003 01:27:55 -0500
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id IAA06993;
Wed, 10 Sep 2003 08:27:44 +0200 (MET DST)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.9+Sun/8.12.8/Submit) id h8A6RhSu009900;
Wed, 10 Sep 2003 08:27:43 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 10 Sep 2003 08:27:43 +0200
To: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Bug#210060: The package description does not follow Debian policy
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-14.5 required=4.0
tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_VM
autolearn=ham version=2.53-bugs.debian.org_2003_8_27
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debi
Bug#209829: marked as done (The package description does not follow Debian policy)
Your message dated Wed, 10 Sep 2003 08:29:39 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#209829: The package description does not follow Debian
policy
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 Sep 2003 21:27:35 +
>From [EMAIL PROTECTED] Tue Sep 09 16:27:33 2003
Return-path: <[EMAIL PROTECTED]>
Received: from dat.etsit.upm.es [138.100.17.73]
by master.debian.org with smtp (Exim 3.35 1 (Debian))
id 19woqv-0005kT-00; Tue, 09 Sep 2003 15:12:41 -0500
Received: (qmail 2230 invoked by uid 1013); 9 Sep 2003 20:12:40 -
Date: Tue, 9 Sep 2003 22:12:40 +0200
From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: The package description does not follow Debian policy
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-8.0 required=4.0
tests=BAYES_01,HAS_PACKAGE,USER_AGENT_MUTT
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: gcc-3.2
Version: 1:3.2.3-8
Severity: important
Justification: section 2.3.3
Your package does not comply with the policy as it does not provide
a proper extended descrition. Policy section 2.3.3 states:
The description should be written so that it gives the system
administrator enough information to decide whether to install the
package.
Take in account that package descriptions are very important to administrators
to determine wether a package is (or isn't) useful for them and are
used by package frontends in order to implement keyword-based searchs
(samples include command line tools such as 'apt-cache search X'
or 'grep-dctrl -F Description X' or even fancier interfaces such as
'dpkg-iasearch').
If you need help to provide a proper description for your package you
are advised to digest the README/manpages/HTML files provided by the package
or, as a last resort, request help at the debian-devel mailing list.
If this package is being generated from a single source package and
you already provide a full description in your control file for the
main package, you might want to use it automatically in sub-packages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the Debian Policy or the thread
at debian-devel started by
Message-ID: <[EMAIL PROTECTED]>
which is available at
http://lists.debian.org/debian-devel/2003/debian-devel-200306/msg01257.html
---
Received: (at 209829-done) by bugs.debian.org; 10 Sep 2003 06:32:54 +
>From [EMAIL PROTECTED] Wed Sep 10 01:32:52 2003
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19wyX6-pK-00; Wed, 10 Sep 2003 01:32:52 -0500
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id IAA07240;
Wed, 10 Sep 2003 08:29:39 +0200 (MET DST)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.9+Sun/8.12.8/Submit) id h8A6TdR6009939;
Wed, 10 Sep 2003 08:29:39 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 10 Sep 2003 08:29:39 +0200
To: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Bug#209829: The package description does not follow Debian policy
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-14.5 required=4.0
tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_VM
autolearn=ham version=2.53-bugs.debian.org_2003_8_27
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.or
Bug#210148: marked as done (The package description does not follow Debian policy)
Your message dated Wed, 10 Sep 2003 08:27:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#210148: The package description does not follow Debian
policy
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 Sep 2003 22:52:44 +
>From [EMAIL PROTECTED] Tue Sep 09 17:52:33 2003
Return-path: <[EMAIL PROTECTED]>
Received: from dat.etsit.upm.es [138.100.17.73]
by master.debian.org with smtp (Exim 3.35 1 (Debian))
id 19wour-0006XJ-00; Tue, 09 Sep 2003 15:16:45 -0500
Received: (qmail 5822 invoked by uid 1013); 9 Sep 2003 20:16:44 -
Date: Tue, 9 Sep 2003 22:16:44 +0200
From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: The package description does not follow Debian policy
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-8.0 required=4.0
tests=BAYES_01,HAS_PACKAGE,USER_AGENT_MUTT
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: libgcj-common
Version: 1:3.3.1-0pre0
Severity: important
Justification: section 2.3.3
Your package does not comply with the policy as it does not provide
a proper extended descrition. Policy section 2.3.3 states:
The description should be written so that it gives the system
administrator enough information to decide whether to install the
package.
Take in account that package descriptions are very important to administrators
to determine wether a package is (or isn't) useful for them and are
used by package frontends in order to implement keyword-based searchs
(samples include command line tools such as 'apt-cache search X'
or 'grep-dctrl -F Description X' or even fancier interfaces such as
'dpkg-iasearch').
If you need help to provide a proper description for your package you
are advised to digest the README/manpages/HTML files provided by the package
or, as a last resort, request help at the debian-devel mailing list.
If this package is being generated from a single source package and
you already provide a full description in your control file for the
main package, you might want to use it automatically in sub-packages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the Debian Policy or the thread
at debian-devel started by
Message-ID: <[EMAIL PROTECTED]>
which is available at
http://lists.debian.org/debian-devel/2003/debian-devel-200306/msg01257.html
---
Received: (at 210148-done) by bugs.debian.org; 10 Sep 2003 06:28:09 +
>From [EMAIL PROTECTED] Wed Sep 10 01:27:57 2003
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19wySL-Ln-00; Wed, 10 Sep 2003 01:27:57 -0500
Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id IAA06936;
Wed, 10 Sep 2003 08:27:15 +0200 (MET DST)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.9+Sun/8.12.8/Submit) id h8A6REp1009893;
Wed, 10 Sep 2003 08:27:14 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 10 Sep 2003 08:27:14 +0200
To: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Bug#210148: The package description does not follow Debian policy
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-14.5 required=4.0
tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_VM
autolearn=ham version=2.53-bugs.debian.org_2003_8_27
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs
gcc-snapshot_20030909-1_i386.changes ACCEPTED
Accepted: gcc-snapshot_20030909-1.diff.gz to pool/main/g/gcc-snapshot/gcc-snapshot_20030909-1.diff.gz gcc-snapshot_20030909-1.dsc to pool/main/g/gcc-snapshot/gcc-snapshot_20030909-1.dsc gcc-snapshot_20030909-1_i386.deb to pool/main/g/gcc-snapshot/gcc-snapshot_20030909-1_i386.deb gcc-snapshot_20030909.orig.tar.gz to pool/main/g/gcc-snapshot/gcc-snapshot_20030909.orig.tar.gz Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian.
gcc-snapshot_20030909-1_hppa.changes ACCEPTED
Accepted: gcc-snapshot_20030909-1_hppa.deb to pool/main/g/gcc-snapshot/gcc-snapshot_20030909-1_hppa.deb Thank you for your contribution to Debian.
Bug#210328: gcc-snapshot: SIGSEV in compiler with -pg flags
Package: gcc-snapshot
Version: 20030909-1
Severity: normal
The following code causes the compiler to SIGSEV in x86:
tst.cpp /
#include
class A;
std::vector < A * > getA()
{
std::vector< A * > a;
return a;
}
//
Compiling with:
$ /usr/lib/gcc-snapshot/bin/g++ -c -pg -c tst.cpp
tst.cpp: In function `std::vector > getA()':
tst.cpp:9: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
Compiling without the "-pg" switch works.
Thanks,
Daniel.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux pcdaniel 2.4.21-5-k7 #1 Mon Aug 25 08:09:01 EST 2003 i686
Locale: LANG=en_US.ISO-8859-1, LC_CTYPE=en_US.ISO-8859-1
Versions of some packages gcc-snapshot depends on:
ii binutils 2.14.90.0.5-0.2 The GNU assembler, linker and bina
ii libc62.3.2-6 GNU C Library: Shared libraries an
ii zlib1g 1:1.1.4-14 compression library - runtime
-- no debconf information
Results for 3.4 20030909 (experimental) testsuite on hppa-unknown-linux-gnu
LAST_UPDATED: Tue Sep 9 20:18:37 UTC 2003 Native configuration is hppa-unknown-linux-gnu === g++ tests === Running target unix XPASS: g++.dg/ext/lvalue1.C not an lvalue (test for errors, line 7) FAIL: g++.dg/ext/pretty1.C scan-assembler top level FAIL: g++.dg/ext/pretty2.C (test for excess errors) WARNING: g++.dg/ext/pretty2.C compilation failed to produce executable FAIL: g++.dg/init/array10.C (test for excess errors) XPASS: g++.dg/other/packed1.C execution test WARNING: g++.old-deja/g++.mike/p10769a.C compilation failed to produce executable WARNING: g++.old-deja/g++.other/enum5.C compilation failed to produce executable XPASS: g++.old-deja/g++.other/init5.C execution test WARNING: g++.old-deja/g++.pt/friend44.C compilation failed to produce executable === g++ Summary === # of expected passes8924 # of unexpected failures3 # of unexpected successes 3 # of expected failures 62 # of unsupported tests 61 /build/packages/gcc/snap/gcc-snapshot-20030909/build/gcc/testsuite/../g++ version 3.4 20030909 (experimental) === g77 tests === Running target unix FAIL: g77.f-torture/execute/980520-1.f compilation, -O0 === g77 Summary === # of expected passes1752 # of unexpected failures1 # of untested testcases 1 # of unsupported tests 6 /build/packages/gcc/snap/gcc-snapshot-20030909/build/gcc/testsuite/../g77 version 3.4 20030909 (experimental) === gcc tests === Running target unix FAIL: gcc.c-torture/compile/2120-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/execute/20030307-1.c execution, -O2 FAIL: gcc.c-torture/execute/20030307-1.c execution, -Os UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O0 UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O1 UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O2 UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O3 -fomit-frame-pointer UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O3 -g UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -Os FAIL: gcc.dg/compat/vector-2 c_compat_x_tst.o compile FAIL: gcc.dg/compat/vector-2 c_compat_y_tst.o compile UNRESOLVED: gcc.dg/compat/vector-2 c_compat_x_tst.o-c_compat_y_tst.o link UNRESOLVED: gcc.dg/compat/vector-2 c_compat_x_tst.o-c_compat_y_tst.o execute FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/debug-1.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-1.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-1.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-1.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-1.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-1.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-2.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-2.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-2.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-2.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-2.c scan-assembler xyzzy FAIL: gcc.dg/debug/debug-2.c scan-assembler xyzzy FAIL: gcc.dg/const-elim-1.c scan-assembler-not L\\\$?C[^A-Z] === gcc Summary === # of expected passes23806 # of unexpected failures35 # of expected failures 79 # of unresolved testcases 8 # of untested testcases 7 # of unsupported tests 266 /build/packages/gcc/snap/gcc-snapshot-20030909/build/gcc/xgcc version 3.4 20030909 (experimental) === objc tests === Running target unix FAIL: objc/execute/formal_protocol-1.m compilation, -O3 -fomit-frame-pointer UNRESOLVED: objc/execute/formal_protocol-1.m execution, -O3 -fomit-frame-pointer FAIL: objc/execute/formal_protocol-1.m compilation, -O3 -g UNRESOLVED: objc/execute/formal_protocol-1.m execution, -O3 -g FAIL: objc/execute/formal_protocol-2.m compilation, -O3 -fomit-frame-pointer UNRESOLVED: objc/execute/formal_protocol-2.m execution, -O3 -fomit-frame-pointer FAIL: objc/execute/fo
Results for 3.3.2 20030908 (Debian prerelease) testsuite on sparc-unknown-linux-gnu
LAST_UPDATED: Mon Sep 8 19:46:09 UTC 2003 Native configuration is sparc-unknown-linux-gnu === g++ tests === Running target unix XPASS: g++.other/init5.C Execution test === g++ Summary === # of expected passes8059 # of unexpected successes 1 # of expected failures 95 # of untested testcases 22 # of unsupported tests 27 /build/buildd/gcc-3.3-3.3.2ds2/build/gcc/testsuite/../g++ version 3.3.2 20030908 (Debian prerelease) === g77 tests === Running target unix === g77 Summary === # of expected passes1686 # of unsupported tests 8 /build/buildd/gcc-3.3-3.3.2ds2/build/gcc/testsuite/../g77 version 3.3.2 20030908 (Debian prerelease) === gcc tests === Running target unix FAIL: gcc.dg/duff-2.c (test for excess errors) === gcc Summary === # of expected passes21377 # of unexpected failures1 # of expected failures 67 # of unsupported tests 164 /build/buildd/gcc-3.3-3.3.2ds2/build/gcc/xgcc version 3.3.2 20030908 (Debian prerelease) === objc tests === Running target unix === objc Summary === # of expected passes1153 /build/buildd/gcc-3.3-3.3.2ds2/build/gcc/xgcc version 3.3.2 20030908 (Debian prerelease) === treelang tests === Running target unix === treelang Summary === # of expected passes1 === libjava tests === Running target unix FAIL: SyncTest execution - gij test WARNING: program timed out. FAIL: SyncTest execution - bytecode->native test FAIL: SyncTest execution - gij test WARNING: program timed out. FAIL: SyncTest -O execution - bytecode->native test === libjava Summary === # of expected passes2983 # of unexpected failures4 # of expected failures 16 # of untested testcases 16 === libstdc++-v3 check-abi Summary === # of added symbols: 0 # of missing symbols:134 # of incompatible symbols: 134 using: /build/buildd/gcc-3.3-3.3.2ds2/src/libstdc++-v3/config/abi/sparc-linux-gnu/baseline_symbols.txt === libstdc++-v3 tests === Running target unix XPASS: 22_locale/collate_byname.cc execution test XPASS: 22_locale/collate_members_char.cc execution test XPASS: 22_locale/collate_members_wchar_t.cc execution test XPASS: 22_locale/ctype_is_char.cc execution test XPASS: 22_locale/ctype_is_wchar_t.cc execution test XPASS: 22_locale/members.cc execution test XPASS: 22_locale/messages_byname.cc execution test XPASS: 22_locale/messages_members_char.cc execution test XPASS: 22_locale/moneypunct_byname.cc execution test XPASS: 22_locale/moneypunct_members_char.cc execution test XPASS: 22_locale/moneypunct_members_wchar_t.cc execution test XPASS: 22_locale/numpunct_byname.cc execution test XPASS: 22_locale/numpunct_members_char.cc execution test XPASS: 22_locale/numpunct_members_wchar_t.cc execution test === libstdc++-v3 Summary === # of expected passes453 # of unexpected successes 14 # of expected failures 14 Compiler version: 3.3.2 20030908 (Debian prerelease) Platform: sparc-unknown-linux-gnu configure flags: --host=sparc-linux -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --with-cpu=v7 --enable-objc-gc BOOT_CFLAGS=-g -O2 Build Dependencies: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii binutils 2.14.90.0.5-0. The GNU assembler, linker and binary utiliti ii libc6-dev 2.3.2-5GNU C Library: Development Libraries and Hea Patches that Debian applied in this version: gcc-names: versioned gcc names gcc-version: Add "(Debian)" to the gcc version string libstdc++-pic: Build and install libstdc++_pic.a library. libstdc++-doclink: link local libstdc++ documentation to local source-level documentation gccbug: Use sensible-editor instead of vi as fallback editor libtool-rpath: 2003-03-10 Andreas Schwab With the introduction of multi-os-directory the libdir specification in *.la files have /. appended to \$(libdir). This confuses libtool when it tries to find out whether to add -rpath, because it only matches literally against sys_lib_dlsearch_path members. Tested on i386-linux. mips-branch-fix: Fix #207915 (PR1171
Results for 3.4 20030909 (experimental) testsuite on i486-pc-linux-gnu
LAST_UPDATED: Tue Sep 9 20:18:37 UTC 2003 Native configuration is i486-pc-linux-gnu === g++ tests === Running target unix XPASS: g++.dg/ext/lvalue1.C not an lvalue (test for errors, line 7) FAIL: g++.dg/ext/pretty1.C scan-assembler top level FAIL: g++.dg/ext/pretty2.C (test for excess errors) WARNING: g++.dg/ext/pretty2.C compilation failed to produce executable FAIL: g++.dg/init/array10.C (test for excess errors) WARNING: g++.old-deja/g++.mike/p10769a.C compilation failed to produce executable WARNING: g++.old-deja/g++.other/enum5.C compilation failed to produce executable XPASS: g++.old-deja/g++.other/init5.C execution test WARNING: g++.old-deja/g++.pt/friend44.C compilation failed to produce executable === g++ Summary === # of expected passes9007 # of unexpected failures3 # of unexpected successes 2 # of expected failures 62 # of unsupported tests 29 /build/packages/gcc/snap/gcc-snapshot-20030909/build/gcc/testsuite/../g++ version 3.4 20030909 (experimental) === g77 tests === Running target unix FAIL: g77.f-torture/execute/980520-1.f compilation, -O0 === g77 Summary === # of expected passes1752 # of unexpected failures1 # of untested testcases 1 # of unsupported tests 6 /build/packages/gcc/snap/gcc-snapshot-20030909/build/gcc/testsuite/../g77 version 3.4 20030909 (experimental) === gcc tests === Running target unix FAIL: gcc.c-torture/compile/2120-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O0 UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O1 UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O2 UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O3 -fomit-frame-pointer UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O3 -g UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -Os FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/const-elim-1.c scan-assembler-not L\\\$?C[^A-Z] === gcc Summary === # of expected passes24180 # of unexpected failures19 # of expected failures 81 # of unresolved testcases 6 # of untested testcases 7 # of unsupported tests 142 /build/packages/gcc/snap/gcc-snapshot-20030909/build/gcc/xgcc version 3.4 20030909 (experimental) === objc tests === Running target unix === objc Summary === # of expected passes1156 /build/packages/gcc/snap/gcc-snapshot-20030909/build/gcc/xgcc version 3.4 20030909 (experimental) === treelang tests === Running target unix === treelang Summary === # of expected passes1 === libffi tests === Running target unix FAIL: libffi.call/cls_1_1byte.c execution test FAIL: libffi.call/cls_2byte.c execution test FAIL: libffi.call/cls_3_1byte.c execution test FAIL: libffi.call/cls_5byte.c execution test FAIL: libffi.call/cls_6byte.c execution test FAIL: libffi.call/pyobjc-tc.c execution test === libffi Summary === # of expected passes114 # of unexpected failures6 # of unsupported tests 2 === libjava tests === Running target unix FAIL: SyncGlobal -O3 execution - bytecode->native test === libjava Summary === # of expected passes3090 # of unexpected failures1 # of expected failures 10 # of untested testcases 9 === libstdc++-v3 check-abi Summary === # of added symbols: 131 # of missing symbols:192 # of incompatible symbols: 196 using: /build/packages/gcc/snap/gcc-snapshot-20030909/src/libstdc++-v3/config/abi/i486-linux-gnu/baseline_symbols.txt === libstdc++ tests === Running target unix FAIL: 22_locale/time_put/put/char/2.cc execution test FAIL:
Results for 3.4 20030909 (experimental) testsuite on alpha-unknown-linux-gnu
LAST_UPDATED: Tue Sep 9 20:18:37 UTC 2003 Native configuration is alpha-unknown-linux-gnu === libffi tests === Running target unix FAIL: libffi.call/pyobjc-tc.c execution test === libffi Summary === # of expected passes124 # of unexpected failures1 # of unsupported tests 2 === libjava tests === Running target unix FAIL: ArrayStore execution - gij test FAIL: ArrayStore execution - gij test FAIL: ArrayStore2 execution - gij test FAIL: ArrayStore2 execution - gij test FAIL: Array_1 execution - gij test FAIL: Array_1 execution - gij test FAIL: Array_2 execution - gij test FAIL: Array_2 execution - gij test FAIL: Array_3 execution - gij test FAIL: Array_3 execution - gij test FAIL: Class_1 execution - gij test FAIL: Class_1 execution - gij test FAIL: CompareNaN execution - gij test FAIL: CompareNaN execution - gij test FAIL: Divide_1 execution - gij test FAIL: Divide_1 execution - gij test FAIL: EvaluationOrder execution - gij test FAIL: EvaluationOrder execution - gij test FAIL: FileHandleGcTest execution - gij test FAIL: FileHandleGcTest execution - gij test FAIL: Final execution - gij test FAIL: Final execution - gij test FAIL: Float_1 execution - gij test FAIL: Float_1 execution - gij test FAIL: G19990301_01 execution - gij test FAIL: G19990301_01 execution - gij test FAIL: G19990302_02 execution - gij test FAIL: G19990302_02 execution - gij test FAIL: G19990303_01 execution - gij test FAIL: G19990303_01 execution - gij test FAIL: G19990303_02 execution - gij test FAIL: G19990303_02 execution - gij test FAIL: G19990304_01 execution - gij test FAIL: G19990304_01 execution - gij test FAIL: G19990310_01 execution - gij test FAIL: G19990310_01 execution - gij test FAIL: II execution - gij test FAIL: II execution - gij test FAIL: InterfaceDispatch execution - gij test FAIL: InterfaceDispatch execution - gij test FAIL: InvokeReturn execution - gij test FAIL: InvokeReturn execution - gij test FAIL: Invoke_1 execution - gij test FAIL: Invoke_1 execution - gij test FAIL: Invoke_2 execution - gij test FAIL: Invoke_2 execution - gij test FAIL: KeepInline execution - gij test FAIL: KeepInline execution - gij test FAIL: MathBuiltin execution - gij test FAIL: MathBuiltin execution - gij test FAIL: Matrix4f execution - gij test FAIL: Matrix4f execution - gij test FAIL: N19990310_02 execution - gij test FAIL: N19990310_02 execution - gij test FAIL: N19990310_3 execution - gij test FAIL: N19990310_3 execution - gij test FAIL: N19990310_4 execution - gij test FAIL: N19990310_4 execution - gij test FAIL: N19990310_5 execution - gij test FAIL: N19990310_5 execution - gij test FAIL: Overflow execution - gij test FAIL: Overflow execution - gij test FAIL: PR141 execution - gij test FAIL: PR141 execution - gij test FAIL: PR160 execution - gij test FAIL: PR160 execution - gij test FAIL: PR162 execution - gij test FAIL: PR162 execution - gij test FAIL: PR218 execution - gij test FAIL: PR218 execution - gij test FAIL: PR242 execution - gij test FAIL: PR242 execution - gij test FAIL: PR260 execution - gij test FAIL: PR260 execution - gij test FAIL: PR3096 execution - gij test FAIL: PR3096 execution - gij test FAIL: PR3731 execution - gij test FAIL: PR3731 execution - gij test FAIL: PR5057 execution - gij test FAIL: PR5057 execution - gij test FAIL: PR5057_2 execution - gij test FAIL: PR5057_2 execution - gij test FAIL: PR55 execution - gij test FAIL: PR55 execution - gij test FAIL: PR56 execution - gij test FAIL: PR56 execution - gij test FAIL: PR6085 execution - gij test FAIL: PR6085 execution - gij test FAIL: PR6204 execution - gij test FAIL: PR6204 execution - gij test FAIL: PR6729 execution - gij test FAIL: PR6729 execution - gij test FAIL: PR6820 execution - gij test FAIL: PR6820 execution - gij test FAIL: PR7482 execution - gij test FAIL: PR7482 execution - gij test FAIL: Shazam execution - gij test FAIL: Shazam execution - gij test FAIL: StaticConstructor execution - gij test FAIL: StaticConstructor execution - gij test FAIL: StringBuffer_1 execution - gij test FAIL: StringBuffer_1 execution - gij test FAIL: SyncGlobal execution - gij test FAIL: SyncGlobal execution - gij test FAIL: SyncTest execution - gij test FAIL: SyncTest execution - gij test FAIL: Synch execution - gij test FAIL: Synch execution - gij test FAIL: TLtest execution - gij test FAIL: TLtest execution - gij test FAIL: TestProxy execution - source compiled test FAIL: TestProxy execution - gij test FAIL: TestProxy execution - bytecode->native test FAIL: TestProxy -O3 execution - source compiled test FAIL: TestProxy execution - gij test FAIL: TestProxy -O3 execution - bytecode->native test FAIL: Thread_Alive execution - gij test FAIL: Thread_Alive execution - gij test FAIL: Thread_Interrupt execution - gij test FAIL: Thread_Interrupt execution - gij test FAIL: Thread_Join execution - gij test FAIL: Thread_Join execution - gij test FAIL: Thread_Monitor execution - gij test FAIL: T
Results for 3.4 20030909 (experimental) testsuite on powerpc-unknown-linux-gnu
LAST_UPDATED: Tue Sep 9 20:18:37 UTC 2003 Native configuration is powerpc-unknown-linux-gnu === g++ tests === Running target unix XPASS: g++.dg/ext/lvalue1.C not an lvalue (test for errors, line 7) FAIL: g++.dg/ext/pretty1.C scan-assembler top level FAIL: g++.dg/ext/pretty2.C (test for excess errors) WARNING: g++.dg/ext/pretty2.C compilation failed to produce executable FAIL: g++.dg/init/array10.C (test for excess errors) XPASS: g++.dg/other/packed1.C execution test WARNING: g++.old-deja/g++.mike/p10769a.C compilation failed to produce executable WARNING: g++.old-deja/g++.other/enum5.C compilation failed to produce executable XPASS: g++.old-deja/g++.other/init5.C execution test WARNING: g++.old-deja/g++.pt/friend44.C compilation failed to produce executable === g++ Summary === # of expected passes8947 # of unexpected failures3 # of unexpected successes 3 # of expected failures 62 # of unsupported tests 60 /build/buildd/gcc-snapshot-20030909/build/gcc/testsuite/../g++ version 3.4 20030909 (experimental) === g77 tests === Running target unix FAIL: 238:is -:should be 3 FAIL: 242:is -:should be 9 FAIL: 241: expected branch percentages not found: 25 FAIL: g77.dg/gcov/gcov-1.f gcov: 2 failures in line counts, 1 in branch percentages, 0 in return percentages FAIL: g77.f-torture/execute/980520-1.f compilation, -O0 === g77 Summary === # of expected passes1751 # of unexpected failures5 # of untested testcases 1 # of unsupported tests 6 /build/buildd/gcc-snapshot-20030909/build/gcc/testsuite/../g77 version 3.4 20030909 (experimental) === gcc tests === Running target unix FAIL: gcc.c-torture/compile/2120-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-1.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/compile/2009-2.c (test for excess errors) FAIL: gcc.c-torture/execute/20030125-1.c execution, -O1 FAIL: gcc.c-torture/execute/20030125-1.c execution, -O2 FAIL: gcc.c-torture/execute/20030125-1.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/20030125-1.c execution, -O3 -g FAIL: gcc.c-torture/execute/20030125-1.c execution, -Os UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O0 UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O1 UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O2 UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O3 -fomit-frame-pointer UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -O3 -g UNRESOLVED: gcc.c-torture/execute/wchar_t-1.c execution, -Os FAIL: gcc.dg/compat/scalar-by-value-3 c_compat_x_tst.o-c_compat_y_tst.o execute FAIL: gcc.dg/compat/scalar-return-3 c_compat_x_tst.o-c_compat_y_tst.o execute FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/debug/20010207-1.c (test for excess errors) FAIL: gcc.dg/20020103-1.c scan-assembler-not LC FAIL: gcc.dg/20020118-1.c execution test FAIL: gcc.dg/altivec-5.c (test for excess errors) FAIL: gcc.dg/builtins-18.c (test for excess errors) FAIL: gcc.dg/builtins-20.c (test for excess errors) FAIL: gcc.dg/ppc-sdata-1.c scan-assembler [EMAIL PROTECTED](13\\) FAIL: gcc.dg/ppc-sdata-1.c scan-assembler [EMAIL PROTECTED](2\\) === gcc Summary === # of expected passes23912 # of unexpected failures32 # of expected failures 80 # of unresolved testcases 6 # of untested testcases 7 # of unsupported tests 240 /build/buildd/gcc-snapshot-20030909/build/gcc/xgcc version 3.4 20030909 (experimental) === objc tests === Running target unix === objc Summary === # of expected passes1156 /build/buildd/gcc-snapshot-20030909/build/gcc/xgcc version 3.4 20030909 (experimental) === treelang tests === Running target unix === treelang Summary === # of expected passes1 === libffi tests === Running target unix FAIL: libffi.call/pyobjc-tc.c execution test === libffi Summary === # of expected passes
[Bug optimization/11319] [3.3/3.4 regression] loop miscompiled on ppc32
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11319 wilson at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From wilson at gcc dot gnu dot org 2003-09-11 00:59 --- I have now run SPEC on a PowerMac G5. The only noticable performance change I see is a 3% improvement in mesa with my patches, but 3% is small enough that it could be within my measurement error. David Edelsohn has agreed that my patches did not introduce performance regressions. See http://gcc.gnu.org/ml/gcc/2003-09/msg00377.html So I am not closing this problem report. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
Bug#209633: marked as done (The package description does not follow Debian policy)
Your message dated Wed, 10 Sep 2003 22:16:02 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#209633: The package description does not follow Debian
policy
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 Sep 2003 20:27:59 +
>From [EMAIL PROTECTED] Tue Sep 09 15:13:16 2003
Return-path: <[EMAIL PROTECTED]>
Received: from dat.etsit.upm.es [138.100.17.73]
by master.debian.org with smtp (Exim 3.35 1 (Debian))
id 19worU-0005u6-00; Tue, 09 Sep 2003 15:13:16 -0500
Received: (qmail 2747 invoked by uid 1013); 9 Sep 2003 20:13:15 -
Date: Tue, 9 Sep 2003 22:13:15 +0200
From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: The package description does not follow Debian policy
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-8.0 required=4.0
tests=BAYES_20,HAS_PACKAGE,USER_AGENT_MUTT
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: gnat-3.3-doc
Version: 1:3.3.1-0pre0
Severity: important
Justification: section 2.3.3
Your package does not comply with the policy as it does not provide
a proper extended descrition. Policy section 2.3.3 states:
The description should be written so that it gives the system
administrator enough information to decide whether to install the
package.
Take in account that package descriptions are very important to administrators
to determine wether a package is (or isn't) useful for them and are
used by package frontends in order to implement keyword-based searchs
(samples include command line tools such as 'apt-cache search X'
or 'grep-dctrl -F Description X' or even fancier interfaces such as
'dpkg-iasearch').
If you need help to provide a proper description for your package you
are advised to digest the README/manpages/HTML files provided by the package
or, as a last resort, request help at the debian-devel mailing list.
If this package is being generated from a single source package and
you already provide a full description in your control file for the
main package, you might want to use it automatically in sub-packages. If this
is the case consider using ${description}, and debian/substvars.
This report has been automatically generated and the main reason is that
the package has an extended description which is only one line long.
Regards
Javier Fernandez-Sanguino
PS: For more information please read the Debian Policy or the thread
at debian-devel started by
Message-ID: <[EMAIL PROTECTED]>
which is available at
http://lists.debian.org/debian-devel/2003/debian-devel-200306/msg01257.html
---
Received: (at 209633-done) by bugs.debian.org; 11 Sep 2003 02:16:05 +
>From [EMAIL PROTECTED] Wed Sep 10 21:16:03 2003
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-172-017.pit1.dsl.speakeasy.net (nevyn.them.org)
[66.93.172.17]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19xH06-0006Uo-00; Wed, 10 Sep 2003 21:16:02 -0500
Received: from drow by nevyn.them.org with local (Exim 4.22 #1 (Debian))
id 19xH06-0006F7-BC; Wed, 10 Sep 2003 22:16:02 -0400
Date: Wed, 10 Sep 2003 22:16:02 -0400
From: Daniel Jacobowitz <[EMAIL PROTECTED]>
To: Matthias Klose <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#209633: The package description does not follow Debian policy
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.1i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-15.5 required=4.0
tests=BAYES_30,EMAIL_ATTRIBUTION,IN_REP_TO,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)
On Wed, Sep 10, 2003 at 12:19:57AM +0200, Matthias Klose wrote:
> Javier Fernández-Sanguino Peña writes:
> > Package: gnat-3.3-doc
> > Version: 1:3.3.1-0pre0
> > Severity: important
