Strange apt-get behavior with held packages
Background: For my purposes, emacs20 is too broken to use.
Therefore, when there was discussion on this list recently about
removing emacs19 from the distribution and making emacs20 replace and
conflict with emacs19, I put emacs19 and emacs19-el on hold to prevent
their removal.
I am running woody, and my apt-get sources point only to woody.
When I did apt-get update and apt-get dist-upgrade yesterday,
apt-get gave the following message:
Sorry, but the following packages have unmet dependencies:
emacs19: Depends: emacsen-common but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
I don't understand this. I have emacs19 19.34-26.5 and
emacs19-el 19.34-26.5 installed and marked hold, and I have
emacsen-common 1.4.12 installed. I also have emacs20 20.7-3
installed. All of these packages are the latest versions available in
woody, and have all dependencies installed.
Does apt-get consider a package broken if it is on hold? This
seems bizarre.
On a different subject, the perl brokeness that has been
discussed at length seems to have moved out of unstable to testing.
After un-holding emacs 19, I tried apt-get -u dist-upgrade, and it
proposed to remove 48 packages, including almost anything related to
perl. After aborting, I tried apt-get upgrade, and it kept-back 15
packages, mainly perl or perl related.
Bob
--
_
|_) _ |_ Robert D. Hilliard <hilliard@debian.org>
|_) (_) |_) 1294 S.W. Seagull Way <bob@bobhilliard.net>
Palm City, FL USA GPG Key ID: 390D6559
PGP Key ID: A8E40EB9
Reply to: