Bug#969633: transition: json-simple

[pini]

Hi Paul,

Le 2024-09-26 13:54, Paul Gevers a écrit :

Hi,

On Sun, 20 Sep 2020 19:33:49 +0200 Gilles Filippini <p...@debian.org> wrote:

Emilio Pozuelo Monfort a écrit le 20/09/2020 à 18:50 :
> On 06/09/2020 13:38, Gilles Filippini wrote:
>> Upstream removed an API that was deprecated long ago and introduced a
>> few backward incompatible changes.
> > Then it needs a SONAME bump.


list whether to change the binary package's name and it was answered
that it should be avoidable [1]. I eventually chose not to change it
because there are few reverse dependencies.

There is no such thing in java. I asked the question on the debian-java

As you don't have a way to know what 3rd party packages exist that rely on json-simple's binaries, the most robust solution is to rename the binary like we do in c-library transitions when SONAME's are bumped. We don't get the benefit of smooth-transitions, but it avoids most silent breakage.

Do I assume correctly that the reverse build dependencies' binaries get the right package name to depend on during the build, or are they hard-coded and would need manual updating? If it's manual, how would the reverse build dependencies' binaries get the right versioned dependency?

Best,
_g.

Thank you for following up on this old thread, but I've now lost interest in json-simple. I started packaging it as a dependency of sikuli which was removed from Debian 8 years ago.

signature.asc
Description: OpenPGP digital signature