Hello community,

here is the log from the commit of package fontpackages for openSUSE:Factory 
checked in at 2015-02-06 10:57:38
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/fontpackages (Old)
 and      /work/SRC/openSUSE:Factory/.fontpackages.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "fontpackages"

Changes:
--------
--- /work/SRC/openSUSE:Factory/fontpackages/fontpackages.changes        
2015-02-05 10:59:00.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.fontpackages.new/fontpackages.changes   
2015-02-06 10:57:40.000000000 +0100
@@ -1,0 +2,6 @@
+Thu Feb  5 11:16:17 UTC 2015 - [email protected]
+
+- Revert last pathname change because libzypp expects a fixed
+  filename pattern. release changes have to caught in build-compare
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ rpm-macros.fonts-config ++++++
--- /var/tmp/diff_new_pack.z79dY0/_old  2015-02-06 10:57:41.000000000 +0100
+++ /var/tmp/diff_new_pack.z79dY0/_new  2015-02-06 10:57:41.000000000 +0100
@@ -7,8 +7,10 @@
 %_fontsconfavaildir      %{_datadir}/%{name}/conf.avail
 # private
 %__fontsconfigrunflag     /var/run/fontpackages/reconfigure-fonts
-%__fontsupdatescript      
/var/adm/update-scripts/reconfigure-fonts-%{name}-%{version}-%{release}
-%__fontsupdatescript_cjk  
/var/adm/update-scripts/reconfigure-cjk-fonts-%{name}-%{version}-%{release}
+# The pattern is fixed within libzypp:
+# /var/adm/update-scripts/name-version-release-anything
+%__fontsupdatescript      
/var/adm/update-scripts/%{name}-%{version}-%{release}-reconfigure-fonts
+%__fontsupdatescript_cjk  
/var/adm/update-scripts/%{name}-%{version}-%{release}-reconfigure-cjk-fonts
 
 # macro: link_avail_to_system_fontsconf name
 # (takes exactly one argument, name of configuration file)

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

Reply via email to