Marked for autoremoval on 11 April due to isospec: #1064938high
Version 9.3.1-1 of minexpert2 is marked for autoremoval from testing on Thu 11 Apr 2024. It depends (transitively) on isospec, affected by #1064938. You should try to prevent the removal by fixing these RC bugs.
Problems while searching for a new upstream version
high
uscan had problems while searching for a new upstream version:
In debian/watch no matching files for watch line
https://gitlab.com/msxpertsuite/minexpert2/-/tags .*/minexpert2-(?:[-_]?[Vv]?(\d[\-+\.:\~\da-zA-Z]*))(?i)(?:\.(?:tar\.xz|tar\.bz2|tar\.gz|tar\.zstd?|zip|tgz|tbz|txz))
vcswatch reports that
there is an error with this package's VCS, or the debian/changelog file inside
it. Please check the error shown below and try to fix it. You might have
to update the VCS URL in the debian/control file to point to the correct
repository.
fatal: could not read Username for 'https://salsa.debian.org': No such device or address
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.
Lintian reports
1 warning
about this package. You should make the package lintian clean getting rid of them.
testing migrations
This package is part of the ongoing testing transition known as auto-isospec.
Please avoid uploads unrelated to this transition, they would
likely delay it and require supplementary work from the release
managers. On the other hand, if your package has problems
preventing it to migrate to testing, please fix them
as soon as possible.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.
This package is part of the ongoing testing transition known as auto-qt6-base.
Please avoid uploads unrelated to this transition, they would
likely delay it and require supplementary work from the release
managers. On the other hand, if your package has problems
preventing it to migrate to testing, please fix them
as soon as possible.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.