Your message dated Thu, 22 Jun 2006 03:32:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#345371: fixed in eclipse-cdt 3.0.1-3
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)
--- Begin Message ---
Package: eclipse-cdt
Version: 3.0.1-1
Severity: serious
Tags: patch
eclipse-cdt missed a build-depdendency on java-gcj-compat-dev:
From the powerpc buildd:
[...]
# build native code.
cd
source-tree/org.eclipse.cdt.releng/results/plugins/org.eclipse.cdt.core.linux/library
&& \
make ARCH=ppc CC='gcc -D_GNU_SOURCE'
make[1]: Entering directory
`/build/buildd/eclipse-cdt-3.0.1/source-tree/org.eclipse.cdt.releng/results/plugins/org.eclipse.cdt.core.linux/library'
Makefile:4: JAVA_HOME not set in environment
gcc -D_GNU_SOURCE -fpic -D_REENTRANT -D_GNU_SOURCE -I. -I/include
-I/include/linux -c -o spawner.o spawner.c
spawner.c:16:17: error: jni.h: No such file or directory
In file included from spawner.c:19:
./Spawner.h:15: error: syntax error before 'jint'
[...]
The build will fail later, though with
/home/rene/eclipse-cdt-3.0.1/source-tree/org.eclipse.cdt.releng/results/assemble.org.eclipse.cdt.linux.gtk.ppc.xml:101:
Execute failed: java.io.IOException: java.io.IOException: Cannot allocate
memory
but that seems another story, but if it fails on my iBook it probably
will do so on the ppc buildd, too...
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-powerpc
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: eclipse-cdt
Source-Version: 3.0.1-3
We believe that the bug you reported is fixed in the latest version of
eclipse-cdt, which is due to be installed in the Debian FTP archive:
eclipse-cdt_3.0.1-3.diff.gz
to pool/main/e/eclipse-cdt/eclipse-cdt_3.0.1-3.diff.gz
eclipse-cdt_3.0.1-3.dsc
to pool/main/e/eclipse-cdt/eclipse-cdt_3.0.1-3.dsc
eclipse-cdt_3.0.1-3_i386.deb
to pool/main/e/eclipse-cdt/eclipse-cdt_3.0.1-3_i386.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.
Michael Koch <[EMAIL PROTECTED]> (supplier of updated eclipse-cdt 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: Thu, 22 Jun 2006 09:36:48 +0000
Source: eclipse-cdt
Binary: eclipse-cdt
Architecture: source i386
Version: 3.0.1-3
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers
<pkg-java-maintainers@lists.alioth.debian.org>
Changed-By: Michael Koch <[EMAIL PROTECTED]>
Description:
eclipse-cdt - C/C++ Development Tools for Eclipse
Closes: 345371
Changes:
eclipse-cdt (3.0.1-3) unstable; urgency=low
.
* debian/rules: Adjusted for current eclipse (Closes: #345371).
* Updated Standards-Version to 3.7.2.
Files:
52f0f616dcba8f1689346b0aebe7fdc2 739 devel optional eclipse-cdt_3.0.1-3.dsc
550354665afb7df9835b2eecec9edd32 237739 devel optional
eclipse-cdt_3.0.1-3.diff.gz
779b1e0198ba45d590f69a6ab6b89845 17450864 devel optional
eclipse-cdt_3.0.1-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEmmuIWSOgCCdjSDsRAuTXAKCe37re4xN4BKomQTO1NpuzehOwLACeP1DK
VExb0NnSzphkjEbBZXJDtdQ=
=XxKT
-----END PGP SIGNATURE-----
--- End Message ---
