Version 3.0.0-3 of weakforced is marked for autoremoval from testing on Sat 04 Apr 2026. It is affected by #1128153. You should try to prevent the removal by fixing these RC bugs.
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:
vcswatch reports that
this package seems to have a new changelog entry (version
3.0.0-5, distribution
unstable) and new commits
in its VCS. You should consider whether it's time to make
an upload.
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
This package will soon be part of the auto-yaml-cpp transition. You might want to ensure that your package is ready for it.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.
This package will soon be part of the auto-libsodium transition. You might want to ensure that your package is ready for it.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.
This package will soon be part of the auto-protobuf transition. You might want to ensure that your package is ready for it.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.
This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it.
You can probably find supplementary information in the
debian-release
archives or in the corresponding
release.debian.org
bug.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/w/weakforced.png){kind=link}