[Cooker] vim-common-6.1-4mdk is dangerous
Since: [gc@bi ~] ls -l /usr/share/vim/lang lrwxrwxrwx1 root root 17 Apr 3 05:22 /usr/share/vim/lang - /usr/share/locale/ And now: [gc@bi ~] rpm -qplv /RPMS/vim-common-6.1-4mdk.i586.rpm | grep /usr/share/vim/lang$ drwxr-xr-x2 rootroot0 Apr 17 18:43 /usr/share/vim/lang Installing vim-common-6.1-4mdk screwed up all my /usr/share/locale directory (thx Titi). -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] vim-common-6.1-4mdk is dangerous
Guillaume Cottenceau wrote: Installing vim-common-6.1-4mdk screwed up all my /usr/share/locale directory (thx Titi). Didn't it conflict with anything ? Here I got file conflicts with : kde-i18n-fr-2.2.2-1mdk koffice-i18n-fr-1.1.1-1mdk cups-common-1.1.14-3mdk locales-fr-2.3.1.3-1mdk locales-ja-2.3.1.3-1mdk libgimpprint1-4.2.1-0.pre5.1mdk So I didn't install it !
Re: [Cooker] vim-common-6.1-4mdk is dangerous
Pascal Terjan [EMAIL PROTECTED] writes: Guillaume Cottenceau wrote: Installing vim-common-6.1-4mdk screwed up all my /usr/share/locale directory (thx Titi). Didn't it conflict with anything ? Yes it did. Here I got file conflicts with : kde-i18n-fr-2.2.2-1mdk koffice-i18n-fr-1.1.1-1mdk cups-common-1.1.14-3mdk locales-fr-2.3.1.3-1mdk locales-ja-2.3.1.3-1mdk libgimpprint1-4.2.1-0.pre5.1mdk So I didn't install it ! As for me, it conflicted with libgimpprint1-4.2.1-0.pre5.1mdk, so it was not a really important conflict. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] vim-common-6.1-4mdk is dangerous
On 18 Apr 2002, Guillaume Cottenceau wrote:
Since:
[gc@bi ~] ls -l /usr/share/vim/lang
lrwxrwxrwx1 root root 17 Apr 3 05:22 /usr/share/vim/lang -
/usr/share/locale/
And now:
[gc@bi ~] rpm -qplv /RPMS/vim-common-6.1-4mdk.i586.rpm | grep /usr/share/vim/lang$
drwxr-xr-x2 rootroot0 Apr 17 18:43 /usr/share/vim/lang
Installing vim-common-6.1-4mdk screwed up all my
/usr/share/locale directory (thx Titi).
Luckily I stopped when urpmi complains about conflict between
vim and locales-*. Otherwise all my customized translations will
be burned in hell as well. Such changes ought to put into
real machine testing before releasing.
Attached a patch to check carefully whether $datadir/vim/lang
is a real directory before removing it.
Besides, I remembered somebody suggested to keep /bin/vi link
to /bin/vim-minimal forever, so that one can still use vi if
/usr is not mounted. Is it acceptable?
--
Abel Cheung
GPG Key: (0xC67186FF) http://deaddog.org/gpg.asc
--- vim.spec2002-04-18 00:42:58.0 +0800
+++ vim.spec.new2002-04-18 17:59:18.0 +0800
-268,7 +268,11
# So we've to symlink locales there
# But to prevent update faillure, we must first be sure a link
# creation won't fail because old directory is still there
-rm -fr %_datadir/vim/lang/*/||:
+if test -d %{_datadir}/vim/lang -a ! -L %{_datadir}/vim/lang; then
+ rm -fr %{_datadir}/vim/lang
+else
+ rm -f %{_datadir}/vim/lang
+fi
%post minimal
update-alternatives --install /bin/vi vi /bin/vim-minimal 10
Re: [Cooker] vim-common-6.1-4mdk is dangerous
Attached a patch to check carefully whether $datadir/vim/lang is a real directory before removing it. Besides, I remembered somebody suggested to keep /bin/vi link to /bin/vim-minimal forever, so that one can still use vi if /usr is not mounted. Is it acceptable? One can still invoke vim-minimal manually even if /usr is not mounted .. the only difference is that they wouldn't have the vi link. -- G.
Re: [Cooker] vim-common-6.1-4mdk is dangerous
On Thu, 18 Apr 2002, Geoffrey Lee wrote: Attached a patch to check carefully whether $datadir/vim/lang is a real directory before removing it. Besides, I remembered somebody suggested to keep /bin/vi link to /bin/vim-minimal forever, so that one can still use vi if /usr is not mounted. Is it acceptable? One can still invoke vim-minimal manually even if /usr is not mounted .. the only difference is that they wouldn't have the vi link. -- G. Yeah you're correct. I missed that :) -- Abel Cheung GPG Key: (0xC67186FF) http://deaddog.org/gpg.asc
Re: [Cooker] vim-common-6.1-4mdk is dangerous
R.I.P. Deaddog [EMAIL PROTECTED] writes: Luckily I stopped when urpmi complains about conflict between vim and locales-*. this is a different problem: locale extermination was due to a fix to let mdk8.2 - mdk8.3/9.0 update conflict is that i owned some directories i should not and other packages do this too. they should be fixed. Otherwise all my customized translations will be burned in hell as well. Such changes ought to put into real machine testing before releasing. it did but i only tested 8.2 update: rpm -Uvh --oldpackage /C/8.2/Mandrake/RPMS/vim*' rpm -Uvh vim-* so i didn't see that cooker got mad :-( Attached a patch to check carefully whether $datadir/vim/lang is a real directory before removing it. applied. thanks Besides, I remembered somebody suggested to keep /bin/vi link to /bin/vim-minimal forever, so that one can still use vi if /usr is not mounted. Is it acceptable? will think about it -- il a ete brule au 28e degre (the naheulbeuk witch) c curieux, gcc fonctionne (gwenole)
