Bug#944417: Bug#946119: binNMU for gudhi, openems, and pygalmesh

To: Paul Gevers <elbrus@debian.org>, 946119@bugs.debian.org, 944417@bugs.debian.org
Subject: Bug#944417: Bug#946119: binNMU for gudhi, openems, and pygalmesh
From: Joachim Reichel <joachim.reichel@posteo.de>
Date: Thu, 5 Dec 2019 23:43:30 +0100
Message-id: <[🔎] b25d49a4-06f4-3144-19d6-c49b99c70901@posteo.de>
Reply-to: Joachim Reichel <joachim.reichel@posteo.de>, 944417@bugs.debian.org
In-reply-to: <[🔎] 915a929e-c9a5-0c7b-903a-fcba334e1f89@debian.org>
References: <[🔎] 157541414659.12825.15376330807664695975.reportbug@enterprise-e> <[🔎] 915a929e-c9a5-0c7b-903a-fcba334e1f89@debian.org> <157331343381.10072.11243342405542228109.reportbug@enterprise-e>

Hi Paul,

On 05.12.19 10:20, Paul Gevers wrote:
> Note: there is no need to create a new bug report for binNMU's that are
> part of a transition with a transition bug.

ok, thanks.

> That said, mips64el and mipsel FTBFS, can you please check what's going on?

I uploaded -4 which should fix this.

> On 04-12-2019 00:02, Joachim Reichel wrote:
>> please schedule binNMUs for gudhi, openems, and pygalmesh to support the
>> cgal_5.0 transition (see bug #944417).

Looking at the logs for pygalmesh I noticed that a binNMU will most likely not
work (see bug #946234). I'll prepare an NMU.

  Joachim

Reply to:

References:
- Bug#946119: binNMU for gudhi, openems, and pygalmesh
  - From: Joachim Reichel <reichel@debian.org>
- Bug#944417: Bug#946119: binNMU for gudhi, openems, and pygalmesh
  - From: Paul Gevers <elbrus@debian.org>

Prev by Date: Processed: [NMU] FTFBS with CGAL 5.0 (if cmake is absent)
Next by Date: Bug#946247: nmu: rdkit_201903.1-2
Previous by thread: Bug#944417: Bug#946119: binNMU for gudhi, openems, and pygalmesh
Next by thread: Processed: severity of 946030 is serious, cloning 946081 ..., reassign -1 to release.debian.org ..., tagging -1 ...
Index(es):
- Date
- Thread