action needed
1 binary package has unsatisfiable dependencies
high
A new upstream version is available: 0.5.1
high
A new upstream version 0.5.1 is available, you should consider packaging it.
The package has not entered testing even though the delay is over
normal
The package has not entered testing even though the 5-day delay is over.
Check why.
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.
Standards version of the package is outdated.
wishlist
The package should be updated to follow the last version of Debian Policy
(Standards-Version 4.7.0 instead of
4.5.0).
testing migrations
-
excuses:
- Migration status: Blocked. Can't migrate due to a non-migratable dependency. Check status below.
- Blocked by: pytorch
- Migrates after: python3.11_pu
- Migration status for pytorch-ignite (- to 0.4.12-1): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
- Issues preventing migration:
- ∙ ∙ Build-Depends(-Arch): pytorch-ignite pytorch (not considered)
- ∙ ∙ Depends: pytorch-ignite pytorch (not considered)
- ∙ ∙ Invalidated by build-dependency
- ∙ ∙ Invalidated by dependency
- ∙ ∙ Depends: pytorch-ignite python3.11_pu (not considered)
- Additional info:
- ∙ ∙ Cannot be tested by piuparts (not a blocker) - https://piuparts.debian.org/sid/source/p/pytorch-ignite.html
- ∙ ∙ uninstallable on arch armel (which is allowed), not running autopkgtest there
- ∙ ∙ uninstallable on arch armhf (which is allowed), not running autopkgtest there
- ∙ ∙ uninstallable on arch i386 (which is allowed), not running autopkgtest there
- ∙ ∙ uninstallable on arch riscv64 (which is allowed), not running autopkgtest there
- ∙ ∙ Waiting for reproducibility test results on armhf - info ♻
- ∙ ∙ Waiting for reproducibility test results on i386 - info ♻
- ∙ ∙ 423 days old (needed 5 days)
- Not considered