Le 13/10/2017 à 19:43, Sébastien Villemot a écrit :
On Thu, Oct 12, 2017 at 10:34:00PM +0200, Julien Bect wrote:Le 04/10/2017 à 10:08, Sébastien Villemot a écrit :On Tue, Oct 03, 2017 at 09:59:25PM +0200, Oliver Heimlich wrote:Am 3. Oktober 2017 18:06:37 MESZ schrieb Julien Bect <julien.bect@centralesupelec.fr>:octave-stk has been marked for autoremoval from testing because of the following test failure on unstable/i386:...Both functions (sqp, qp) are in Octave itself, and the problem is already known : http://savannah.gnu.org/bugs/?38875. How should we deal with this issue to prevent octave-stk-2.4.2-1 from being removed from testing ?I'd suggest to mark it as an xtest, since there is nothing you can do about right now.Sounds good to me. A Debian-specific patch (that can be removed later when octave is fixed) is probably the easy way, but you can also do a new upstream release if you prefer.I have pushed a Debian-specific patch. Can you please check that I did that right ?Yes it's good. I just added some more DEP-3 metadata.If it's ok, I think that we should do a 2.4.2-2 release to prevent removal from testing.Thanks, uploaded.
Hi all, Some of the tests currently fail in the continuous integration system: https://tracker.debian.org/pkg/octave-stk The problem is that there is no graphics toolkit available.gnuplot-nox is used to avoid this when building, but what should we do here ?
It wouldn't seem right to add gnuplot-nox, or any particular graphics toolkit, to the dependencies of octave-stk...
Should I create a patch to disable all the tests that produce graphics ? Or is there a way to indicate "testing-dependencies" ?
@++ Julien