From: Andrey Repin <anrdaemon@yandex.ru>
To: Heavenly Avenger <avenger@avenger.ws>, cygwin@cygwin.com
Subject: Re: Fwd: [fixed] Stubborn ghostscript 9.19 not upgrading to 9.23
Date: Sat, 21 Jul 2018 18:45:00 -0000 [thread overview]
Message-ID: <95496955.20180721122453@yandex.ru> (raw)
In-Reply-To: <6c398205-52ae-0fc1-e248-b9e49862af04@avenger.ws>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2959 bytes --]
Greetings, Heavenly Avenger!
> Sorry, problem solved...
> $ cygcheck -c libgs9
> Cygwin Package Information
> Package             Version       Status
> libgs9Â Â Â Â Â Â Â Â Â Â Â Â Â Â 9.23-1Â Â Â Â Â Â Â Â OK
> $ cygcheck -l libgs9
> /usr/bin/cyggs-9.dll
> $ ls -l /usr/bin/cyggs-9.dll
> -rwxr-xr-x 1 avenger None 11816979 Jun 29Â 2016 /usr/bin/cyggs-9.dll
> Yeah, cygcheck, yeah... (notice 2016 above?) :P
> Seems cygcheck -c does not really pokes checksum of every file in the
> package? I wonder why this didn't report as corrupt.
Checksums change after rebase.
> After reinstalling libgs9:
> $ ls -l /usr/bin/cyggs-9.dll
> -rwxr-xr-x 1 avenger Administrators 12393491 Mar 21 17:58
> /usr/bin/cyggs-9.dll
> $ gs --version
> 9.23
> Works now. I guess I should just search for 2016 DLLs within /usr/bin
> and assume them all as broken, and reinstall the packages. :)
> -------- Forwarded Message --------
> Subject: Stubborn ghostscript 9.19 not upgrading to 9.23
> Date: Fri, 20 Jul 2018 22:58:45 -0300
> From: Heavenly Avenger <avenger@avenger.ws>
> To: cygwin@cygwin.com
> 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
--
With best regards,
Andrey Repin
Saturday, July 21, 2018 12:24:15
Sorry for my terrible english...\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒ÷\a&ö&ÆV×2æFÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöf\x17\x12ðФFö7VÖVçF\x17Föã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöFö72æFÖÀÐ¥Vç7V'67&&R\x06æfó¢\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöÖÂò7Vç7V'67&&R×6×\x06ÆPÐ Ð
next prev parent reply other threads:[~2018-07-21 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 7:58 Heavenly Avenger
2018-07-21 9:35 ` Fwd: [fixed] " Heavenly Avenger
2018-07-21 18:45 ` Andrey Repin [this message]
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=95496955.20180721122453@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=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).