Dear Thomas Schmitt,
Yes, I think the local fix is the way to go. Probably even getting rid of the source of this, my manual GRPC install and replacing it with libgrpc++-dev. But that’s outside of this issue.
Yours,
Jonathan Chung
Am 02.04.2024 um 23:34 schrieb Thomas Schmitt <scdbackup@gmx.net>:
Hi,
(You forgot to Cc: debian-user@lists.debian.org.
Consider to send your mail to the list address, too. I too would then
resend my following reply to the list.)
Chung Jonathan wrote:
I do have libz.so.1.3,
since I manually compiled grpc on my machine and this also uses a newer
version of zlib appearently. [...]
Do you still think a bug report is worth it?
Rather not.
The original combination of pigz and zlib works in Debian 12. So it's
not a bug in that context.
The fact that it hampers upgrade to younger zlib is already addressed
by the version of pigz in "testing". So in the context of Debian 13 it
will be no bug either.
This leaves only the possibility to really ask for a backport for the
new feature that one can upgrade zlib before Debian offers it. But the
desired use case is near to the topic of "Frankendebian":
https://wiki.debian.org/DontBreakDebian
If in urgent need for a fix, i expect that you would get more lucky by
patching the "stable" pigz package for your local use according to
https://wiki.debian.org/BuildingTutorial
(patching is done in
https://wiki.debian.org/BuildingTutorial#Edit_the_source_code
and as usual in Debian, there are more ways than this one to do it ...)
Have a nice day :)
Thomas
|