On 13/11/2025 07:25, Andreas Metzler wrote:
Package: release.debian.org
Severity: normal
Control: affects -1 + src:gpgme1.0
Control: block 1117237 by -1
User: release.debian.org@packages.debian.org
Usertags: transition
Hello
the gpgme1.0 source was split upstream into (debian source package
names):
- gpgme1.0 (C library, gpgme-json binary)
- gpgmepp (C++ bindings)
- qgpgme (QT5 and QT6 bindings)
- gpgmepy (python bindings)
The C library and the C++ bindings both also had a smallish API change
(removal a deprecated stuff) and therefore a somame bump.
About a month ago I tried rebuilding all rdeps and submitted bugs
against the failing ones (see the blockers of the tracker bug #1117237
Most have been fixed promptly and I have uploaded NMUs for the remaining
ones to the delayed queue, (they should appear in sid on Nov 13) except
for these:
* libcryptui (Due to #1112383 libcryptui: unmaintained upstream; upstream
repository is archived and read-only)
* caja-seahorse ( #1118295 caja-seahorse: Remove from Debian?)
* seahorse - The fix has been applied in Debian packaging and a release
has already been tagged in GIT, just waiting for the upload to appear.
I have pinged Jeremy about the seahorse upload.
Given the package split in different sources, we can't use the auto-tracker, so
I have added one. Things look good, but let's wait for the sqlcipher transition
to happen while the rest of the deferred uploads reach the archive and the
tracker is set up.