Please adjust $summary as you see fit. 8.71-r1 is the first revision that will compile with libpng14, so anything above that is fine too.
ping?
no word from maintainers in reasonable time, CCing arch's to get -r1 stable. current stable *silently* breaks with libpng14, fails to detect it configure -time. (going with -r1 because it's the last revision before the urw-fonts migration which i don't know is ready or not.)
x86 stable
Updating the request to latest version that fixes quite anoying bug with postscript files reading. (bug 313177) adding x86 back, sorry :]
Stable on amd64
(In reply to comment #4) > Updating the request to latest version that fixes quite anoying bug with > postscript files reading. (bug 313177) > > adding x86 back, sorry :] > But it breaks other things!
So what happened here? =app-text/ghostscript-gpl-8.71-r4 will remain stable or should we drop the keywords and run for -r1?
Grrr no, downgrading would just cause too many headaches. What's done is done. I only wish you would consult someone from printing or fonts herds before doing something like this, as I specifically told samuli on irc we'd like to wait with -r4 stabilization. No one would be happy if I suddenly decided I want some version of KDE or Xorg stable, right?
So what are you doing here? A higher version is stable and you still request to stabilize an older one? Users will use the latest stable version no matter what ( unless you mask it )
(In reply to comment #4) > Updating the request to latest version that fixes quite anoying bug with > postscript files reading. (bug 313177) > > adding x86 back, sorry :] > Bug 313177 is not a regression over to current stable, while bugs 315035 and 317897 are. Therefore this should be pretty straightforward: Stabilize -r1, revert your stable keywords to -r1 if you already stabilized -r4. Like I already asked(!). Then, fix those two bugs and add -r5, remove -r4, get it stable in 30 days. sigh
x86 already stabilized correct version -r1. amd64 stable for -r1, reverted -r4
(In reply to comment #11) > x86 already stabilized correct version -r1. > amd64 stable for -r1, reverted -r4 (Comment 6 suggests that what follows is already known) Reverting -r4 breaks my amd64 system. xfig requires urw-fonts which forbids gnu-gs-fonts-std ghostscript-r1 requires gnu-gs-fonts-std (-r4 does not) I have added ~app-text/ghostscript-gpl-8.71 to package.keywords and all is well here, but reverting -r4 will cause anyone with xfig to do something like this as well
(In reply to comment #12) > (In reply to comment #11) > > x86 already stabilized correct version -r1. > > amd64 stable for -r1, reverted -r4 > > (Comment 6 suggests that what follows is already known) > Reverting -r4 breaks my amd64 system. > xfig requires urw-fonts which forbids gnu-gs-fonts-std > ghostscript-r1 requires gnu-gs-fonts-std (-r4 does not) > > I have added ~app-text/ghostscript-gpl-8.71 to package.keywords > and all is well here, but reverting -r4 will cause anyone with xfig > to do something like this as well > 100% unrelated to this bug, previous stable ghostscript-gpl already depended on gnu-gs-fonts-std, and xfig that depended on urw-fonts was stabilized months ago in bug 264575. yes, this means xfig and ghostscript-gpl can't be installed on the same system, and it's xfig's fault. archteams, please proceed with -r1 as planned.
(In reply to comment #13) > 100% unrelated to this bug, previous stable ghostscript-gpl already depended on It *is* related since urw-fonts-2.4.9 was stabilized as part of this bug and it blocks gnu-gs-fonts-std and gnu-gs-fonts-other, and this stabilization was *not* rolled back when -r4 was rolled back, hence all the issues people are having. If I get home and it's still stable I'll roll it back, but I'd prefer if someone could do it sooner.
(In reply to comment #14) > (In reply to comment #13) > > 100% unrelated to this bug, previous stable ghostscript-gpl already depended on > > It *is* related since urw-fonts-2.4.9 was stabilized as part of this bug and sigh. reverted.
ppc stable
(In reply to comment #15) During the downgrade from -r4 to -r1 the fonts from gnu-gs-fonts-std have been installed in the wrong directory because /usr/share/fonts/default/ghostscript is a symlink in -r4. After the downgrade the symlink is gone and gs no longer finds its fonts when called with -dSAFER (as in bug 322087 comment #5, I experienced exactly the same problem). Renaming /usr/share/fonts/urw-fonts to /usr/share/fonts/default/ghostscript fixed it for me, but there are probably many people with messed up font directories now.
ppc64 stable
Stable for HPPA.
arm stable
alpha/ia64/s390/sh/sparc stable, closing
