Your message dated Sat, 16 May 2009 22:30:43 +0100
with message-id <200905162130.n4gluhm0017...@kmos.homeip.net>
and subject line xerces-j has been removed from Debian, closing #528081
has caused the Debian Bug report #528081,
regarding xerces-j: Please remove build-dep on jikes
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
528081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xerces-j
Version: 1.4.4-4
Severity: important

Hi,

jikes is orphaned, unmaintained, and buggy and therefore we are trying
to remove it from the archive.  xerces-j currently
build-depends on jikes.  Could you please try to build with one of the
other java compilers and remove the jikes build-depends? I've tried it with openjdk-6-jdk and it seems to work fairly well but does still have some issues.

Thank you,

Barry deFreese
Debian QA




--- End Message ---
--- Begin Message ---
Version: 1.4.4-4+rm

The xerces-j package has been removed from Debian so we are closing
the bugs that were still opened against it.

For more information about this package's removal, read
http://bugs.debian.org/528534 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.

Don't hesitate to reply to this mail if you have any question.

Thank you for your contribution to Debian.

Kind regards,
--
Marco Rodrigues


--- End Message ---
_______________________________________________
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Reply via email to