Hello community,

here is the log from the commit of package ghostscript-fonts for 
openSUSE:Factory checked in at 2012-10-07 18:59:03
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/ghostscript-fonts (Old)
 and      /work/SRC/openSUSE:Factory/.ghostscript-fonts.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "ghostscript-fonts", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:Factory/ghostscript-fonts/ghostscript-fonts.changes      
2012-08-12 15:25:31.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.ghostscript-fonts.new/ghostscript-fonts.changes 
2012-10-07 18:59:05.000000000 +0200
@@ -1,0 +2,46 @@
+Fri Sep 28 16:35:29 CEST 2012 - [email protected]
+
+- Set the version is the same version as the current ghostscript
+  package i.e. 9.06 because this ghostscript-fonts-* packages
+  are the right ones for this Ghostscript version.
+
+-------------------------------------------------------------------
+Fri Sep 28 10:46:03 CEST 2012 - [email protected]
+
+- Have SuSEconfig.pango stuff in RPM scriptlets only
+  if suse_version < 1220 because since openSUSE 12.2
+  there is no longer SuSEconfig.pango (see the "declined"
+  comment of OBS submitrequest 136232).
+
+-------------------------------------------------------------------
+Thu Sep 27 13:22:44 CEST 2012 - [email protected]
+
+- Using an absolute path as source in symbolic link in spec file
+  to avoid an issue with /usr/sbin/Check in SLE11, SLE_11_SP1,
+  and SLE_11_SP2 that would wrongly convert a relative path
+  ../ghostscript/fonts into a ../ghostscript/fonts.gz file.
+  Afterwards /usr/lib/rpm/brp-symlink converts it to a relative
+  path so that the binary RPM gets the intended symbolic link
+  /usr/share/fonts/ghostscript -> ../ghostscript/fonts
+  (bnc#778879).
+
+-------------------------------------------------------------------
+Wed Sep 26 10:09:22 CEST 2012 - [email protected]
+
+- Provide a link /usr/share/fonts/ghostscript which points to
+  /usr/share/ghostscript/fonts (the directory where Ghostscript
+  expects its fonts) to make the Ghostscript fonts also appear
+  in the directory /usr/share/fonts/ where applications
+  search for fonts (bnc#778879).
+
+-------------------------------------------------------------------
+Tue Sep 25 14:58:06 CEST 2012 - [email protected]
+
+- Fix the negligent changes done by the below "prepare spec file
+  for dropping SuSEconfig.fonts" so that it builds again for
+  all released openSUSE versions (up to 12.2) because only
+  if suse_version > 1220 one can BuildRequire fontpackages-devel
+  which provides the RPM macros like reconfigure_fonts_post,
+  reconfigure_fonts_postun, and reconfigure_fonts_posttrans.
+
+-------------------------------------------------------------------

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

Other differences:
------------------
++++++ ghostscript-fonts.spec ++++++
--- /var/tmp/diff_new_pack.cK9fT2/_old  2012-10-07 18:59:06.000000000 +0200
+++ /var/tmp/diff_new_pack.cK9fT2/_new  2012-10-07 18:59:06.000000000 +0200
@@ -18,7 +18,11 @@
 
 Name:           ghostscript-fonts
 BuildArch:      noarch
+# Prepare spec file for dropping SuSEconfig.fonts
+# see https://features.opensuse.org/313536
+%if 0%{?suse_version} > 1220
 BuildRequires:  fontpackages-devel
+%endif
 # t1utils is needed to convert PostScript Type 1 font program data (*.pfb)
 # to PostScript (*.pfa) so that ghostscript-fonts-std-8.11.patch can be applied
 # and afterwards back to PostScript Type 1 font program data:
@@ -37,7 +41,7 @@
 # than the old ghostscript-fonts-* sub-packages, the existing versioning scheme
 # is still used here. This versioning scheme makes sense because this
 # ghostscript-fonts-* packages are the right ones for this Ghostscript version:
-Version:        9.05
+Version:        9.06
 Release:        0
 # Source0...Source9 is for sources from upstream:
 # URL for Source0: 
http://mirror.cs.wisc.edu/pub/mirrors/ghost/fonts/ghostscript-fonts-std-8.11.tar.gz
@@ -82,13 +86,13 @@
 Optional Fonts for Ghostscript
 in the package ghostscript-fonts-other.
 
+
 %package std
 Summary:        Basic Fonts for Ghostscript
 Group:          Productivity/Publishing/PS
 PreReq:         coreutils %suseconfig_fonts_prereq
 
 %description std
-
 Several Type 1 basic PostScript fonts.
 Times, Helvetica, Courier, Symbol, etc.
 Contributed by URW++ Design and Development
@@ -106,7 +110,6 @@
 Requires:       ghostscript-fonts-std
 
 %description other
-
 A miscellaneous set including Cyrillic,
 kana, and fonts derived from the free
 Hershey fonts, with improvements (such as
@@ -116,17 +119,20 @@
 you can read about them in more detail in
 the documentation on Hershey fonts.
 
+
 %prep
 # Be quiet when unpacking and
 # create directory (and change to it) before unpacking Source0 and
-# additionally unpack Source1 after changing directory
+# additionally unpack Source1 after changing directory:
 %setup -q -c %{name}-%{version} -a 1
 
 %build
 # There is nothing to "make" as the sources contain plain font files.
 
 %install
-# Install the fonts into the /usr/share/ghostscript/fonts/ directory,
+# Install the fonts into the /usr/share/ghostscript/fonts/ directory
+# which is the Ghostscript upstream standard directory where
+# Ghostscript looks first and foremost for its fonts
 # see section "3.1 Fonts" in doc/Install.htm in the Ghostscript sources:
 FONT_INSTALL_DIR=%{buildroot}%{_datadir}/ghostscript/fonts
 install -d -m755 $FONT_INSTALL_DIR
@@ -147,50 +153,111 @@
    rm -vf $PFA
 done
 popd
+# Provide a link to make the Ghostscript fonts also appear in the directory
+# /usr/share/fonts/ where applications (including X11) search for fonts.
+# A usr/share/fonts/ sub-directory does not exist in the buildroot:
+install -d -m 755 %{buildroot}%{_datadir}/fonts
+# Using an absolute path as source in symbolic link to avoid an issue with 
/usr/sbin/Check
+# in SLE11, SLE_11_SP1, and SLE_11_SP2 that would wrongly convert a relative
+# path ../ghostscript/fonts into a ../ghostscript/fonts.gz file,
+# see http://lists.opensuse.org/opensuse-packaging/2012-09/msg00239.html
+# Afterwards /usr/lib/rpm/brp-symlink converts it to a relative path so that 
the binary RPM
+# gets the intended symbolic link /usr/share/fonts/ghostscript -> 
../ghostscript/fonts
+ln -s %{_datadir}/ghostscript/fonts %{buildroot}%{_datadir}/fonts/ghostscript
 
 # Use traditional bash scriptlet with an explicite "exit 0" line at the end to 
be fail safe
 # see http://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets
+# Only if suse_version > 1220 it BuildRequires fontpackages-devel which 
provides reconfigure_fonts_post.
+# Since openSUSE 12.2 there is no SuSEconfig.pango (have it only in the 
scriptlet if suse_version < 1220):
 %post std
+%if 0%{?suse_version} > 1220
 %reconfigure_fonts_post
+%else
+if test -x sbin/conf.d/SuSEconfig.fonts
+then %run_suseconfig -m fonts
+fi
+%endif
+%if 0%{?suse_version} < 1220
 if test -x sbin/conf.d/SuSEconfig.pango
 then %run_suseconfig -m pango
 fi
+%endif
 exit 0
 
 # Use traditional bash scriptlet with an explicite "exit 0" line at the end to 
be fail safe
 # see http://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets
+# Only if suse_version > 1220 it BuildRequires fontpackages-devel which 
provides reconfigure_fonts_postun.
+# Since openSUSE 12.2 there is no SuSEconfig.pango (have it only in the 
scriptlet if suse_version < 1220):
 %postun std
+%if 0%{?suse_version} > 1220
 %reconfigure_fonts_postun
+%else
+if test -x sbin/conf.d/SuSEconfig.fonts
+then %run_suseconfig -m fonts
+fi
+%endif
+%if 0%{?suse_version} < 1220
 if test -x sbin/conf.d/SuSEconfig.pango
 then %run_suseconfig -m pango
 fi
+%endif
 exit 0
 
+%if 0%{?suse_version} > 1220
+# Use traditional bash scriptlet with an explicite "exit 0" line at the end to 
be fail safe
+# see http://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets
+# Only if suse_version > 1220 it BuildRequires fontpackages-devel which 
provides reconfigure_fonts_posttrans:
 %posttrans std
 %reconfigure_fonts_posttrans
 exit 0
+%endif
 
 # Use traditional bash scriptlet with an explicite "exit 0" line at the end to 
be fail safe
 # see http://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets
+# Only if suse_version > 1220 it BuildRequires fontpackages-devel which 
provides reconfigure_fonts_post.
+# Since openSUSE 12.2 there is no SuSEconfig.pango (have it only in the 
scriptlet if suse_version < 1220):
 %post other
