From: Heavenly Avenger <avenger@avenger.ws>
To: cygwin@cygwin.com
Subject: Stubborn ghostscript 9.19 not upgrading to 9.23
Date: Sat, 21 Jul 2018 07:58:00 -0000 [thread overview]
Message-ID: <a225c951-9ca7-58b7-08a3-f9ace62b0c4a@avenger.ws> (raw)
Hello!
I got into this problem that ghostscript refuses to upgrade.
If I try to run a rtf2ps.sh I used to do frequently, I'm getting this:
Looking for the error I see somebody mentioning it should be under
/usr/share/gs/*. I have only /usr/share/ghostscript/*, and it looks like
the same. Therein, I have 9.19 and 9.23 directories, which suggests
there's some leftovers from 9.19. Yet, if I try to find the missing file
(gs_init.ps), I get it within the 9.23 tree. Then it /should/ be good.
Then, moved to /usr/bin and:
$ ./gs --version
9.19
$ ls /usr/share/ghostscript/
9.19Â 9.23Â fonts
I closed all cygwin terminals, checked up whether no cygwin process was
running, and performed a reinstall of the ghostscript package. It reads
9.23 in setup_x86_64.exe, so I left a little confuse as to why it is not
getting updated... maybe the package is nuts? Double checked, gs.exe
process is not running nor stuck.
Any ideas about what's going on here? :) I would prefer to be able to
fully upgrade the package, but if the only way is to keep the old one or
do some hacky symlinks, I guess I would need to live with that. :(
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2018-07-21 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 7:58 Heavenly Avenger [this message]
2018-07-21 9:35 ` Fwd: [fixed] " Heavenly Avenger
2018-07-21 18:45 ` Andrey Repin
2018-07-21 19:10 ` Heavenly Avenger
2018-07-23 8:26 ` Andrey Repin
2018-07-23 14:34 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a225c951-9ca7-58b7-08a3-f9ace62b0c4a@avenger.ws \
--to=avenger@avenger.ws \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).