Hello community,

here is the log from the commit of package libchewing for openSUSE:Factory 
checked in at 2013-04-29 09:54:17
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libchewing (Old)
 and      /work/SRC/openSUSE:Factory/.libchewing.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libchewing", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/libchewing/libchewing.changes    2013-04-26 
13:27:08.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.libchewing.new/libchewing.changes       
2013-04-29 09:54:18.000000000 +0200
@@ -1,0 +2,5 @@
+Fri Apr 26 19:31:22 UTC 2013 - [email protected]
+
+- revert unnessary renaming chewing-devel back to libchewing-devel.
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ libchewing.spec ++++++
--- /var/tmp/diff_new_pack.r09Pkd/_old  2013-04-29 09:54:19.000000000 +0200
+++ /var/tmp/diff_new_pack.r09Pkd/_new  2013-04-29 09:54:19.000000000 +0200
@@ -47,15 +47,13 @@
 %description
 Intelligent phonetic input method library for traditional Chinese.
 
-%package -n chewing-devel
+%package devel
 Summary:        Development package for chewing
 Group:          Development/Libraries/C and C++
 Requires:       %{name} = %{version}
 Requires:       python-chewing = %{version}
-Provides:       %{name}-devel = %{version}
-Obsoletes:      %{name}-devel = %{version}
 
-%description -n chewing-devel
+%description devel
 Development package for chewing (An Intelligent phonetic input method library 
for traditional Chinese)
 
 %package -n %lname
@@ -193,7 +191,7 @@
 %{_bindir}/zhuindict_compile
 %doc %{_docdir}/chewing-utils
 
-%files -n chewing-devel
+%files devel
 %defattr(-, root, root)
 %{_includedir}/chewing/
 %{_libdir}/libchewing.so

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

Reply via email to