Your message dated Mon, 09 Mar 2020 23:50:01 +0000
with message-id <e1jbs9p-000bgk...@fasolo.debian.org>
and subject line Bug#953408: Removed package(s) from unstable
has caused the Debian Bug report #953408,
regarding RM: coq [armel armhf i386 mipsel mips64el s390x] -- ROM; FTBFS 
(mostly on 32bit architectures, or where ocaml has only a bytecode compiler)
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.)


-- 
953408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal

Hi, recent coq has testsuite failures on many architectures, mostly
due to a problem with coq/ocaml on 32bit architectures. This is
currently being investigated by upstream, but will take some time.
OTOH, it is time to move on to coq 8.11.0 as this version is build
against lablgtk3 (previous versions vhere build against lablgtk2).

Thanks -Ralf.

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

       coq | 8.9.1-5+b1 | armel, armhf, i386, mips64el, mipsel, s390x
coq-theories | 8.9.1-5+b1 | armel, armhf, i386, mips64el, mipsel, s390x
    coqide | 8.9.1-5+b1 | armel, armhf, i386, mips64el, mipsel, s390x
libcoq-ocaml | 8.9.1-5+b1 | armel, armhf, i386, mips64el, mipsel, s390x
libcoq-ocaml-dev | 8.9.1-5+b1 | armel, armhf, i386, mips64el, mipsel, s390x

------------------- Reason -------------------
ROM; FTBFS (mostly on 32bit architectures, or where ocaml has only a bytecode 
compiler)
----------------------------------------------

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 and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not 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. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

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.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 953...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/953408

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

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

--- End Message ---

Reply via email to