[Bug 953149] New: Ghostscript 9.18 has no longer e_<SomeError> now gs_error_<SomeError> must be used
http://bugzilla.opensuse.org/show_bug.cgi?id=953149 Bug ID: 953149 Summary: Ghostscript 9.18 has no longer e_<SomeError> now gs_error_<SomeError> must be used Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: All OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening@forge.provo.novell.com Reporter: jsmeix@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Since Ghostscript 9.18 the PostScript interpreter errors were amalgamated with the errors in the graphics library (gserrors.h), see http://bugs.ghostscript.com/show_bug.cgi?id=696317 Examples: e_ExecStackUnderflow -> gs_error_ExecStackUnderflow e_Fatal -> gs_error_Fatal e_NeedInput -> gs_error_NeedInput Packages that still use the e_<SomeError> fail to build with Ghostscript 9.18. The real solution would be to use the gs_error_<SomeError> form. As an interim measure one could add something like: #define e_ExecStackUnderflow gs_error_ExecStackUnderflow #define e_Fatal gs_error_Fatal #define e_NeedInput gs_error_NeedInput -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c1
Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c2
Vincent Untz
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c3
Dominique Leuenberger
$ osc maintainer libspectre Defined in package: X11:common:Factory/libspectre bugowner of libspectre : KDEMaintainers
maintainer of libspectre : group:gnome-maintainers -----------------------------------------------------------------------
That's what I call a joint effort: bugs owned by the KDE Team, package maintained by the GNOME Team :) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c4
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c5
Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c6
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c7
--- Comment #7 from Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c8
Dominique Leuenberger
osc build => succeeded (this is against pure factory, with GS 9.16)
for the build log: + grep -e '\(newer\|matches\)' ++ rpm -q --qf '%{version}' ghostscript-devel + zypper vcmp 9.16 9.18 + exit 0 ==> no patching done - good then I did:
osc getbinaries Printing ghostscript openSUSE_Factory x86_64 osc build -p binaries => succeeded (this is now against factory, but with gs overloaded to 9.18)
relevant part of the build log: + grep -e '\(newer\|matches\)' ++ rpm -q --qf '%{version}' ghostscript-devel + zypper vcmp 9.18 9.18 9.18 matches 9.18 + echo 'Patch #0 (libspectre-gs-9.18.patch):' Patch #0 (libspectre-gs-9.18.patch): + /usr/bin/cat /home/abuild/rpmbuild/SOURCES/libspectre-gs-9.18.patch + /usr/bin/patch -p1 --fuzz=0 patching file libspectre/spectre-gs.c + exit 0 ==> file has been patched - good Can you please check if the same .spec modifications work for all cases you care for? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c9
--- Comment #9 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c10
--- Comment #10 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c11
--- Comment #11 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c12
--- Comment #12 from Dominique Leuenberger
A general recommendation when doing
read X Y Z < <(output of a command)
it is fail-safe programming to always add a dummy variable where possibly trailing junk gets stored.
Will remember that.. on 13.2, though, the issue is that all data ends up in GS_MAJ for some reason -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c13
--- Comment #13 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c14
--- Comment #14 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c15
--- Comment #15 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c16
--- Comment #16 from Johannes Meixner
http://bugzilla.opensuse.org/show_bug.cgi?id=953149
http://bugzilla.opensuse.org/show_bug.cgi?id=953149#c17
Johannes Meixner
From my point of view building home:dimstar:Factory/libspectre works well.
-- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com