Bug#953229: marked as done (coq: FTBFS test failures)
Your message dated Fri, 11 Sep 2020 05:13:02 +0200
with message-id <20200911031302.GA658195@seneca.home.org>
and subject line Re: coq: FTBFS test failures
has caused the Debian Bug report #953229,
regarding coq: FTBFS test failures
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 owner@bugs.debian.org
immediately.)
--
953229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953229
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: coq: FTBFS test failures
- From: Gianfranco Costamagna <locutusofborg@debian.org>
- Date: Fri, 6 Mar 2020 09:50:01 +0100
- Message-id: <b79515d0-6f17-0ef5-cf1b-b421ca68becc@debian.org>
- References: <b79515d0-6f17-0ef5-cf1b-b421ca68becc.ref@debian.org>
Source: coq
Version: 8.11.0-1
Severity: serious
Hello, looks like the latest coq is FTBFS because of test failures on various architectures.
Looks like at least armel, armhf, i386, s390x and some others are failing for this.
https://buildd.debian.org/status/package.php?p=coq&suite=unstable
Can you please have a look (if you didn't already!)
thanks
Gianfranco
--- End Message ---
--- Begin Message ---
Version: 8.12.0-2
> Hello, looks like the latest coq is FTBFS because of test failures on
> various architectures.
this is fixed now, through a series of upstream fixes and desactivations
of tests, after discussion with upstream, in 8.11.1~pre1-1, 8.12.0-1
and 8.12.0-2.
It only remains an unresolved failure on s390x.
-Ralf.
--- End Message ---
Reply to: