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

2006-12-24 Thread Colin Watson
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
functional.

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.

Cheers,

-- 
Colin Watson   [EMAIL PROTECTED]
auto
/usr/bin/view
view.1.gz
/usr/share/man/man1/view.1.gz
view.it.1.gz
/usr/share/man/it/man1/view.1.gz
view.fr.UTF-8.1.gz
/usr/share/man/fr.UTF-8/man1/view.1.gz
view.ru.UTF-8.1.gz
/usr/share/man/ru.UTF-8/man1/view.1.gz
view.pl.1.gz
/usr/share/man/pl/man1/view.1.gz
view.it.ISO8859-1.1.gz
/usr/share/man/it.ISO8859-1/man1/view.1.gz
view.fr.ISO8859-1.1.gz
/usr/share/man/fr.ISO8859-1/man1/view.1.gz
view.it.UTF-8.1.gz
/usr/share/man/it.UTF-8/man1/view.1.gz
view.pl.ISO8859-2.1.gz
/usr/share/man/pl.ISO8859-2/man1/view.1.gz
view.pl.UTF-8.1.gz
/usr/share/man/pl.UTF-8/man1/view.1.gz
view.fr.1.gz
/usr/share/man/fr/man1/view.1.gz
view.ru.KOI8-R.1.gz
/usr/share/man/ru.KOI8-R/man1/view.1.gz
view.ru.1.gz
/usr/share/man/ru/man1/view.1.gz

/usr/bin/vim
35
/usr/share/man/man1/vim.1.gz












/usr/bin/vim.basic
30
/usr/share/man/man1/vim.1.gz
/usr/share/man/it/man1/vim.1.gz
/usr/share/man/fr.UTF-8/man1/vim.1.gz

/usr/share/man/pl/man1/vim.1.gz
/usr/share/man/it.ISO8859-1/man1/vim.1.gz
/usr/share/man/fr.ISO8859-1/man1/vim.1.gz
/usr/share/man/it.UTF-8/man1/vim.1.gz
/usr/share/man/pl.ISO8859-2/man1/vim.1.gz
/usr/share/man/pl.UTF-8/man1/vim.1.gz
/usr/share/man/fr/man1/vim.1.gz

/usr/share/man/ru/man1/vim.1.gz
/usr/bin/vim.tiny
10
/usr/share/man/man1/vim.1.gz
/usr/share/man/it/man1/vim.1.gz
/usr/share/man/fr.UTF-8/man1/vim.1.gz
/usr/share/man/ru.UTF-8/man1/vim.1.gz
/usr/share/man/pl/man1/vim.1.gz
/usr/share/man/it.ISO8859-1/man1/vim.1.gz
/usr/share/man/fr.ISO8859-1/man1/vim.1.gz
/usr/share/man/it.UTF-8/man1/vim.1.gz
/usr/share/man/pl.ISO8859-2/man1/vim.1.gz
/usr/share/man/pl.UTF-8/man1/vim.1.gz
/usr/share/man/fr/man1/vim.1.gz
/usr/share/man/ru.KOI8-R/man1/vim.1.gz




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

2006-11-18 Thread James Vega
On Fri, Nov 17, 2006 at 02:40:46PM -0500, James Vega wrote:
 On Fri, Nov 17, 2006 at 11:11:50AM -0700, Larry Lade wrote:
  Package: vim
  Version: 1:7.0-164+1
  Followup-For: Bug #399024
  
  
  Confirmed.
  
  This bug appears in packages vim, vim-gnome, and vim-gtk.
  
  Note this bug also occurs when trying to REMOVE the packages in question. 
  
  --Begin output--
  
  Setting up vim (7.0-164+1) ...
  update-alternatives: unable to make 
  /usr/share/man/ru.UTF-8/man1/editor.1.gz.dpkg-tmp a symlink to 
  /etc/alternatives/editor.ru.UTF-8.1.gz: No such file or directory
  dpkg: error processing vim (--configure):
   subprocess post-installation script returned error exit status 2
 
 This is interesting since the postinst script for 1:7.0-164+1 doesn't
 have ru.UTF-8 anywhere in it.  I'm guessing this is because the previous
 versions did and we're only removing alternatives on prerm remove not
 prerm upgrade.  I'll confirm this and should be able to get a new
 upload which fixes it this weekend.

I'm unable to reproduce this problem.  I've tried through both an
aptitude upgrade and apt-get upgrade from 1:7.0-158+1 to
1:7.0-164+1.  Do you know which version you were upgrading from when
this happened?

James
-- 
GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED]


signature.asc
Description: Digital signature


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

2006-11-18 Thread Bas Zoetekouw
Hi!

 I'm unable to reproduce this problem.  I've tried through both an
 aptitude upgrade and apt-get upgrade from 1:7.0-158+1 to
 1:7.0-164+1.  Do you know which version you were upgrading from when
 this happened?

I just encountered this bug while upgrading vim-full from 1:7.0-158+1 to
current unstable (1:7.0-164+1).

