Debcheck


	Back to QA Debcheck - trixie Summary All packages (light) main only Broken PreDepends Broken Depends Broken Recommends Broken Suggests HalfBroken PreDepends HalfBroken Depends HalfBroken Recommends HalfBroken Suggests Build-Depends HalfBroken Build-Depends Malformed Build-Depends OldLibs Priority Old Standards-Version No Standards-Version Wrong Standards-Version Syntax other Depends Main on !Main all sections Broken PreDepends Broken Depends Broken Recommends Broken Suggests HalfBroken PreDepends HalfBroken Depends HalfBroken Recommends HalfBroken Suggests Build-Depends HalfBroken Build-Depends Malformed Build-Depends OldLibs Priority Old Standards-Version No Standards-Version Wrong Standards-Version Syntax

Distribution: trixie

Problems for source package python-meshplex

Current Source Version: 0.17.1-5
Current Maintainer: Debian Science Maintainers <[email protected]>
Section: main
BTS entry: https://bugs.debian.org/src:python-meshplex

BuildDepends

Package declares a build time dependency on python3-numpy (>= 1.20.0~) which cannot be satisfied on mips64el. Package python-meshplex does not exist on mips64el.
Package declares a build time dependency on python3-matplotlib which cannot be satisfied on mips64el. Package python-meshplex does not exist on mips64el.
Package declares a build time dependency on python3-scipy which cannot be satisfied on mips64el. Package python-meshplex does not exist on mips64el.
Package declares a build time dependency on python3-all which cannot be satisfied on mips64el. Package python-meshplex does not exist on mips64el.

Binary Package: python3-meshplex (Version: 0.17.1-5)

BTS entry: https://bugs.debian.org/python3-meshplex

Relationships

Package has a Depends on python3:any which cannot be satisfied on mips64el.
Package has a Depends on python3-numpy (>= 1.20.0~) which cannot be satisfied on mips64el.
Package has a Depends on python3-scipy which cannot be satisfied on mips64el.

Last updated: Sun Jun 8 15:25:44 2025

DO NOT MASS FILE BUG REPORTS
GET A CONSENSUS ON [email protected] BEFORE MASS FILING BUGS