Hello community, here is the log from the commit of package ghostscript for openSUSE:Factory checked in at 2014-09-25 08:42:28 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/ghostscript (Old) and /work/SRC/openSUSE:Factory/.ghostscript.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "ghostscript" Changes: -------- --- /work/SRC/openSUSE:Factory/ghostscript/ghostscript-mini.changes 2014-03-31 20:43:10.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.ghostscript.new/ghostscript-mini.changes 2014-09-25 08:42:43.000000000 +0200 @@ -1,0 +2,49 @@ +Tue Sep 23 10:14:28 CEST 2014 - jsm...@suse.de + +- Version upgrade to 9.15. Primarily a maintenance release. + There are no recorded incompatible changes (as of this writing). + Highlights in this release include: + * Ghostscript now supports the PDF security handler revision 6. + * The pdfwrite and ps2write (and related) devices can now be + forced to "flatten" glyphs into "basic" marking operations + (rather than writing fonts to the output), by giving + the -dNoOutputFonts command line option (defaults to "false"). + * PostScript programs can now use get_params or get_param to + determine if a page contains color markings by reading the + pageneutralcolor state from the device (so whether the page + is "color" or "mono"). Note that this is only accurate when in + clist mode, so -dMaxBitmap=0 and -dGrayDetection=true should + both be used. + * The pdfwrite device now supports Link annotations with GoTo + and GoToR actions. + * The pdfwrite device now supports BMC/BDC/EMC pdfmarks + * Regarding the new color management for the pdfwrite device + introduced in the previous release, the proscription on using + the new color management when producing PDF/A-1 compliant files + is now lifted. To reiterate, also, with the new color + management implementation, using the UseCIEColor option is + strongly discouraged. For further information on the new + pdfwrite color management, see in Ps2pdf.htm the + "Color Conversion and Management" section. + * Plus the usual round of bug fixes, compatibility changes, + and incremental improvements. + For details see the News.htm and History9.htm files. + +------------------------------------------------------------------- +Wed Sep 17 12:17:47 CEST 2014 - jsm...@suse.de + +- Version upgrade to 9.15rc2 (second release candidate for 9.15). + Ghostscript upstream QA highlighted a couple of issues + that they felt warranted a fresh release candidate. + For details see the History9.htm file. + +------------------------------------------------------------------- +Tue Sep 9 16:06:31 CEST 2014 - jsm...@suse.de + +- Version upgrade to 9.15rc1 (first release candidate for 9.15). + For details see the News.htm and History9.htm files. +- ppc64le-support.patch is no longer needed because + it is fixed in the upstream sources. +- Removed trailing whitespaces in spec file and changes file. + +------------------------------------------------------------------- --- /work/SRC/openSUSE:Factory/ghostscript/ghostscript.changes 2014-08-30 16:03:41.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.ghostscript.new/ghostscript.changes 2014-09-25 08:42:43.000000000 +0200 @@ -1,0 +2,49 @@ +Tue Sep 23 10:14:28 CEST 2014 - jsm...@suse.de + +- Version upgrade to 9.15. Primarily a maintenance release. + There are no recorded incompatible changes (as of this writing). + Highlights in this release include: + * Ghostscript now supports the PDF security handler revision 6. + * The pdfwrite and ps2write (and related) devices can now be + forced to "flatten" glyphs into "basic" marking operations + (rather than writing fonts to the output), by giving + the -dNoOutputFonts command line option (defaults to "false"). + * PostScript programs can now use get_params or get_param to + determine if a page contains color markings by reading the + pageneutralcolor state from the device (so whether the page + is "color" or "mono"). Note that this is only accurate when in + clist mode, so -dMaxBitmap=0 and -dGrayDetection=true should + both be used. + * The pdfwrite device now supports Link annotations with GoTo + and GoToR actions. + * The pdfwrite device now supports BMC/BDC/EMC pdfmarks + * Regarding the new color management for the pdfwrite device + introduced in the previous release, the proscription on using + the new color management when producing PDF/A-1 compliant files + is now lifted. To reiterate, also, with the new color + management implementation, using the UseCIEColor option is + strongly discouraged. For further information on the new + pdfwrite color management, see in Ps2pdf.htm the + "Color Conversion and Management" section. + * Plus the usual round of bug fixes, compatibility changes, + and incremental improvements. + For details see the News.htm and History9.htm files. + +------------------------------------------------------------------- +Wed Sep 17 12:17:47 CEST 2014 - jsm...@suse.de + +- Version upgrade to 9.15rc2 (second release candidate for 9.15). + Ghostscript upstream QA highlighted a couple of issues + that they felt warranted a fresh release candidate. + For details see the History9.htm file. + +------------------------------------------------------------------- +Tue Sep 9 16:06:31 CEST 2014 - jsm...@suse.de + +- Version upgrade to 9.15rc1 (first release candidate for 9.15). + For details see the News.htm and History9.htm files. +- ppc64le-support.patch is no longer needed because + it is fixed in the upstream sources. +- Removed trailing whitespaces in spec file and changes file. + +------------------------------------------------------------------- Old: ---- ghostscript-9.14.tar.gz ppc64le-support.patch New: ---- ghostscript-9.15.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ ghostscript-mini.spec ++++++ --- /var/tmp/diff_new_pack.pVHN5c/_old 2014-09-25 08:42:44.000000000 +0200 +++ /var/tmp/diff_new_pack.pVHN5c/_new 2014-09-25 08:42:44.000000000 +0200 @@ -27,49 +27,44 @@ License: AGPL-3.0 Group: System/Libraries Url: http://www.ghostscript.com/ -# Special version needed for Ghostscript release candidates e.g. "Version: 9.pre10rc1": -# Version 9.10rc1 would be newer than 9.10 (run "zypper vcmp 9.10rc1 9.10") because the rpmvercmp algorithm -# would treat 9.10rc1 as 9.10.rc.1 (alphabetic and numeric sections get separated into different elements) -# and 9.10.rc.1 is newer than 9.10 (it has one more element in the list while previous elements are equal) -# so that we use an alphabetic prefix to make it older than 9.10 (numbers are considered newer than letters): -#Version: 9.pre10rc1 +# Special version needed for Ghostscript release candidates (e.g. "Version: 9.14pre15rc1" for 9.15rc1). +# Version 9.15rc1 would be newer than 9.15 (run "zypper vcmp 9.15rc1 9.15") because the rpmvercmp algorithm +# would treat 9.15rc1 as 9.15.rc.1 (alphabetic and numeric sections get separated into different elements) +# and 9.15.rc.1 is newer than 9.15 (it has one more element in the list while previous elements are equal) +# so that we use an alphabetic prefix 'pre' to make it older than 9.15 (numbers are considered newer than letters). +# But only with the alphabetic prefix "9.pre15rc1" would be older than the previous version number "9.14" +# because rpmvercmp would treat 9.pre15rc1 as 9.pre.15.rc1 and letters are older than numbers +# so that we keep additionally the previous version number to upgrade from the previous version: +#Version: 9.14pre15rc2 # Normal version for Ghostscript releases is the upstream version: -Version: 9.14 +Version: 9.15 Release: 0 # tarball_version is used below to specify the directory via "setup -n": -# Special tarball_version needed for Ghostscript release candidates e.g. "define tarball_version 9.10rc1". +# Special tarball_version needed for Ghostscript release candidates e.g. "define tarball_version 9.15rc1". # For Ghostscript releases tarball_version and version are the same (i.e. the upstream version): %define tarball_version %{version} +#define tarball_version 9.15rc2 # built_version is used below in the install and files sections: -# Separated built_version needed in case of Ghostscript release candidates e.g. "define built_version 9.10". +# Separated built_version needed in case of Ghostscript release candidates e.g. "define built_version 9.15". # For Ghostscript releases built_version and version are the same (i.e. the upstream version): %define built_version %{version} +#define built_version 9.15 # Source0...Source9 is for sources from upstream: # Special URLs for Ghostscript release candidates: -# URL for Source0: http://www.ghostscript.com/~chrisl/ghostscript-9.10rc1.tar.gz -# URL for MD5 checksums: http://www.ghostscript.com/~chrisl/MD5SUMS -# MD5 checksum for Source0: 0cdf23c5dff76040983bca74675f88be -#Source0: http://www.ghostscript.com/~chrisl/ghostscript-9.10rc1.tar.gz +# URL for Source0: http://www.ghostscript.com/~chrisl/ghostscript-9.15rc2.tar.gz +# URL for MD5 checksums: http://www.ghostscript.com/~chrisl/MD5SUMS or http://www.ghostscript.com/~chrisl/MD5SUM +# MD5 checksum for Source0: 20bffacff52552aa1c430fe64403fb68 +#Source0: http://www.ghostscript.com/~chrisl/ghostscript-9.15rc2.tar.gz # Normal URLs for Ghostscript releases: -# URL for Source0: http://downloads.ghostscript.com/public/ghostscript-9.14.tar.gz +# URL for Source0: http://downloads.ghostscript.com/public/ghostscript-9.15.tar.gz # URL for MD5 checksums: http://downloads.ghostscript.com/public/MD5SUMS -# MD5 checksum for Source0: 586494befb443363338c1b6379f13973 +# MD5 checksum for Source0: 5a78ab0990ff6ec3a103576bc8777c46 Source0: http://downloads.ghostscript.com/public/ghostscript-%{version}.tar.gz # Patch0...Patch9 is for patches from upstream: # # Source10...Source99 is for sources from SUSE which are intended for upstream: # # Patch10...Patch99 is for patches from SUSE which are intended for upstream: -# Patch10 ppc64le-support.patch from IBM fixes endianness in lcms (the Little-CMS library) -# to support the new architecture ppc64le (IBM Power PC Little Endian architecture) -# because ppc64 is big-endian and ppc64le is little-endian and lcms has a hard-coded -# check that assumes PowerPC is always big-endian which is incorrect on ppc64le. -# The fix is already in the main Little-CMS repository by this Git commit -# https://github.com/mm2/Little-CMS/commit/b4f5c91a2c1582bd284f0d0f49cb43e2c2235a79 -# (There are some cosmetic changes in the patch as it went upstream.) -# It is not yet in the imported copy in Ghostscript. -# IBM will work with upstream to get the fix imported too. -Patch10: ppc64le-support.patch # # Source100...Source999 is for sources from SUSE which are not intended for upstream: # @@ -142,8 +137,6 @@ # Be quiet when unpacking and # use a directory name matching Source0 to make it work also for ghostscript-mini: %setup -q -n ghostscript-%{tarball_version} -# Patch10 ppc64le-support.patch from IBM fixes endianness in lcms (the Little-CMS library): -%patch10 -p1 %build # Set our preferred architecture-specific flags for the compiler and linker: ++++++ ghostscript.spec ++++++ --- /var/tmp/diff_new_pack.pVHN5c/_old 2014-09-25 08:42:44.000000000 +0200 +++ /var/tmp/diff_new_pack.pVHN5c/_new 2014-09-25 08:42:44.000000000 +0200 @@ -33,49 +33,44 @@ License: AGPL-3.0 Group: System/Libraries Url: http://www.ghostscript.com/ -# Special version needed for Ghostscript release candidates e.g. "Version: 9.pre10rc1": -# Version 9.10rc1 would be newer than 9.10 (run "zypper vcmp 9.10rc1 9.10") because the rpmvercmp algorithm -# would treat 9.10rc1 as 9.10.rc.1 (alphabetic and numeric sections get separated into different elements) -# and 9.10.rc.1 is newer than 9.10 (it has one more element in the list while previous elements are equal) -# so that we use an alphabetic prefix to make it older than 9.10 (numbers are considered newer than letters): -#Version: 9.pre10rc1 +# Special version needed for Ghostscript release candidates (e.g. "Version: 9.14pre15rc1" for 9.15rc1). +# Version 9.15rc1 would be newer than 9.15 (run "zypper vcmp 9.15rc1 9.15") because the rpmvercmp algorithm +# would treat 9.15rc1 as 9.15.rc.1 (alphabetic and numeric sections get separated into different elements) +# and 9.15.rc.1 is newer than 9.15 (it has one more element in the list while previous elements are equal) +# so that we use an alphabetic prefix 'pre' to make it older than 9.15 (numbers are considered newer than letters). +# But only with the alphabetic prefix "9.pre15rc1" would be older than the previous version number "9.14" +# because rpmvercmp would treat 9.pre15rc1 as 9.pre.15.rc1 and letters are older than numbers +# so that we keep additionally the previous version number to upgrade from the previous version: +#Version: 9.14pre15rc2 # Normal version for Ghostscript releases is the upstream version: -Version: 9.14 +Version: 9.15 Release: 0 # tarball_version is used below to specify the directory via "setup -n": -# Special tarball_version needed for Ghostscript release candidates e.g. "define tarball_version 9.10rc1". +# Special tarball_version needed for Ghostscript release candidates e.g. "define tarball_version 9.15rc1". # For Ghostscript releases tarball_version and version are the same (i.e. the upstream version): %define tarball_version %{version} +#define tarball_version 9.15rc2 # built_version is used below in the install and files sections: -# Separated built_version needed in case of Ghostscript release candidates e.g. "define built_version 9.10". +# Separated built_version needed in case of Ghostscript release candidates e.g. "define built_version 9.15". # For Ghostscript releases built_version and version are the same (i.e. the upstream version): %define built_version %{version} +#define built_version 9.15 # Source0...Source9 is for sources from upstream: # Special URLs for Ghostscript release candidates: -# URL for Source0: http://www.ghostscript.com/~chrisl/ghostscript-9.10rc1.tar.gz -# URL for MD5 checksums: http://www.ghostscript.com/~chrisl/MD5SUMS -# MD5 checksum for Source0: 0cdf23c5dff76040983bca74675f88be -#Source0: http://www.ghostscript.com/~chrisl/ghostscript-9.10rc1.tar.gz +# URL for Source0: http://www.ghostscript.com/~chrisl/ghostscript-9.15rc2.tar.gz +# URL for MD5 checksums: http://www.ghostscript.com/~chrisl/MD5SUMS or http://www.ghostscript.com/~chrisl/MD5SUM +# MD5 checksum for Source0: 20bffacff52552aa1c430fe64403fb68 +#Source0: http://www.ghostscript.com/~chrisl/ghostscript-9.15rc2.tar.gz # Normal URLs for Ghostscript releases: -# URL for Source0: http://downloads.ghostscript.com/public/ghostscript-9.14.tar.gz +# URL for Source0: http://downloads.ghostscript.com/public/ghostscript-9.15.tar.gz # URL for MD5 checksums: http://downloads.ghostscript.com/public/MD5SUMS -# MD5 checksum for Source0: 586494befb443363338c1b6379f13973 +# MD5 checksum for Source0: 5a78ab0990ff6ec3a103576bc8777c46 Source0: http://downloads.ghostscript.com/public/ghostscript-%{version}.tar.gz # Patch0...Patch9 is for patches from upstream: # # Source10...Source99 is for sources from SUSE which are intended for upstream: # # Patch10...Patch99 is for patches from SUSE which are intended for upstream: -# Patch10 ppc64le-support.patch from IBM fixes endianness in lcms (the Little-CMS library) -# to support the new architecture ppc64le (IBM Power PC Little Endian architecture) -# because ppc64 is big-endian and ppc64le is little-endian and lcms has a hard-coded -# check that assumes PowerPC is always big-endian which is incorrect on ppc64le. -# The fix is already in the main Little-CMS repository by this Git commit -# https://github.com/mm2/Little-CMS/commit/b4f5c91a2c1582bd284f0d0f49cb43e2c2235a79 -# (There are some cosmetic changes in the patch as it went upstream.) -# It is not yet in the imported copy in Ghostscript. -# IBM will work with upstream to get the fix imported too. -Patch10: ppc64le-support.patch # # Source100...Source999 is for sources from SUSE which are not intended for upstream: # @@ -265,8 +260,6 @@ # Be quiet when unpacking and # use a directory name matching Source0 to make it work also for ghostscript-mini: %setup -q -n ghostscript-%{tarball_version} -# Patch10 ppc64le-support.patch from IBM fixes endianness in lcms (the Little-CMS library): -%patch10 -p1 %build # Set our preferred architecture-specific flags for the compiler and linker: ++++++ ghostscript-9.14.tar.gz -> ghostscript-9.15.tar.gz ++++++ /work/SRC/openSUSE:Factory/ghostscript/ghostscript-9.14.tar.gz /work/SRC/openSUSE:Factory/.ghostscript.new/ghostscript-9.15.tar.gz differ: char 5, line 1 -- To unsubscribe, e-mail: opensuse-commit+unsubscr...@opensuse.org For additional commands, e-mail: opensuse-commit+h...@opensuse.org