+%if 0%{?suse_version} > 1220
 %reconfigure_fonts_post
+%else
+if test -x sbin/conf.d/SuSEconfig.fonts
+then %run_suseconfig -m fonts
+fi
+%endif
+%if 0%{?suse_version} < 1220
 if test -x sbin/conf.d/SuSEconfig.pango
 then %run_suseconfig -m pango
 fi
+%endif
 exit 0
 
 # Use traditional bash scriptlet with an explicite "exit 0" line at the end to 
be fail safe
 # see http://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets
+# Only if suse_version > 1220 it BuildRequires fontpackages-devel which 
provides reconfigure_fonts_postun.
+# Since openSUSE 12.2 there is no SuSEconfig.pango (have it only in the 
scriptlet if suse_version < 1220):
 %postun other
+%if 0%{?suse_version} > 1220
 %reconfigure_fonts_postun
+%else
+if test -x sbin/conf.d/SuSEconfig.fonts
+then %run_suseconfig -m fonts
+fi
+%endif
+%if 0%{?suse_version} < 1220
 if test -x sbin/conf.d/SuSEconfig.pango
 then %run_suseconfig -m pango
 fi
+%endif
 exit 0
 
+%if 0%{?suse_version} > 1220
+# Use traditional bash scriptlet with an explicite "exit 0" line at the end to 
be fail safe
+# see http://en.opensuse.org/openSUSE:Packaging_scriptlet_snippets
+# Only if suse_version > 1220 it BuildRequires fontpackages-devel which 
provides reconfigure_fonts_posttrans:
 %posttrans other
 %reconfigure_fonts_posttrans
 exit 0
+%endif
 
 %files
 %defattr(-, root, root)
@@ -199,6 +266,7 @@
 %files std
 %defattr(0644,root,root,0755)
 %verify(not md5 size mtime) %{_datadir}/ghostscript/fonts/fonts.*
+%{_datadir}/fonts/ghostscript
 %dir %{_datadir}/ghostscript
 %dir %{_datadir}/ghostscript/fonts
 %{_datadir}/ghostscript/fonts/fonts.dir

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

Reply via email to