Re: Overwriting files and not replacing packages - (no Replaces)
Mathieu Malaterre writes: > I have uploaded CharLS 2.1.0+dfsg-7 with a single Breaks statement (no > Replaces statement): > > $ cat d/control > ... > Breaks: libdcmtk-dev (<< 3.6.4-2.1) > > In this specific case I do not need 'Replaces:' (*), because > 'libcharls.so' from libdcmtk-dev is not meant to be replaced by the > one shipped in libcharls-dev (2.1.0+dfsg-7) (this is not the normal > breaks+replaces pattern). That doesn't seem correct, but you haven't really said much about what you want to achieve. Why do both packages ship the same file? Are they somehow related? Ansgar
Re: Overwriting files and not replacing packages - (no Replaces)
Am 12.11.2020 um 08:28 teilte Mathieu Malaterre mit: Hi, In this specific case I do not need 'Replaces:' (*), because 'libcharls.so' from libdcmtk-dev is not meant to be replaced by the one shipped in libcharls-dev (2.1.0+dfsg-7) (this is not the normal breaks+replaces pattern). Replaces would be incorrect as both packages have different purposes and one package does not replaces part of the other package. Is my understanding correct? According to my understanding Conflict would be more in order: "Conflicts should be used when two packages provide the same file and will continue to do so," I don't see a file libcharls.so in libdcmtk-dev from unstable. What am I missing? H. -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Overwriting files and not replacing packages - (no Replaces)
Dear mentors, I have uploaded CharLS 2.1.0+dfsg-7 with a single Breaks statement (no Replaces statement): $ cat d/control ... Breaks: libdcmtk-dev (<< 3.6.4-2.1) In this specific case I do not need 'Replaces:' (*), because 'libcharls.so' from libdcmtk-dev is not meant to be replaced by the one shipped in libcharls-dev (2.1.0+dfsg-7) (this is not the normal breaks+replaces pattern). Is my understanding correct? (*) https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
