Control: severity -1 important On 03/10/15 11:55, Gert Wollny wrote: > On Fri, 2015-10-02 at 15:57 +0200, Mathieu Malaterre wrote: > >> Forgot to quote section ยง8.4 Development files >> >> https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s >> -sharedlibs-dev >> >> [...] >> If there are development files associated with a shared library, the >> source package needs to generate a binary development package named >> librarynamesoversion-dev, or if you prefer >> [...] >> > > And the sentence continues > > [...] > , or if you prefer only to support one development version at a time, > libraryname-dev. > [...] > > IMHO adding the so-name to the -dev package makes only sense if the > different -dev packages can co-exist, like , e.g., libgtk2.0-dev and > libgtk3-dev, something that is clearly not the case for the > libdcmtkN-dev packages, because here we talk about a transition.
Yes, exactly. It makes little sense to version the -dev package and change it with every SONAME bump if you don't also rename the source package. In this situation, transitions are unnecessarily hard because all the rdeps need sourceful uploads. This bug was triggered because of this: https://release.debian.org/transitions/html/auto-dcmtk.html where all your rdeps build-dep on libdcmtk2-dev. Perhaps the severity is inflated. I don't mind to downgrade this, but now you have to either fix the rdeps (and do so for every transition, which is not nice) or stop renaming the package. [Or let libdcmtk4-dev provide libdcmtk2-dev... but that approach seems odd...] Cheers, Emilio
