The dependencies of cyrus-admin=3.10.0-1 cannot be satisfied in unstable on
i386, mips64el, amd64, ppc64el, s390x, and arm64
because: unsatisfied dependency on perlapi-5.38.2
The dependencies of cyrus-dev=3.10.0-1 cannot be satisfied in unstable on
i386, mips64el, amd64, ppc64el, s390x, and arm64
because: unsatisfied dependency on perlapi-5.38.2
The dependencies of libcyrus-imap-perl=3.10.0-1 cannot be satisfied in unstable on
i386, mips64el, amd64, ppc64el, s390x, and arm64
because: unsatisfied dependency on perlapi-5.38.2
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.
vcswatch reports that
this package seems to have a new changelog entry (version
3.10.0-2, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
The current maintainer is looking for someone who can help with
the maintenance of this package. If you are interested in this
package, please consider helping out. One way you can help is
offer to be a co-maintainer or triage bugs in the BTS. Please see bug number #921717 for more information.
Among the 8 debian patches
available in version 3.10.0-1 of the package,
we noticed the following issues:
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.
This package will soon be part of the auto-openldap 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-libxml2 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-icu 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.