[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#999770: marked as done (transition: libjsoncpp)

Your message dated Fri, 7 Jan 2022 13:19:47 +0100
with message-id <Ydgv43jPVr9d2QuK@ramacher.at>
and subject line Re: Bug#999770: transition: libjsoncpp
has caused the Debian Bug report #999770,
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 owner@bugs.debian.org
immediately.)


-- 
999770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999770
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear release team,

I woud like to transition libjsoncpp after an ABI version bump. I
rebuilt CMake successfully and I don't expect any FTBFS issues, as the
diff on the public headers shows mostly added "noexpect" and "const"
qualifiers, which will not break existing source code. One hacky
"volatile" qualifier has been removed from the
SecureAllocator<T>::deallocate() signature in json/allocator.h, but
codesearch.debian.net tells me that header is not directly used by
reverse dependencies anyway.

The Ben file at
https://release.debian.org/transitions/html/auto-libjsoncpp.html
is good.


Cheers
Timo


-----BEGIN PGP SIGNATURE-----

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmGTqUYACgkQ+C8H+466
LVmBAwwAkXJS3XQgdwR4JyN6idMw/K3KrPpYLde68q5+lHOKjLUCOgcvs1gPDOfh
gDI0sCOyjOocYVYy/08CHhDitOXbZxPDuYU5LLoqoORgFyaycIPMmM5zmgZnQvWA
sYCe/DeLbgKSZEdvyZEurLx2T1S0QmudR96garFiIti0J9WsM6KWNDCzK6m7PVZt
ZhOZ+UMBCDFzjeejTo+Nl8HQ4punVUNGmRmu4xjF5OafFmzKfPclJx2EIJOXJMyp
NMV4aoqDhic+4eBSk6Epogo5bEHFQry9H2+AJtt+0MBEV7wG5tDE0eVCOSdd3TXy
qdLWlfIF1vkQM8J2M6Z4eESnSeRVQK7615fFkzaZSpS6us6NaF2AJsP/acgNqJTi
vIJkj8NBP/tBOR6+tkXWLy2HQCokTdbqBKtAS2YipWZNO4g9LmUFhGxeOeRCKbSS
oarHOuz8YfnR8D9YGZqb7mo3UrnNRJZuivq2kYmr6hZC6aP/6v7HQlH+yvOcXrD7
fe+lvyli
=oOjg
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On 2021-12-11 15:22:50 +0100, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> Control: forwarded -1 https://release.debian.org/transitions/html/auto-libjsoncpp.html
> 
> On 2021-11-16 13:51:23 +0100, Timo Röhling wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian.org@packages.debian.org
> > Usertags: transition
> > 
> > Dear release team,
> > 
> > I woud like to transition libjsoncpp after an ABI version bump. I
> > rebuilt CMake successfully and I don't expect any FTBFS issues, as the
> > diff on the public headers shows mostly added "noexpect" and "const"
> > qualifiers, which will not break existing source code. One hacky
> > "volatile" qualifier has been removed from the
> > SecureAllocator<T>::deallocate() signature in json/allocator.h, but
> > codesearch.debian.net tells me that header is not directly used by
> > reverse dependencies anyway.
> 
> Please go ahead

The old package got removed from testing.

Cheers

> 
> Cheers
> 
> > 
> > The Ben file at
> > https://release.debian.org/transitions/html/auto-libjsoncpp.html
> > is good.
> > 
> > 
> > Cheers
> > Timo
> > 
> > 
> > 
> 
> -- 
> Sebastian Ramacher



-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: