Re: emacs-nox

[Sven Joachim <svenjoac@gmx.de>]

Hi Sebastian,

Sebastian Tennant <sebyte@smolny.plus.com> writes:

> I have the following problem:
>
>   # apt-get install --reinstall emacs22-nox
>   [...]
>   The following packages have unmet dependencies.
>     emacs22-nox: Depends: libncurses5 (>= 5.6+20071006-3) but 5.6+20070908-1 is
>     to be installed
>   E: Broken packages
>
> But libncurses5 >= 5.6+20071006-3 is not available:
>
>   # apt-show-versions libncurses5
>   libncurses5	5.6+20070908-1	install ok installed
>   libncurses5	5.5-5	stable
>   libncurses5	5.6+20070908-1	testing
>   libncurses5	5.6+20070908-1	unstable
>   libncurses5/testing uptodate 5.6+20070908-1

Have you run "apt-get update" recently?  If yes, you should use a
different mirror.  FWIW, I already have libncurses5 5.6+20071013-1,
installed on October 17 (I run unstable).

> This unmet dependency means when I want to dist-upgrade I am prompted to
> do the following:
>
>   # apt-get dist-upgrade
>   Reading package lists... Done
>   Building dependency tree       
>   Reading state information... Done
>   Calculating upgrade... Done
>   The following packages will be REMOVED
>     bbdb debian-el dictem dictionary-el emacs22-nox nxml-mode ruby1.8-elisp
>     w3m-el
>   The following packages have been kept back:
>     cupsys hpijs hpijs-ppds libcupsys2 mplayer-nogui
>   The following packages will be upgraded:
>     emacs22-bin-common emacs22-common emacs22-el
>   3 upgraded, 0 newly installed, 8 to remove and 5 not upgraded.
>   Need to get 25.7MB of archives.
>   After unpacking 14.2MB disk space will be freed.
>   Do you want to continue [Y/n]? n
>   Abort.
>
> I suspect that if I allow dist-upgrade to remove emacs22-nox I won't be
> able to simply install it again, which would be a disaster!

It won't be that fatal, since you could reinstall it at a later point,
but that is certainly not what you want.

> Should I file a bug report, or just wait until a version of libncurses5
> is available that staisfies emacs22-nox.

First make sure to run "apt-get update".  If that does not cure the
problem, file a bug against the "mirrors" pseudopackage that your
mirror is horribly outdated.

Regards,
        Sven