Axel Beckert <[email protected]> writes:
> upgrading emacs25-lucid on armhf pulls in emacs-lucid, but that fails
> to install as follows:
>
> Preparing to unpack .../emacs-lucid_1%3a25.2+1-8_armhf.deb ...
> Unpacking emacs-lucid (1:25.2+1-8) ...
> dpkg: error processing archive
> /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-8_armhf.deb (--unpack):
> trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in
> package emacs25-lucid 25.2+1-6+b3
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> Errors were encountered while processing:
> /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-8_armhf.deb
>
> The Replaces header only contains emacs-gtk and emacs-nox, but likely
> also needs emacs25-lucid. And probably also needs a "Breaks:
> emacs25-lucid".
I suspect I'm just misunderstanding the dependency system, but this
confuses me because:
emacs25-lucid 25.2+1-6+b3
Depends: emacs25-bin-common
and
emacs25-bin-common
Depends: emacs25-common
and on the newer side
emacs-lucid 1:25.2+1-8
Depends: emacs-common (= 1:25.2+1-8)
and
emacs-common 1:25.2+1-8
Depends: emacsen-common (>= 3.0.0)
and
emacsen-common (>= 3.0.0)
Conflicts: emacs25-common
So I'd expected the indirect dependency of emacs-lucid on the newer
emacsen-common to have indirectly forced emacs25-lucid out (via the
emacsen-common conflicts), so that there wouldn't be a file conflict,
but obviously I'm missing something (and agree that it's a somewhat
tortuous route).
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
