Re: Frequent Warning messages using gv
On Sat, 8 Oct 2022 13:09:47 -0400, Ken Brown wrote:
On 10/8/2022 9:01 AM, Jon Turney wrote:
Installing 'xorg-x11-fonts-dpi75' and/or 'xorg-x11-fonts-dpi100' will
probably resolve these warnings.
It's unclear to me if gv needs a dependency on more font packages or
not, since the PS could be using any fonts?
I could go either way on this. On the one hand, gv is a postscript
viewer and has no control over what fonts it might be asked to
display. On the other hand, gv is intended to be run under X11, so
maybe it should require the most basic X11 fonts.
gv requires ghostscript which requires ghostscript-fonts-other and
urw-base35-fonts which should provide a fallback from Helvetica to Nimbus.
Perhaps for older apps and documents urw-base35-fonts-legacy could or
should (also) be included?
Could that solve the problem, or would it still require
xorg-x11-fonts-dpi{75,100)?
--
La perfection est atteinte,
non pas lorsqu'il n'y a plus rien à ajouter,
mais lorsqu'il n'y a plus rien à retirer.
-- Antoine de Saint-Exupéry
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
upload to calm: should curr-2 be vaulted while still in setup.ini?
Hi folks, After upload, noticed in calm deployment log that release current - 2 is being vaulted, but it's still showing in setup.ini. If current - 2 is selected in setup, won't this cause setup to fail, as as it will no longer be available under release/, nor propagated on mirrors? INFO: adding 1 package(s) for arch x86_64 > INFO: move from Brian Inglis's upload area to release area:> INFO: deploying x86_64/release/cpuid/cpuid-20221003-1-src.hint> INFO: deploying x86_64/release/cpuid/cpuid-20221003-1-src.tar.xz> INFO: deploying x86_64/release/cpuid/cpuid-20221003-1.hint> INFO: deploying x86_64/release/cpuid/cpuid-20221003-1.tar.xz> INFO: vaulting 1 old package(s) for arch x86_64> INFO: move from release area to vault:> INFO: vaulting x86_64/release/cpuid/cpuid-20220812-1-src.hint> INFO: vaulting x86_64/release/cpuid/cpuid-20220812-1-src.tar.xz> INFO: vaulting x86_64/release/cpuid/cpuid-20220812-1.hint> INFO: vaulting x86_64/release/cpuid/cpuid-20220812-1.tar.xz> SUMMARY: 12 INFO(s) [prev] version: 20220812-2 install: x86/release/cpuid/cpuid-20220812-2.tar.xz 132096 3eb7f8d86db037c242d7dccbd79b28a4a57771eb08f4e187fd5be124e6b3aff4aa615636e83ed39e6529982869460282b195454914ff6ff573ce2f427b58dcad source: x86/release/cpuid/cpuid-20220812-2-src.tar.xz 139888 e8e958c2f799fdbed04076878f1a2293066f6004dc3754892354f5484bed172e7ae49d0f0043c0a1a4b5ef52a85b803305de136ec5edd71852a3e5dc02d9ac26 depends2: cygwin, perl_base build-depends: binutils, coreutils, cygport, gcc-core, gzip, make, perl, tar -- La perfection est atteinte, non pas lorsqu'il n'y a plus rien à ajouter, mais lorsqu'il n'y a plus rien à retirer. -- Antoine de Saint-Exupéry
Re: Frequent Warning messages using gv
Thank you. Installing these two packages has done the trick, at least for the several files that previously generated warning messages. Sent via Outlook on my Asus ZenFone 8 From: Jon Turney Sent: Saturday, October 8, 2022 2:01:50 PM To: Fergus Daly ; The Cygwin Mailing List Subject: Re: Frequent Warning messages using gv On 05/10/2022 06:45, Fergus Daly wrote: > Whenever I use gv on a PostScript file as in > $ gv filename.ps > then a (usually) successful display is (almost invariably) accompanied by > Warning messages about font conversions. > It is not obvious what limitations or errors are affecting the displayed > output, if any, and I have got into the habit > of issuing the command with the qualifier > $ gv filename.ps 2> /dev/null > However: the Warning messages whilst occasionally very esoteric nearly always > include the form > Warning: Missing charsets in String to FontSet conversion > Warning: Cannot convert string > "-*-Helvetica-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct > Warning: Cannot convert string > "-*-Helvetica-Medium-R-Normal--*-100-*-*-P-*-ISO8859-1" to type FontStruct > Warning: Cannot convert string > "-*-Helvetica-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct > Warning: Cannot convert string > "-*-Helvetica-Medium-R-Normal--*-140-*-*-P-*-ISO8859-1" to type FontStruct > Is there some additional fonts package or group of packages that I could > usefully incorporate into my Cygwin setup that > would reduce warnings when using gv? (And maybe improve the rendering of > outputs.) > My directory /usr/share/fonts/microsoft/ contains 120+ ttf links, though none > looking anything like helv*. Installing 'xorg-x11-fonts-dpi75' and/or 'xorg-x11-fonts-dpi100' will probably resolve these warnings. It's unclear to me if gv needs a dependency on more font packages or not, since the PS could be using any fonts? -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: Perl distributions
The following Perl distributions have been updated to their latest release version available on CPAN: x86/x86_64 -- perl-Net-DNS-SEC-1.20-1 noarch -- perl-Alien-Build-2.71-1 perl-HTTP-Message-6.39-1 perl-Net-DNS-1.35-1 perl-URI-5.13-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Updated: Perl distributions
The following Perl distributions have been updated to their latest release version available on CPAN: x86/x86_64 -- perl-Net-DNS-SEC-1.20-1 noarch -- perl-Alien-Build-2.71-1 perl-HTTP-Message-6.39-1 perl-Net-DNS-1.35-1 perl-URI-5.13-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Re: Cygwin 3.3.6: PHP's SplFileObject::fwrite seems broken
On 10/3/2022 12:59 PM, Hans Henrik Bergan wrote: @Ken Brown I don't think you wrote what you meant. You're not saying that explicitly specifying the default value changes the behavior, are you? Maybe you meant to say that the default mode is "r"? sorry about that, i meant "ab" makes the code work. @Andrey Repin php -d 'display_errors=stderr' ? adding -d 'display_errors=stderr' does not make any difference. still int(0) NULL Someone needs to debug this. Unfortunately, php currently has no Cygwin maintainer. Are you able to run php under gdb to see what's going on? Even better, are you interested in taking over as the php maintainer? If not, I might try debugging this at some point. But I have quite a bit of Real Life going on at the moment, so I don't know when I'll get to it. Ken -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Frequent Warning messages using gv
On 10/8/2022 9:01 AM, Jon Turney wrote: On 05/10/2022 06:45, Fergus Daly wrote: Whenever I use gv on a PostScript file as in $ gv filename.ps then a (usually) successful display is (almost invariably) accompanied by Warning messages about font conversions. It is not obvious what limitations or errors are affecting the displayed output, if any, and I have got into the habit of issuing the command with the qualifier $ gv filename.ps 2> /dev/null However: the Warning messages whilst occasionally very esoteric nearly always include the form Warning: Missing charsets in String to FontSet conversion Warning: Cannot convert string "-*-Helvetica-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-100-*-*-P-*-ISO8859-1" to type FontStruct Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-140-*-*-P-*-ISO8859-1" to type FontStruct Is there some additional fonts package or group of packages that I could usefully incorporate into my Cygwin setup that would reduce warnings when using gv? (And maybe improve the rendering of outputs.) My directory /usr/share/fonts/microsoft/ contains 120+ ttf links, though none looking anything like helv*. Installing 'xorg-x11-fonts-dpi75' and/or 'xorg-x11-fonts-dpi100' will probably resolve these warnings. It's unclear to me if gv needs a dependency on more font packages or not, since the PS could be using any fonts? I could go either way on this. On the one hand, gv is a postscript viewer and has no control over what fonts it might be asked to display. On the other hand, gv is intended to be run under X11, so maybe it should require the most basic X11 fonts. Ken -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [Bug] setup regression #2
Jon Turney writes: > On 03/10/2022 20:23, Achim Gratz wrote: >> Jon Turney writes: >>> This problem is with files created by setup, or by post-install scripts? >> I think both, although the problematic symlinks were created through >> alternatives. > > That's pretty baffling. Even more baffling is that I have another installation that are completely fine even with their Group now switched to Administrators. The one syxstem where I've had the problems is a server version and might have some GPO that affect thing that an admin user does. > I don't see how any of those commits would change the ownership of > files created by setup itself. The ownership is still with the user that runs the install script, however the group has changed. > The only relevant change seems to be in "Defer setting group until > after All Users/Just For Me is chosen", I've made > nt_sec.resetPrimaryGroup() explicit, but that only happens for > non-admin installs... I think that setup was essentially treating the install as "for this user only" since it was created and maintained by a script that can't affect that option and the fact it was also in group Adminsitroators didn't actually register until now. The DACL on the server install changed from conferring access to "Everyone" to just the install user and SYSTEM IIRC. It doesn't do that on the (non-domain) build machine at home that runs Win10 Pro. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: Scallywag TeX dblatex font requirements dependencies missing
On 10/8/2022 9:04 AM, Jon Turney wrote:
On 30/09/2022 19:25, Brian Inglis wrote:
On 2022-09-30 07:01, Jon Turney wrote:
On 29/09/2022 07:22, Brian Inglis wrote:
Hi folks, [Please Reply All as Cygwin mail blocked by ISP]
Scallywag job failing complaining about TeX fonts.
Any ideas about what extra TeX font dependencies dblatex requires under
gtk-doc building docs for gsasl 2.2 under playground:
https://cygwin.com/cgi-bin2/jobs.cgi?id=4618
https://github.com/cygwin/scallywag/actions/runs/3148865611/jobs/5119913953
Googling the first error message leads me to suggest
texlive-collection-fontsrecommended
Thanks Jon,
I planned to add that and ...extra, but shouldn't presumably required fonts be
TeX/LaTex/dblatex package dependencies, when not mentioned anywhere in
downstream packages, including in build scripts on other systems?
I don't think so. TeX/LaTeX/dblatex can't know what fonts are going to be
required to build documentation for other packages.
How are maintainers and users expected to make the connection, if nobody
mentions you need special "unrelated" font packages, in any of the downstream
packages?
For example, for DbLaTeX, only the Windows install page mentions MikTeX fonts,
and there appears to be no other link between the abstract font specs, the TeX
fonts used, and packages required, although there appear to be mentions of
DejaVu "system" fonts, so do non-TeX font packages also need installed e.g.
dejavu-fonts or urw-base35-fonts{,-legacy}?
Those who are not TeXies need a few more hints.
gsasl should tell you what fonts are required to build its documentation. Since
it apparently doesn't (I haven't checked), you have to go by the error messages.
The first error message I see in the log is
! I can't find file `pzdr'
followed shortly by
...failed to make pzdr.tfm.
Searching Cygwin packages for 'pzdr', you find that pzdr.tfm is in
texlive-collection-fontsrecommended. So you add the latter to BUILD_REQUIRES
and try again. If there are still error messages about missing fonts, repeat
the process.
I don't know any other way to do it.
Ken
Re: [PATCH 2/2] typo: that -> than
On 07/10/2022 18:26, Chad Dougherty wrote: Signed-off-by: Chad Dougherty --- contrib.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib.html b/contrib.html index d5024694..04dc9726 100755 --- a/contrib.html +++ b/contrib.html @@ -132,7 +132,7 @@ in git format-patch format. git format-patch [--cover-letter] -This will produce files with all of your changes newer that origin, +This will produce files with all of your changes newer than origin, making it easy for someone to review and, if you don't have write access, push. Give them a final once-over. Ideally you include a good description of your change with details what it does, how it works, what I applied these, thanks.
Re: [Bug] setup regression #2
On 03/10/2022 20:23, Achim Gratz wrote: Jon Turney writes: This problem is with files created by setup, or by post-install scripts? I think both, although the problematic symlinks were created through alternatives. That's pretty baffling. I don't see how any of those commits would change the ownership of files created by setup itself. The only relevant change seems to be in "Defer setting group until after All Users/Just For Me is chosen", I've made nt_sec.resetPrimaryGroup() explicit, but that only happens for non-admin installs... (I'm not sure how these commits could have caused the former, if the latter then reverting 45d8e84e "Drop group change while running postinstall scripts" would be the thing to try...) As I said, I don't understand it either. It seems my installations were all using the primary group for the account that does the install (which does have administrative rights and is separate from my normal user account on most machines). The primary group is either "None" for the build machine that only uses local accounts and is not a member of any domain or "Domain Users" otherwise. The new code uses "Administrators", but that seems to have the side effect of denying "normal" users access to the installation and instead weaves in extra DACL for SYSTEM. As long as there's an option to force it to keep the former behaviour things should be OK, but I haven't really checked if and how this is possible. Unfortunately, there is no such option.
[ITP] minisign 0.10
Hello, I'm interested in becoming a package maintainer for minisign: https://jedisct1.github.io/minisign/ I suspect the mailing list was blocking my original announcement about this so I have put all of the relevant information in the README here: https://github.com/crd477/cygports/blob/main/minisign/README.md Thanks, and take care... -- -Chad
Re: Cygwin Git repos refusing push
On Sat, 8 Oct 2022 at 14:12, Jon Turney wrote: > > On 04/10/2022 15:02, Adam Dinwoodie wrote: > [...] > >> > >> I've adjusted the gitolite configuration so this should work again. > > > > Would it be possible to add some output to the hooks to provide a useful > > explanation for what's going on? I think anything a hook prints to > > stdout or stderr will be seen by the user in the `git push` output, and > > something a bit more informative than "DENIED" would be nice! > > This is not totally straightforward, as this hook is part of, and > managed by, gitolite. > > > It's not a big issue either way, but having a more informative output in > > this case might have saved me a bit of time trying to ensure the problem > > was genuinely on the server and not just that I was doing something > > daft. > > Do you have a suggestion as to what else the hook should say? Something to the effect of "This server does not permit pushing to any branch other than 'master' or 'playground'" would have made it clearer what was going on, at least for me. But as I say, if it's difficult to do, it's not a big deal!
Re: Feature request: File descriptor support by sockets.
On Thu, 6 Oct 2022 at 18:37, Darren Whobrey wrote: > > Hi, I'm using the latest version of Cygwin (3.3.6) and the Cygwin OpenSSH > (OpenSSH_9.0p1, OpenSSL 1.1.1q 5 Jul 2022) version of ssh to talk to hosts > using ControlMaster connection sharing. This uses sockets behind the scenes. > When ControlMaster is set to no, the connection is successful. > > Ssh connections are failing at the point where IO starts to be forwarded to > the host. > > Here's a snippet of log output from "ssh -vvv some-host": > > > > When successful connections are made from an OL7 client (with older version > of OpenSSH, but mux commands are similar), comparative logs are: > > > > According to this web posting, it suggests the bug lies with "file > descriptors over unix sockets do not work in Cygwin": > https://exchangetuts.com/is-ssh-controlmaster-with-cygwin-on-windows-actually-possible-1639696447917488 > > Is this something that can be fixed? I'm very confident it *can* be fixed! But this gap has existed since at least 2009 (see https://cygwin.com/pipermail/cygwin/2012-February/15.html and https://sourceware.org/legacy-ml/cygwin/2009-10/msg00397.html) so I suspect that, unless you're proposing to do the work or pay someone to do it on your behalf, it's unlikely to happen any time soon. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin Git repos refusing push
On 04/10/2022 15:02, Adam Dinwoodie wrote: [...] I've adjusted the gitolite configuration so this should work again. Would it be possible to add some output to the hooks to provide a useful explanation for what's going on? I think anything a hook prints to stdout or stderr will be seen by the user in the `git push` output, and something a bit more informative than "DENIED" would be nice! This is not totally straightforward, as this hook is part of, and managed by, gitolite. It's not a big issue either way, but having a more informative output in this case might have saved me a bit of time trying to ensure the problem was genuinely on the server and not just that I was doing something daft. Do you have a suggestion as to what else the hook should say?
Re: Frequent Warning messages using gv
On 10/8/2022 8:57 AM, Adam Dinwoodie wrote: On Wed, 5 Oct 2022 at 06:46, Fergus Daly wrote: Whenever I use gv on a PostScript file as in $ gv filename.ps then a (usually) successful display is (almost invariably) accompanied by Warning messages about font conversions. It is not obvious what limitations or errors are affecting the displayed output, if any, and I have got into the habit of issuing the command with the qualifier $ gv filename.ps 2> /dev/null However: the Warning messages whilst occasionally very esoteric nearly always include the form Warning: Missing charsets in String to FontSet conversion Warning: Cannot convert string "-*-Helvetica-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-100-*-*-P-*-ISO8859-1" to type FontStruct Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-140-*-*-P-*-ISO8859-1" to type FontStruct Is there some additional fonts package or group of packages that I could usefully incorporate into my Cygwin setup that would reduce warnings when using gv? (And maybe improve the rendering of outputs.) My directory /usr/share/fonts/microsoft/ contains 120+ ttf links, though none looking anything like helv*. I doubt it. I'm not familiar with gv, but this looks like you're trying to process documents that incorporate Helvetica, in a way that requires having the font files, without having the font files. Helvetica is a trademark, and the font files are under copyright, so no Cygwin package is going to be able to include the fonts or even include substitutes with matching filenames. You *might* be able to add symlinks from the missing Helvetica files to more readily available metric-identical alternatives you already have access to, e.g. Arial, MS Sans Serif, or Liberation Sans. Otherwise I suspect you need to either avoid processing files that incorporate fonts you don't own, or buy copies of the relevant Helvetica typefaces. Something I might try first is researching how fontconfig can allow you to set up substitutions. Cheers - Eliot Moss -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Scallywag TeX dblatex font requirements dependencies missing
On 30/09/2022 19:25, Brian Inglis wrote:
On 2022-09-30 07:01, Jon Turney wrote:
On 29/09/2022 07:22, Brian Inglis wrote:
Hi folks, [Please Reply All as Cygwin mail blocked by ISP]
Scallywag job failing complaining about TeX fonts.
Any ideas about what extra TeX font dependencies dblatex requires
under gtk-doc building docs for gsasl 2.2 under playground:
https://cygwin.com/cgi-bin2/jobs.cgi?id=4618
https://github.com/cygwin/scallywag/actions/runs/3148865611/jobs/5119913953
Googling the first error message leads me to suggest
texlive-collection-fontsrecommended
Thanks Jon,
I planned to add that and ...extra, but shouldn't presumably required
fonts be TeX/LaTex/dblatex package dependencies, when not mentioned
anywhere in downstream packages, including in build scripts on other
systems?
How are maintainers and users expected to make the connection, if nobody
mentions you need special "unrelated" font packages, in any of the
downstream packages?
For example, for DbLaTeX, only the Windows install page mentions MikTeX
fonts, and there appears to be no other link between the abstract font
specs, the TeX fonts used, and packages required, although there appear
to be mentions of DejaVu "system" fonts, so do non-TeX font packages
also need installed e.g. dejavu-fonts or urw-base35-fonts{,-legacy}?
Those who are not TeXies need a few more hints.
I don't know.
Maybe Ken has some insight?
Re: Frequent Warning messages using gv
On 05/10/2022 06:45, Fergus Daly wrote: Whenever I use gv on a PostScript file as in $ gv filename.ps then a (usually) successful display is (almost invariably) accompanied by Warning messages about font conversions. It is not obvious what limitations or errors are affecting the displayed output, if any, and I have got into the habit of issuing the command with the qualifier $ gv filename.ps 2> /dev/null However: the Warning messages whilst occasionally very esoteric nearly always include the form Warning: Missing charsets in String to FontSet conversion Warning: Cannot convert string "-*-Helvetica-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-100-*-*-P-*-ISO8859-1" to type FontStruct Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct Warning: Cannot convert string "-*-Helvetica-Medium-R-Normal--*-140-*-*-P-*-ISO8859-1" to type FontStruct Is there some additional fonts package or group of packages that I could usefully incorporate into my Cygwin setup that would reduce warnings when using gv? (And maybe improve the rendering of outputs.) My directory /usr/share/fonts/microsoft/ contains 120+ ttf links, though none looking anything like helv*. Installing 'xorg-x11-fonts-dpi75' and/or 'xorg-x11-fonts-dpi100' will probably resolve these warnings. It's unclear to me if gv needs a dependency on more font packages or not, since the PS could be using any fonts? -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Frequent Warning messages using gv
On Wed, 5 Oct 2022 at 06:46, Fergus Daly wrote: > Whenever I use gv on a PostScript file as in > $ gv filename.ps > then a (usually) successful display is (almost invariably) accompanied by > Warning messages about font conversions. > It is not obvious what limitations or errors are affecting the displayed > output, if any, and I have got into the habit > of issuing the command with the qualifier > $ gv filename.ps 2> /dev/null > However: the Warning messages whilst occasionally very esoteric nearly always > include the form > Warning: Missing charsets in String to FontSet conversion > Warning: Cannot convert string > "-*-Helvetica-Bold-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct > Warning: Cannot convert string > "-*-Helvetica-Medium-R-Normal--*-100-*-*-P-*-ISO8859-1" to type FontStruct > Warning: Cannot convert string > "-*-Helvetica-Medium-R-Normal--*-120-*-*-P-*-ISO8859-1" to type FontStruct > Warning: Cannot convert string > "-*-Helvetica-Medium-R-Normal--*-140-*-*-P-*-ISO8859-1" to type FontStruct > Is there some additional fonts package or group of packages that I could > usefully incorporate into my Cygwin setup that > would reduce warnings when using gv? (And maybe improve the rendering of > outputs.) > My directory /usr/share/fonts/microsoft/ contains 120+ ttf links, though none > looking anything like helv*. I doubt it. I'm not familiar with gv, but this looks like you're trying to process documents that incorporate Helvetica, in a way that requires having the font files, without having the font files. Helvetica is a trademark, and the font files are under copyright, so no Cygwin package is going to be able to include the fonts or even include substitutes with matching filenames. You *might* be able to add symlinks from the missing Helvetica files to more readily available metric-identical alternatives you already have access to, e.g. Arial, MS Sans Serif, or Liberation Sans. Otherwise I suspect you need to either avoid processing files that incorporate fonts you don't own, or buy copies of the relevant Helvetica typefaces. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: libffi: upgrade to libffi-3.4.3 proposed (cygport file attached)
On 04/10/2022 19:11, Hannes Müller wrote: Dear Maintainer(s), libffi is ORPHANED and outdated. Attached a cygport for newest libffi-3.4.3, which needs no extra patches. PS: libffi-3.4.3 is also used on MSYS2 without extra patches. Thanks! Thanks. I'm minded to do a NMU of libffi using your revised cygport, but I notice that many tests fail on x86 (see [1]). Is this expected, or does it indicate some problem there? [1] https://github.com/cygwin/scallywag/actions/runs/3205410540/jobs/5237942271#step:6:2343
[ANNOUNCEMENT] Test: libreadline{7,-devel} 8.2-2 (TEST)
The following test packages have been uploaded to the Cygwin distribution: * libreadline7 8.2-2 * libreadline-devel 8.2-2 This patch release *2* avoids a crash that could happen with a bad locale. The readline library will read a line from the terminal and return it, allowing the user to edit the line with the standard emacs editing keys. It allows the programmer to give the user an easier-to-use and more intuitive interface. Please test this Base category library as extensively as possible (especially if you are a Cygwin package maintainer) as this package is used in all installations. I have it locally installed so it is getting used by commands, and has and is getting frequent exercise with no apparent issues so far. If no issues are reported within a few weeks the package will be upgraded to current stable. For more information see the project home pages: http://tiswww.cwru.edu/php/chet/readline/rltop.html https://sv.gnu.org/projects/readline/ For changes since the previous Cygwin release please see below or read /usr/share/doc/readline/NEWS after installation: https://git.sv.gnu.org/gitweb/?p=readline.git;f=CHANGES;hb=readline-8.2 1. Changes to Readline a. Fixed a problem with cleaning up active marks when using callback mode. b. Fixed a problem with arithmetic comparison operators checking the version. c. Fixed a problem that could cause readline not to build on systems without POSIX signal functions. d. Fixed a bug that could cause readline to crash if the application removed the callback line handler before readline read all typeahead. e. Added additional checks for read errors in the middle of readline commands. f. Fixed a redisplay problem that occurred when switching from the digit- argument prompt `(arg: N)' back to the regular prompt and the regular prompt contained invisible characters. g. Fixed a problem with restoring the prompt when aborting an incremental search. h. Fix a problem with characters > 128 not being displayed correctly in certain single-byte encodings. i. Fixed a problem with unix-filename-rubout that caused it to delete too much when applied to a pathname consisting only of one or more slashes. j. Fixed a display problem that caused the prompt to be wrapped incorrectly if the screen changed dimensions during a call to readline() and the prompt became longer than the screen width. k. Fixed a problem that caused the \r output by turning off bracketed paste to overwrite the line if terminal echo was disabled. l. Fixed a bug that could cause colored-completion-prefix to not display if completion-prefix-display-length was set. m. Fixed a problem with line wrapping prompts when a group of invisible characters runs to the right edge of the screen and the prompt extends longer then the screen width. n. Fixed a couple problems that could cause rl_end to be set incorrectly by transpose-words. o. Prevent some display problems when running a command as the result of a trap or one bound using `bind -x' and the command generates output. p. Fixed an issue with multi-line prompt strings that have one or more invisible characters at the end of a physical line. q. Fixed an issue that caused a history line's undo list to be cleared when it should not have been. r. When replacing a history entry, make sure the existing entry has a non-NULL timestamp before copying it; it may have been added by the application, not the history library. 2. New Features in Readline a. There is now an HS_HISTORY_VERSION containing the version number of the history library for applications to use. b. History expansion better understands multiple history expansions that may contain strings that would ordinarily inhibit history expansion (e.g., `abc!$!$'). c. There is a new framework for readline timeouts, including new public functions to set timeouts and query how much time is remaining before a timeout hits, and a hook function that can trigger when readline times out. There is a new state value to indicate a timeout. d. Automatically bind termcap key sequences for page-up and page-down to history-search-backward and history-search-forward, respectively. e. There is a new `fetch-history' bindable command that retrieves the history entry corresponding to its numeric argument. Negative arguments count back from the end of the history. f. `vi-undo' is now a bindable command. g. There is a new option: `enable-active-region'. This separates control of the active region and bracketed-paste. It has the same default value as bracketed-paste, and enabling bracketed paste enables the active region. Users can now turn off the active region while leaving bracketed paste enabled. h. rl_completer_word_break_characters is now `const char *' like rl_basic_word_break_characters. i. Readline looks in $LS_COLORS for a custom filename extension (*.readline-colored-completion-prefix)
Test: libreadline{7,-devel} 8.2-2 (TEST)
The following test packages have been uploaded to the Cygwin distribution: * libreadline7 8.2-2 * libreadline-devel 8.2-2 This patch release *2* avoids a crash that could happen with a bad locale. The readline library will read a line from the terminal and return it, allowing the user to edit the line with the standard emacs editing keys. It allows the programmer to give the user an easier-to-use and more intuitive interface. Please test this Base category library as extensively as possible (especially if you are a Cygwin package maintainer) as this package is used in all installations. I have it locally installed so it is getting used by commands, and has and is getting frequent exercise with no apparent issues so far. If no issues are reported within a few weeks the package will be upgraded to current stable. For more information see the project home pages: http://tiswww.cwru.edu/php/chet/readline/rltop.html https://sv.gnu.org/projects/readline/ For changes since the previous Cygwin release please see below or read /usr/share/doc/readline/NEWS after installation: https://git.sv.gnu.org/gitweb/?p=readline.git;f=CHANGES;hb=readline-8.2 1. Changes to Readline a. Fixed a problem with cleaning up active marks when using callback mode. b. Fixed a problem with arithmetic comparison operators checking the version. c. Fixed a problem that could cause readline not to build on systems without POSIX signal functions. d. Fixed a bug that could cause readline to crash if the application removed the callback line handler before readline read all typeahead. e. Added additional checks for read errors in the middle of readline commands. f. Fixed a redisplay problem that occurred when switching from the digit- argument prompt `(arg: N)' back to the regular prompt and the regular prompt contained invisible characters. g. Fixed a problem with restoring the prompt when aborting an incremental search. h. Fix a problem with characters > 128 not being displayed correctly in certain single-byte encodings. i. Fixed a problem with unix-filename-rubout that caused it to delete too much when applied to a pathname consisting only of one or more slashes. j. Fixed a display problem that caused the prompt to be wrapped incorrectly if the screen changed dimensions during a call to readline() and the prompt became longer than the screen width. k. Fixed a problem that caused the \r output by turning off bracketed paste to overwrite the line if terminal echo was disabled. l. Fixed a bug that could cause colored-completion-prefix to not display if completion-prefix-display-length was set. m. Fixed a problem with line wrapping prompts when a group of invisible characters runs to the right edge of the screen and the prompt extends longer then the screen width. n. Fixed a couple problems that could cause rl_end to be set incorrectly by transpose-words. o. Prevent some display problems when running a command as the result of a trap or one bound using `bind -x' and the command generates output. p. Fixed an issue with multi-line prompt strings that have one or more invisible characters at the end of a physical line. q. Fixed an issue that caused a history line's undo list to be cleared when it should not have been. r. When replacing a history entry, make sure the existing entry has a non-NULL timestamp before copying it; it may have been added by the application, not the history library. 2. New Features in Readline a. There is now an HS_HISTORY_VERSION containing the version number of the history library for applications to use. b. History expansion better understands multiple history expansions that may contain strings that would ordinarily inhibit history expansion (e.g., `abc!$!$'). c. There is a new framework for readline timeouts, including new public functions to set timeouts and query how much time is remaining before a timeout hits, and a hook function that can trigger when readline times out. There is a new state value to indicate a timeout. d. Automatically bind termcap key sequences for page-up and page-down to history-search-backward and history-search-forward, respectively. e. There is a new `fetch-history' bindable command that retrieves the history entry corresponding to its numeric argument. Negative arguments count back from the end of the history. f. `vi-undo' is now a bindable command. g. There is a new option: `enable-active-region'. This separates control of the active region and bracketed-paste. It has the same default value as bracketed-paste, and enabling bracketed paste enables the active region. Users can now turn off the active region while leaving bracketed paste enabled. h. rl_completer_word_break_characters is now `const char *' like rl_basic_word_break_characters. i. Readline looks in $LS_COLORS for a custom filename extension (*.readline-colored-completion-prefix)
Re: guile 3.0.8: readline does not work - patch with also other fixes
Hi folks, On my system with over 2K Cygwin packages installed, of which over 900 are named lib..., there are over 750 simple cygP-[0-9]+.dll including cygPV-[0-9]+.dll, over 250 compound version cygPV-M-m.dll, and about 80 with no -, including about 64 semantic versions: cygicudata56...70.dll cygicui18n56...70.dll cygicuio56...70.dll cygicuuc56...70.dll cygicule56.dll cygicule57.dll cygiculx56.dll cygiculx57.dll cygicutest70.dll cygicutu70.dll cygperl5_32.dll cygruby260.dll about 16 likely current - age ABI versions: cygcatgets1.dll cygfreebl3.dll cygfreeblpriv3.dll cyghistory7.dll cygnspr4.dll cygnss3.dll cygnssdbm3.dll cygnssutil3.dll cygplc4.dll cygplds4.dll cygreadline7.dll cygsmime3.dll cygsoftokn3.dll cygssl3.dll cygusb0.dll about a half dozen with no versions: cyggvfscommon.dll cyggvfsdaemon.dll cygnativeGLthunk.dll cygregina.dll cygtxc_dxtn.dll cygz.dll and the one to rule them all: cygwin1.dll The intensely curious can download over 170GB compressed tars and scan the over 12000 binary packages available for DLLs. ;^> -- La perfection est atteinte, non pas lorsqu'il n'y a plus rien à ajouter, mais lorsqu'il n'y a plus rien à retirer. -- Antoine de Saint-Exupéry -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