-- 
++
| Bas Zoetekouw  | GPG key: 0644fab7 |
|| Fingerprint: c1f5 f24c d514 3fec 8bf6 |
| [EMAIL PROTECTED] |  a2b1 2bae e41f 0644 fab7 |
++ 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



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

2006-11-18 Thread Michal Čihař
Hi

On Sat, 18 Nov 2006 09:23:59 -0500
James Vega [EMAIL PROTECTED] wrote:

 I'm unable to reproduce this problem.  I've tried through both an
 aptitude upgrade and apt-get upgrade from 1:7.0-158+1 to
 1:7.0-164+1.  Do you know which version you were upgrading from when
 this happened?

Aptitude log shows following:

[UPGRADE] vim 1:7.0-158+1 - 1:7.0-164+1
[UPGRADE] vim-common 1:7.0-158+1 - 1:7.0-164+1
[UPGRADE] vim-full 1:7.0-158+1 - 1:7.0-164+1
[UPGRADE] vim-gui-common 1:7.0-158+1 - 1:7.0-164+1
[UPGRADE] vim-runtime 1:7.0-158+1 - 1:7.0-164+1

After few times running configure, errors were disappearing - first time
vim-full and vim failed, then only vim, which failed several times, and
with today update even vim has configured...

-- 
Michal Čihař | http://cihar.com | http://blog.cihar.com


signature.asc
Description: PGP signature


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

2006-11-18 Thread Larry Lade

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.

Synaptic's History tool oddly records no activity on these packages since 26
October (122 - 152 upgrade).

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.

Hmm... a quick Google search indicates this path appearing in reports for
Vim 7.0 on other bug tracking systems.


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

2006-11-18 Thread James Vega
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.

 Synaptic's History tool oddly records no activity on these packages since 26
 October (122 - 152 upgrade).
 
 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.

James
-- 
GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED]


signature.asc
Description: Digital signature


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

2006-11-17 Thread Larry Lade
Package: vim
Version: 1:7.0-164+1
Followup-For: Bug #399024


Confirmed.

This bug appears in packages vim, vim-gnome, and vim-gtk.

Note this bug also occurs when trying to REMOVE the packages in question. 

--Begin output--

Setting up vim (7.0-164+1) ...
update-alternatives: unable to make 
/usr/share/man/ru.UTF-8/man1/editor.1.gz.dpkg-tmp a symlink to 
/etc/alternatives/editor.ru.UTF-8.1.gz: No such file or directory
dpkg: error processing vim (--configure):
 subprocess post-installation script returned error exit status 2
Setting up vim-gnome (7.0-164+1) ...
update-alternatives: unable to make 
/usr/share/man/ru.UTF-8/man1/editor.1.gz.dpkg-tmp a symlink to 
/etc/alternatives/editor.ru.UTF-8.1.gz: No such file or directory
dpkg: error processing vim-gnome (--configure):
 subprocess post-installation script returned error exit status 2
Setting up vim-gtk (7.0-164+1) ...
update-alternatives: unable to make 
/usr/share/man/ru.UTF-8/man1/editor.1.gz.dpkg-tmp a symlink to 
/etc/alternatives/editor.ru.UTF-8.1.gz: No such file or directory
dpkg: error processing vim-gtk (--configure):
 subprocess post-installation script returned error exit status 2

--End output--

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-howard
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages vim depends on:
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libgpmg1 1.19.6-23   General Purpose Mouse - shared lib
ii  libncurses5  5.5-5   Shared libraries for terminal hand
ii  vim-common   1:7.0-164+1 Vi IMproved - Common files
ii  vim-runtime  1:7.0-164+1 Vi IMproved - Runtime files

vim recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



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

2006-11-17 Thread James Vega
On Fri, Nov 17, 2006 at 11:11:50AM -0700, Larry Lade wrote:
 Package: vim
 Version: 1:7.0-164+1
 Followup-For: Bug #399024
 
 
 Confirmed.
 
 This bug appears in packages vim, vim-gnome, and vim-gtk.
 
 Note this bug also occurs when trying to REMOVE the packages in question. 
 
 --Begin output--
 
 Setting up vim (7.0-164+1) ...
 update-alternatives: unable to make 
 /usr/share/man/ru.UTF-8/man1/editor.1.gz.dpkg-tmp a symlink to 
 /etc/alternatives/editor.ru.UTF-8.1.gz: No such file or directory
 dpkg: error processing vim (--configure):
  subprocess post-installation script returned error exit status 2

This is interesting since the postinst script for 1:7.0-164+1 doesn't
have ru.UTF-8 anywhere in it.  I'm guessing this is because the previous
versions did and we're only removing alternatives on prerm remove not
prerm upgrade.  I'll confirm this and should be able to get a new
upload which fixes it this weekend.

James
-- 
GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED]


signature.asc
Description: Digital signature


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

2006-11-17 Thread Larry Lade

I did a _re-install_ (remove failed with same error) of package vim-tiny.
This bug appears to have disappeared on all packages since. Very strange...
Perhaps this will provide a workaround for the time being.


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

2006-11-17 Thread Dreambuster

Is necessary to make a  apt-get  dist-upgrade  to regulate this.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]