action needed
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.
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.4 instead of
4.7.3).
testing migrations
-
excuses:
- Migrates after: php-spyc
- Migration status for matomo-device-detector (- to 6.5.0-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Removal request by auto-removals
- ∙ ∙ Trying to remove package, not update it
- ∙ ∙ Remove hint for (transitive) dependency: matomo-device-detector, php-deepcopy, php-directory-scanner, php-file-iterator, php-invoker, php-parser, php-phar-io-manifest, php-phar-io-version, php-spyc, php-staabm-side-effects-detector, php-symfony-contracts, php-text-template, php-timer, php-tokenizer, php-zeta-base, php-zeta-console-tools, phpab, phpunit-cli-parser, phpunit-complexity, phpunit-global-state, phpunit-lines-of-code, phpunit-object-enumerator, phpunit-object-reflector, phpunit-recursion-context, phpunit-type, phpunit-version, symfony
- ∙ ∙ Autopkgtest for matomo-device-detector: amd64: Test triggered, arm64: Test triggered, i386: Test triggered, ppc64el: Test triggered, riscv64: Test triggered, s390x: Test triggered
- ∙ ∙ Build-Depends(-Arch): matomo-device-detector php-spyc (not considered)
- ∙ ∙ Depends: matomo-device-detector php-spyc (not considered)
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/m/matomo-device-detector.html
- ∙ ∙ Reproduced on amd64
- ∙ ∙ Reproduced on arm64
- ∙ ∙ Reproduced on armhf
- ∙ ∙ Reproduced on i386
- ∙ ∙ Reproduced on ppc64el
- ∙ ∙ 86 days old (needed 5 days)
- Not considered
![[bug history graph]](https://qa.debian.org/data/bts/graphs/m/matomo-device-detector.png){kind=link}