Marked for autoremoval on 03 October: #1143654high
Version 1.0.21-17 of freecontact is marked for autoremoval from testing on Sat 03 Oct 2026. It is affected by #1143654. The removal of freecontact will also cause the removal of (transitive) reverse dependencies: libfreecontact-perl, python-freecontact. 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:
Untrackable project: no upstream site for this package.
debian/patches: 1 patch with invalid metadata, 1 patch to forward upstream
high
Among the 2 debian patches
available in version 1.0.21-19 of the package,
we noticed the following issues:
1 patch with
invalid metadata that ought to be fixed.
1 patch
where the metadata indicates that the patch has not yet been forwarded
upstream. You should either forward the patch upstream or update the
metadata to document its real status.
The package has not entered testing even though the delay is over
normal
The package has not entered testing even though the 2-day delay is over.Check why.
This package will soon be part of the auto-xerces-c 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.
Migration status for freecontact (1.0.21-17 to 1.0.21-19): BLOCKED: Cannot migrate due to another item, which is blocked (please check which dependencies are stuck)
![[bug history graph]](https://qa.debian.org/data/bts/graphs/f/freecontact.png){kind=link}