Your message dated Wed, 20 Jan 2016 19:19:05 +0000
with message-id <>
and subject line Bug#811466: Removed package(s) from unstable
has caused the Debian Bug report #800868,
regarding clojure1.2: depends on obsolete libasm3-java library
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: clojure1.2
Severity: important
Usertags: oldlibs libasm3-java


clojure1.2 depends on libasm3-java, which is obsolete and
incompatible with Java 8 which will be the new default in the near
future. clojure1.2 should be ported to the new libasm4-java version,
so that we can remove the old, unmaintained one.

Please try to do this before the Stretch release as we are going to
try to remove libasm3-java this cycle.

We will bump this issue to serious when the list of rdeps is small
and we are getting ready to remove libasm3-java completely.

If you have any questions don't hesitate to ask and contact us on



--- End Message ---
--- Begin Message ---
Version: 1.2.1+dfsg-5+rm

Dear submitter,

as the package clojure1.2 has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see

The version of this package that was in Debian prior to this removal
can still be found using

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

Debian distribution maintenance software
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
This is the maintainer address of Debian's Java team
Please use for discussions and questions.

Reply via email to