Your message dated Fri, 2 Jan 2026 10:58:01 +0100
with message-id <[email protected]>
and subject line Re: Bug#1120612: transition: gpgme1.0
has caused the Debian Bug report #1120612,
regarding transition: gpgme1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1120612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120612
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Control: affects -1 + src:gpgme1.0
Control: block 1117237 by -1
User: [email protected]
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.
Ben file:
title = "gpgme1.0";
is_affected = .depends ~ "libgpgme11t64|libgpgmepp6t64" | .depends ~
"libgpgme45|libgpgmepp7";
is_good = .depends ~ "libgpgme45|libgpgmepp7";
is_bad = .depends ~ "libgpgme11t64|libgpgmepp6t64";
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
On 2025-11-16 07:18:26 +0100, Andreas Metzler wrote:
> On 2025-11-15 Emilio Pozuelo Monfort <[email protected]> wrote:
> > Control: tags -1 confirmed
>
> > On 13/11/2025 12:07, Emilio Pozuelo Monfort wrote:
> >> 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: [email protected]
> >>> 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)
> [...]
> > Go ahead.
>
> Good morning,
> Thank you, done. The 4 packages have been built successfully on all
> archs (except for two builds on non-release archs: qgpgme/sparc64 and
> gpgmepy/hurd-i386).
All packages migrated and the old binaries got removed. Closing
Cheers
--
Sebastian Ramacher
--- End Message ---
