Possible problems in your Debian packages

Mon Jun 2 08:26:20 UTC 2008

=== cacao:
= 3 bug(s) that should be fixed for the next Debian release:
- #441122 <http://bugs.debian.org/441122>
  cacao - FTBFS: undefined reference to `__data_start'
- #458631 <http://bugs.debian.org/458631>
  cacao: FTBFS: error: variable _Jv_JNIInvokeInterface has initializer but incomplete type [fixed in experimental]
- #477854 <http://bugs.debian.org/477854>
  cacao: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
= Not in testing for 537 days.
  If things don't change, it won't be part of lenny!
  See <http://release.debian.org/migration/testing.pl?package=cacao>

=== cairo-java:
= No migration to testing for 34 days.
  See <http://release.debian.org/migration/testing.pl?package=cairo-java>

=== commons-daemon:
= No migration to testing for 34 days.
  See <http://release.debian.org/migration/testing.pl?package=commons-daemon>

=== eclipse:
= 1 bug(s) that should be fixed for the next Debian release:
- #483279 <http://bugs.debian.org/483279>
  tuxguitar_0.9.99~1.0rc4-1(ia64/unstable): FTBFS: compile errors

=== eclipse-cdt:
= 1 bug(s) that should be fixed for the next Debian release:
- #432541 <http://bugs.debian.org/432541>
  eclipse-cdt FTBFS
= Not in testing for 140 days.
  If things don't change, it won't be part of lenny!
  See <http://release.debian.org/migration/testing.pl?package=eclipse-cdt>

=== eclipse-pydev:
= 1 bug(s) that should be fixed for the next Debian release:
- #480693 <http://bugs.debian.org/480693>
  eclipse-pydev: FTBFS: tries to write in $HOME
= Not in testing for 219 days.
  If things don't change, it won't be part of lenny!
  See <http://release.debian.org/migration/testing.pl?package=eclipse-pydev>

=== glib-java:
= No migration to testing for 36 days.
  See <http://release.debian.org/migration/testing.pl?package=glib-java>

=== java-access-bridge:
= 1 bug(s) that should be fixed for the next Debian release:
- #474890 <http://bugs.debian.org/474890>
  java-access-bridge: FTBFS: Nonexistent build-dependency: openjdk-6-jdk
= Not in testing for 57 days.
  If things don't change, it won't be part of lenny!
  See <http://release.debian.org/migration/testing.pl?package=java-access-bridge>

=== java-gnome:
= Not in testing for 1087 days.
  If things don't change, it won't be part of lenny!
  See <http://release.debian.org/migration/testing.pl?package=java-gnome>

=== libgconf-java:
= No migration to testing for 36 days.
  See <http://release.debian.org/migration/testing.pl?package=libgconf-java>

=== libglade-java:
= No migration to testing for 35 days.
  See <http://release.debian.org/migration/testing.pl?package=libglade-java>

=== libgtk-java:
= No migration to testing for 34 days.
  See <http://release.debian.org/migration/testing.pl?package=libgtk-java>

=== libgui-commands-java:
= No migration to testing for 32 days.
  See <http://release.debian.org/migration/testing.pl?package=libgui-commands-java>

=== libjmathtex-java:
= No migration to testing for 32 days.
  See <http://release.debian.org/migration/testing.pl?package=libjmathtex-java>

=== libsaxon-java:
= No migration to testing for 54 days.
  See <http://release.debian.org/migration/testing.pl?package=libsaxon-java>

=== libswirl-java:
= No migration to testing for 32 days.
  See <http://release.debian.org/migration/testing.pl?package=libswirl-java>

=== libtritonus-java:
= No migration to testing for 37 days.
  See <http://release.debian.org/migration/testing.pl?package=libtritonus-java>

=== libvte-java:
= No migration to testing for 34 days.
  See <http://release.debian.org/migration/testing.pl?package=libvte-java>

=== libxmlrpc3-java:
= No migration to testing for 36 days.
  See <http://release.debian.org/migration/testing.pl?package=libxmlrpc3-java>

=== Packages with a new upstream version according to DEHS:
  antlr3  3.1b1  (Debian: 3.0.1+dfsg-2)
  cdk  1.0.3  (Debian: 1.0.2-2)
  commons-pool  1.4  (Debian: 1.3-1)
  eclipse  3.3.2  (Debian: 3.2.2-6)
  jarjar  1.0rc7  (Debian: 1.0~rc7.dfsg-2)
  jcifs  1.2.20  (Debian: 1.2.19-1)
  jcommon-serializer  0.3.0-rc  (Debian: 0.2.0-2)
  jsch  0.1.38  (Debian: 0.1.37-3)
  junit4  4.4  (Debian: 4.3.1-4)
  libcobra-java  0.98.2  (Debian: 0.98-1)
  libcommons-jexl-java  1.0-RC1  (Debian: 1.0-5)
  libfonts-java  0.4.0-rc  (Debian: 0.3.3-2)
  libformula  0.2.0-rc  (Debian: 0.1.14-1)
  libgettext-commons-java  0.9-src  (Debian: 0.9-1)
  libgnujaf-java  20040420  (Debian: 1.1.1-4)
  libjboss-profiler-java  2.0.Beta1  (Debian: 1.0.CR4-1)
  libjboss-vfs-java  2.0.0~Beta11  (Debian: 2.0.0~Beta10-1)
  libjdom-java  1.1  (Debian: 0.99.b10-6)
  libjgrapht-java  0.7.3  (Debian: 0.6.0-4)
  libjorbis-java  0.0.17  (Debian: 0.0.16-4)
  libloader  0.4.0-rc  (Debian: 0.3.6-3)
  liblogkit-java  2.0.dev-0  (Debian: 1.2.2-9)
  libpgjava  8.3-603  (Debian: 8.2-504-2)
  libpicocontainer-java  2.3  (Debian: 2.1-1)
  libswirl-java  1.1  (Debian: 1.0.13-3)
  maven2  2.0.9-RC8  (Debian: 2.0.9-1)
  pentaho-reporting-flow-engine  0.9.3  (Debian: 0.9.2-3)
  rhino  1.7R2pre  (Debian: 1.7R1-1)
  saxonb  9.0.0.5  (Debian: 9.0.0.4+svn20080322-1)
  statcvs  0.4.0  (Debian: 0.3.dfsg+1-1)

------------ interesting stuff probably ends here ------------
This is an automated mail. These mails are sent monthly.
For more information about these mails, refer to
http://wiki.debian.org/qa.debian.org/DdpoByMail

We are sorry if this mail was useless for you. If you think it was
avoidable (that we can detect easily that the problems weren't
actually problems), please reply to it and let us know.

If you don't want to receive this type of mail any more, you can reply
to this mail and use one of the following commands at the beginning of
the mail:
- unsubscribe <email>
You will no longer receive any mail for any package
- ignore <package> <email>
You will no longer receive information about that package in those
mails. So if that package is the only one with problems, you won't
receive anything.
- ignore <bug> <email>
You will no longer receive information about this bug.

All commands are manually processed, but you will receive
confirmation. The commands are just here so that we know precisely
what you want.

A more detailed status of your packages is available from the DDPO.
See: 
http://qa.debian.org/developer.php?login=pkg-java-maintainers@lists.alioth.debian.org

Don't hesitate to reply to this mail if you have questions. The wiki
page will be updated with useful information.
-- 
DDPOMail, run by Lucas Nussbaum