Bug#399024: vim: Upgrade fails because of missing man page directory

Colin Watson cjwatson at ubuntu.com
Sun Dec 24 13:25:56 UTC 2006

On Sat, Nov 18, 2006 at 04:24:21PM -0500, James Vega wrote:
> On Sat, Nov 18, 2006 at 02:03:43PM -0700, Larry Lade wrote:
> > According to dpkg.log packages vim, vim-common, vim-runtime, vim-tiny,
> > vim-gtk, vim-gnome, vim-gui-common  from 1:7.0-094+1 to 1:7.0-122+1, to 1:
> > 7.0-152+1, to 1:7.0-158+1, to 1:7.0-164+1. The error messages about the
> > Russian manpage do not appear in that log. I can attach the log if you think
> > it would be useful.
> The portion about upgrading to 1:7.0-164+1 may be, but I'm not very
> hopeful.

I'm also seeing this on Ubuntu when upgrading from 1:7.0-122+1ubuntu1 to
1:7.0-164+1ubuntu1. I don't think the Ubuntu changes are relevant.

> > I'm starting to suspect this is cruft introduced by some other package some
> > time ago. I'm still perplexed where "/usr/share/man/ru.UTF-8/" is coming
> > from, since I don't even have such a directory on my filesystem.
> Up until 1:7.0-164+1, Vim (vim-common specifically) shipped man pages in
> that directory.  Every vim variant also setup alternatives links in the
> various man page directories.  In 1:7.0-164+1, we stopped shipping man
> pages in /usr/share/man/ru.{UTF-8,KOI8-R}/man1 and moved the KOI8-R man
> pages to /usr/share/man/ru/man1 based on another bug report that had
> been filed against Vim a while ago.
> What I suspected was happening was that when we setup the alternatives in
> vim-$variant's postinst, it had problems with the ru.KOI8-R and ru.UTF-8
> no longer being shipped.  That doesn't seem to be the case though, at
> least when I perform an upgrade.  I'll try it in a fresh chroot later to
> see if something about my normal environment is making things work when
> they shouldn't.  Otherwise, I'm at a loss as to why it's working for me
> and not for other people.

It's got something to do with existing alternatives. I've attached my
/var/lib/dpkg/alternatives/view, which mentions ru.KOI8-R and ru.UTF-8.

Strangely, though, repeated 'dpkg --configure -a' invocations sort it
out, which suggests that one way to work around this would be to retry
each update-alternatives call once if it fails. Nasty, but perhaps

update-alternative does have code to discard obsolete slave links (look
for "obsolete" in /usr/sbin/update-alternatives). Perhaps there's some
way to get it to do that more competently?

In any case, this does feel like an update-alternatives bug as well,
even if you work around it in vim.


Colin Watson                                       [cjwatson at ubuntu.com]
-------------- next part --------------





More information about the pkg-vim-maintainers mailing list