Hello community,

here is the log from the commit of package vim for openSUSE:Factory checked in 
at 2014-03-15 17:35:50
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/vim (Old)
 and      /work/SRC/openSUSE:Factory/.vim.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "vim"

Changes:
--------
--- /work/SRC/openSUSE:Factory/vim/vim.changes  2014-03-09 18:35:05.000000000 
+0100
+++ /work/SRC/openSUSE:Factory/.vim.new/vim.changes     2014-03-15 
17:35:51.000000000 +0100
@@ -1,0 +2,16 @@
+Thu Mar 13 11:13:57 UTC 2014 - [email protected]
+
+- Updated to revision 205, fixes the following problems
+  * Typos in messages.
+  * Python tests fail.
+  * Can't build Vim with Perl when -Dusethreads is not specified for
+    building Perl, and building Vim with --enable-perlinterp=dynamic.
+  * (issue 197) ]P doesn't paste over Visual selection.
+  * Too many #ifdefs in the code.
+  * 'lispwords' is a global option.
+  * Parsing 'errorformat' is not correct.
+  * A mapping where the second byte is 0x80 doesn't work.
+  * ":mksession" writes command to move to second argument while it
+    does not exist.  When it does exist the order might be wrong.
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ vim.spec ++++++
--- /var/tmp/diff_new_pack.ETsy2f/_old  2014-03-15 17:35:52.000000000 +0100
+++ /var/tmp/diff_new_pack.ETsy2f/_new  2014-03-15 17:35:52.000000000 +0100
@@ -17,7 +17,7 @@
 
 
 %define pkg_version 7.4
-%define official_ptchlvl 192
+%define official_ptchlvl 205
 %define VIM_SUBDIR vim74
 %define site_runtimepath /usr/share/vim/site
 %define make make VIMRCLOC=/etc VIMRUNTIMEDIR=/usr/share/vim/current 
MAKE="make -e" %{?_smp_mflags}

++++++ vim-7.4-patches.tar.bz2 ++++++
++++ 2738 lines of diff (skipped)

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to