On 28.12.06 Frank Küster ([EMAIL PROTECTED]) wrote: > Roland Rosenfeld <[EMAIL PROTECTED]> wrote:
Hi, > >> Unpacking replacement iceweasel ... > >> dpkg: error processing > >> /var/cache/apt/archives/iceweasel_2.0.0.1+dfsg-1_i386.deb (--unpack): > >> trying to overwrite `/usr/share/firefox', which is also in package dwww > >> Please restart any running Iceweasels, or you will experience problems. > >> > >> I guess that directory belongs rather to iceweasel than to dwww. > >> Hence the bug belongs to your package. > > > > The problem is that /usr/share/firefox usually is a directory (at > > least in the packages dwww and firefox), while iceweasel contains > > a symlink /usr/share/firefox: > > I wonder why this causes a problem in dpkg at all. > > ,---- Policy 6.6 > | 4. [...] > | > | A directory will never be replaced by a symbolic link to a > | directory or vice versa; instead, the existing state (symlink or > | not) will be left alone and dpkg will follow the symlink if > | there is one. > | > `---- > > To me this always implied that file conflicts between packages aren't > possible in this situation, either (and I even think I tried it out). > After all, it's not a bug for two packages to ship the same directory. > But it causes a problem if one package ships the file as symlink and the other as directory. > Moreover, I don't see how this problem can be fixed in iceweasel, > and why it is not RC for dwww to fail to install when iceweasel is > present. > I had the way round: iceweasel upgrade and having dwww installed. iceweasel tries to overwrite the directory shipped by dwww. I guess the bug is reproducible quite easy. H. -- sigmentation fault
