action needed
A new upstream version is available: 2012
high
A new upstream version 2012 is available, you should consider packaging it.
piuparts found (un)installation error(s)
normal
Piuparts stresses package installation, uninstallation, upgrade, ... While doing such tests, one or more errors were found for the following suites:
You should fix them.
testing migrations
-
excuses:
- Migration status for mavproxy (- to 1.8.74-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ mavproxy/amd64 has unsatisfiable dependency
- ∙ ∙ python3-mavproxy/amd64 has unsatisfiable dependency
- ∙ ∙ mavproxy/arm64 has unsatisfiable dependency
- ∙ ∙ python3-mavproxy/arm64 has unsatisfiable dependency
- ∙ ∙ Lintian check waiting for test results - info
- ∙ ∙ Too young, only 0 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts can't test mavproxy (not a blocker) - https://piuparts.debian.org/sid/source/m/mavproxy.html
- ∙ ∙ Autopkgtest skipped on amd64: not installable
- ∙ ∙ Autopkgtest skipped on arm64: not installable
- ∙ ∙ Autopkgtest skipped on armhf: not installable (which is allowed)
- ∙ ∙ Autopkgtest skipped on i386: not installable (which is allowed)
- ∙ ∙ Autopkgtest skipped on ppc64el: not installable (which is allowed)
- ∙ ∙ Autopkgtest skipped on riscv64: not installable (which is allowed)
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- Not considered
![[bug history graph]](https://qa.debian.org/data/bts/graphs/m/mavproxy.png){kind=link}