Your message dated Fri, 18 Aug 2006 08:23:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368967: fixed
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: libgcj6-dev
Version: 4.0.2-5j2
Severity: normal

This package installs jni.h in /usr/lib/gcc/i486-linux-gnu/4.0.3/include/.
This only works if you happen to use gcc 4.0.3 to compile the C program
you're dealing with, but my gcc thinks it's version 4.0.4:

$ gcc -print-search-dirs
install: /usr/lib/gcc/i486-linux-gnu/4.0.4/
programs: 
=/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/:/usr/libexec/gcc/i486-linux-gnu/4.0.4/:/usr/libexec/gcc/i486-linux-gnu/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/bin/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/bin/
libraries: 
=/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/lib/i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../i486-linux-gnu/lib/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../i486-linux-gnu/4.0.4/:/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../:/lib/i486-linux-gnu/4.0.4/:/lib/:/usr/lib/i486-linux-gnu/4.0.4/:/usr/lib/

Since gcj-x.y and gcc-x.y are different source packages, you are bound
to have this sort of descrepancy once in a while.

In order to allow packages to use the JNI interface without breaking
every so often, the header files need to be placed in a directory where
every compiler can find them.


--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

   gcj-4.0 |    4.0.3-2 | source, alpha, amd64, arm, hppa, i386, ia64, m68k, 
mips, mipsel, powerpc, s390, sparc
gcj-4.0-base |    4.0.3-2 | alpha, amd64, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, s390, sparc
   gij-4.0 |    4.0.3-2 | alpha, amd64, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, s390, sparc
   libgcj6 |    4.0.3-2 | alpha, amd64, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, s390, sparc
libgcj6-awt |    4.0.3-2 | alpha, amd64, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, s390, sparc
libgcj6-dbg |    4.0.3-2 | alpha, amd64, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, s390, sparc
libgcj6-dev |    4.0.3-2 | alpha, amd64, arm, hppa, i386, ia64, m68k, mips, 
mipsel, powerpc, s390, sparc
libgcj6-jar |    4.0.3-2 | all
libgcj6-src |    4.0.3-2 | all

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED]

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[EMAIL PROTECTED]

Debian distribution maintenance software
pp.
Jeroen van Wolffelaar (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to