Your message dated Sun, 22 Dec 2024 21:46:18 +0100
with message-id <z2h6miqvotbp4...@ramacher.at>
and subject line Re: Bug#1081827: transition: libjsoncpp
has caused the Debian Bug report #1081827,
regarding transition: libjsoncpp
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 ow...@bugs.debian.org
immediately.)
--
1081827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: libjson...@packages.debian.org
Control: affects -1 + src:libjsoncpp
User: release.debian....@packages.debian.org
Usertags: transition
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Release Team,
I'd like to transition libjsoncpp after a SONAME bump.
The changes are mostly ABI-incompatible layout changes to some structs (added
members somewhere in the middle). One function has been refactored, but it is
not directly called anywhere outside libjsoncpp according to
sources.debian.org
The Ben tracker at
https://release.debian.org/transitions/html/auto-libjsoncpp.html
looks mostly fine, although cmake should be DL 2 as it depends on
libjsoncpp-dev. This might be caused by the "<!cmake.pkg.bootstrap>"
condition.
Cheers
Timo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmbmo4wACgkQzIxr3RQD
9MoOug/7BVAtVK/nejA0tqyji5nPuX2GIdmZmix0XI7Y4WZg3sOIxufnturTFj4H
DmAfCiqSM6lofOir9BWQ1WdDnS5nYPPTQm0d2j1v9dYNLy5GKrsqUAWQFg3Z7iBl
2fniEHiChfZtV9LSP2bXw+Q7WbcmK9MzRDdRn4Itmfi8xWv1nl/Jb15e0kNLDKQH
aKX0Qr+7CtLyBJkU7qikxBVuOAZ0vZhpcnr/7DjRjKh/iUR+MjcGa7uhRbKToHTU
h4TZKXPX2/Pd5oI64rT1UwuH9jXeDUx4itE9a3iod6jgXSgw8JgP1x0XXazsZT6J
sRgtNtCcwdlOnlxFiMzOkO+5YL9voK1/oEMPAidJ39xF1WGepObW05xb1/dBS4C3
M59OjqegOL2jzmTc/fED4giI8toLF1terG2xQLSx60sySow8C1nY9qihXQQleLcY
jGyYa1FzOHK2xEfmAHYB2+q8/Ifi0NB2h9W9Moge1Odh3qiErKwXv512c1UWgHvt
4lc+BN3D3POWPNW/DAeNYDQjqSlj0moVRAI9UhjEGNAeHLtqjASByONKLkZ6z63U
WSY/mX7GxZwS+urBalm+dMCIJicuVfnIKC+zMiEzFz81rvJs6dE6z8uNliNypnax
+faZ1LmWejTPctWqRL7OnR5ViIL6wcw1ZTiMh76OFm9D5VikYV4=
=97rw
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 2024-09-26 18:16:12 +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> Control: forwarded -1
> https://release.debian.org/transitions/html/auto-libjsoncpp.html
>
> On 2024-09-15 11:06:21 +0200, Timo Röhling wrote:
> > Package: release.debian.org
> > Severity: normal
> > X-Debbugs-Cc: libjson...@packages.debian.org
> > Control: affects -1 + src:libjsoncpp
> > User: release.debian....@packages.debian.org
> > Usertags: transition
> >
> > Dear Release Team,
> >
> > I'd like to transition libjsoncpp after a SONAME bump.
> >
> > The changes are mostly ABI-incompatible layout changes to some structs
> > (added
> > members somewhere in the middle). One function has been refactored, but it
> > is
> > not directly called anywhere outside libjsoncpp according to
> > sources.debian.org
>
> Please go ahead.
The old binary packages got removed from testing. Closing
Cheers
--
Sebastian Ramacher
--- End Message ---
