Thanks for reporting this Bob. On Thu, 2011-12-29 at 00:30 +0100, Kamil Ignacak wrote: > On -10.01.-28163 20:59, Bob Proulx wrote: > > Unpacking libcw3 (from .../libcw3_3.0-2_amd64.deb) ... > > dpkg: error processing /var/cache/apt/archives/libcw3_3.0-2_amd64.deb (--unpack): > > trying to overwrite '/usr/share/man/man7/cw.7.gz', which is also in package unixcw 2.3-13 > > configured to not write apport reports > To Kamal Mostafa: looks like we should revert the latest change in > debian/control (patch attached). Would you agree? Yes, I now see the error of my ways in removing the Replaces, and furthermore I think we also need a Conflicts: for both of those. I'll upload a new unixcw package shortly, which I think fixes the problem. Bob, please advise if you find otherwise. > > I am on the outside looking in and am surprised by this break. It > > appears that you are renaming the unixcw package to cw and that the > > package renaming has failed due to missing Conflicts, Replaces, Breaks > > headers and missing transition dummy package for the old unixcw but I > > haven't examined the problem in detail at this moment. What is the > > intention? > unixcw(-dev) has been renamed to libcw3(-dev) for consistency reasons > and to avoid using name of project/source code package as Debian package > name. Considerable changes in lib's API and functionality made the > switch to new name even more needed (IMHO). > > Initially debian/control contained "Replaces: unixcw(-dev)" lines, but > the line has been removed for some (minor?) reason. It seems that the > change needs to be reverted. And... Since the new libcw3 doesn't provide a compatible API with the old unixcw library, I don't think we can provide a transition dummy unixcw package. We've fixed the one package that we know was dependent on unixcw (cwdaemon) to now use the new libcw3, but any other users of the library will unfortunately be broken by the API change. -Kamal
Attachment:
signature.asc
Description: This is a digitally signed message part