[ANNOUNCEMENT] Updated: mhash v0.9.9.9-3
CHANGES SINCE LAST RELEASE == This is a minor fix and rebuild after 6 years. It was built against a recent Cygwin library collection, it does not contain any source or build changes. Changes and source are tracked at: https://github.com/pdinc-oss/mhash.git RELEASE === The following packages have been uploaded to the Cygwin distribution: * libmhash2-0.9.9.9-3 * libmhash-devel-0.9.9.9-3 DESCRIPTION === Mhash is a free library which provides a uniform interface to a large number of hash algorithms. These algorithms can be used to compute checksums, message digests, and other signatures. Upstream website: http://mhash.sourceforge.net/ SUPPORT === Please use the upstream mailing list and issue tracker for support [https://sourceforge.net/projects/mhash/support]. I am on the Mhash developer mailing list. If the issue is Cygwin related please contact cygwin@cygwin.com . -- *** 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
Re: 3.3.1: Missing VersionInfo resource for all executables/DLLs
On 11.11.2021 19:47, Hiya Z via Cygwin wrote: Hello, Upgraded to 3.3.x and noticed that the VersionInfo resource fields for all binaries under bin are blank (Properties->Details from Explorer). Is this by intent or a miss? It is breaking my application installer that relied on version check for cygwin1.dll. Regards. Binaries should not have VersionInfo, only cygwin1.dll had it. Not checked on 3.3.x -- 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
3.3.1: Missing VersionInfo resource for all executables/DLLs
Hello, Upgraded to 3.3.x and noticed that the VersionInfo resource fields for all binaries under bin are blank (Properties->Details from Explorer). Is this by intent or a miss? It is breaking my application installer that relied on version check for cygwin1.dll. Regards. -- 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
"MZxxxxx": not found (solved)
Greetings, All! $ /usr/bin/sh -xi + MZ@��� �!�L�!This program cannot be run in DOS mode. /usr/bin/sh: 1: MZ@���: not found + � /usr/bin/sh: 2: �: not found /usr/bin/sh: 2: Syntax error: word unexpected (expecting ")") /bin/sh is a (native)symlink to /bin/dash. Running /bin/dash directly produced the same issue. (And /usr/bin is a mounted /bin, yes.) Turned out, I've had $ENV set for years now in my wrapper script, but it only became a problem just now. I've now renamed the variable to resolve the issue. -- With best regards, Andrey Repin Thursday, November 11, 2021 19:33:54 Sorry for my terrible english... -- 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
Fixing permissions issue, appears as "Unknown package" error at end of setup run
I've read through the Cygwin FAQ, googled around, and I wasn't able to find the appropriate answer, which is why I'm sending it to this mailing list. Apologies if this is not the correct place. At the end of setup-x86_64.exe run, I get a popup about an Unknown package error. As instructed, I looked at /var/log/setup.log.full and saw: 2021/11/09 12:39:04 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/inetutils-server.sh" *** Warning: The permissions on the directory /var are not correct. *** Warning: They must match the regexp d..x..x..[xt] *** ERROR: Problem with /var directory. Exiting. 2021/11/09 12:39:09 abnormal exit: exit code=1 Is there a way to make cygwin re-set all the cygwin system directories and files permissions to their default values? Thanks in advance. /ALG -- 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: Another pipe-related problem?
On 11/10/2021 1:42 PM, Henry S. Thompson wrote: Ken Brown writes: The good news is that the bug doesn't seem to occur in XEmacs 21.4 (on 32-bit Cygwin). So one way to approach this would be to bisect the XEmacs git repo to find the commit that introduced the bug. You'd probably have to do the work on 32-bit Cygwin since, if I remember correctly, XEmacs 21.4 didn't build on 64-bit Cygwin. Right, although I _suspect_ it will be in 64-bit-only code. Easy enough to find out, once I resurrect a 32-bit install on a spare machine that I can run 3.3 on (I use XEmacs all day every day from my day job, so I need to stay with 3.2 until we fix this). I had actually tested the 32-bit case before suggesting the bisection. The bug does occur there too. And, as Andrey said, you don't need to use a spare machine. You can have as many parallel Cygwin installs as you want on a single machine, some 64-bit and some 32-bit. 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
[ANNOUNCEMENT] Updated: lua-logging-1.6.0-1
The following new packages have been uploaded in the Cygwin distribution: * lua-logging-1.6.0-1 * lua-logging-1.6.0-1-src This is an update to the latest upstream release. Compiled for Lua 5.3 as before (not for Lua 5.4) -- SUMMARY: Lua logging library DESCRIPTION: LuaLogging provides a simple API to use logging features in Lua. Its design was based on log4j. LuaLogging currently supports, through the use of appenders, console, file, email, socket and sql outputs. HOMEPAGE: https://lunarmodules.github.io/lualogging/ SOURCE: https://github.com/lunarmodules/lualogging/tree/v1.6.0 LICENSE: MIT License https://github.com/lunarmodules/lualogging/blob/v1.6.0/COPYRIGHT Cygwin Package Summary: https://www.cygwin.com/packages/summary/lua-logging-src.html Cygport Source: https://cygwin.com/git/?p=git/cygwin-packages/lua-logging.git -- Lemures Lemniscati -- 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: lua-crypto-0.3.2p4-1
The following new packages have been uploaded in the Cygwin distribution: * lua-crypto-0.3.2p4-1 * lua-crypto-devel-0.3.2p4-1 * lua-crypto-0.3.2p4-1-src This is a rebuild with libssl1.0, and is an update to the latest upstream, 4 commits after 0.3.2. -- SUMMARY: Lua OpenSSL bindings DESCRIPTION: *** This project is DEPRECATED, use luaossl. *** LuaCrypto provides a Lua frontend to the OpenSSL cryptographic library. The OpenSSL features that are currently exposed are digests (MD5, SHA-1, HMAC, and more) and crypto-grade random number generators. HOMEPAGE: https://github.com/starius/luacrypto/ SOURCE: https://github.com/starius/luacrypto/tree/0639ea2f65dbe5f11c2d874527f3019ce5293ac5 LICENSE: MIT License https://github.com/starius/luacrypto/blob/0639ea2f65dbe5f11c2d874527f3019ce5293ac5/COPYING Cygwin Package Summary: https://www.cygwin.com/packages/summary/lua-crypto-src.html Cygport Source: https://cygwin.com/git/?p=git/cygwin-packages/lua-crypto.git -- Lemures Lemniscati -- 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: Could rm remove files and folders with colon in their name?
On 10/11/2021 21:39, Corinna Vinschen via Cygwin wrote: On Nov 10 21:24, Mario Emmenlauer wrote: On 10.11.21 14:49, Corinna Vinschen via Cygwin wrote: On Nov 10 10:45, Mario Emmenlauer wrote: Could 'rm' support removing files and folders that have a colon ':' in their name? I.e. I would like that 'rm -fr' would remove a full directory tree, including such folders. Currently it will correctly remove anything inside such folders, but not the folder itself. As an example, for the following structure: C:/root/folder/C:/inside/file.txt When using 'rm -fr root', afterwards I have: C:/root/folder/C: It works fine if the folder is called, say, "a:b", it just doesn't work for a name which looks like a drive letter "x:", apparently. That is indeed interesting, I was not aware of it! Then maybe the problem is not so hard to solve? That would be awesome! To the contrary. The problem is the ambiguity that "X:/foo" might be either the absolute POSIX path $CWD/X:/foo, or the absolute DOS path "X:\foo". I have a patch which fixes your case, but not much else. The problem is that we historically allow DOS paths as input at all. That was a bad decision from the start, but you can't easily change 25 years of history... Oh my, I see! All the more thanks for so quickly patching support for this use case. Its highly appreciated! All the best, Mario -- 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: Another pipe-related problem?
Greetings, Andrey Repin via Cygwin! > Though I strongly require a virtual machine for such exercises. -require +recommend Sorry for confusion. -- With best regards, Andrey Repin Thursday, November 11, 2021 14:06:19 Sorry for my terrible english... -- 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] tcsh 6.23.00-1
The following packages have been uploaded to the Cygwin distribution: * tcsh-6.23.00-1 I am pleased to announce that tcsh-6.23 is now available; this is mainly a bug fix release (after 2 years) with a couple of new features: 1. Add "jobs -Z" to setproctitle(3) 2. Add ln=target in LS_COLORS 3. Add a :Q modifier that preserves empty arguments Please consult the Fixes file for a complete list of changes. Tcsh is an enhanced but completely compatible version of csh, the C shell. Tcsh is a command language interpreter which can be used both as an interactive login shell and as a shell script command processor. Tcsh includes a command line editor, programmable word completion, spelling correction, a history mechanism, job control and a C language like syntax. -- 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: Console output broken in version 3.3.x under native ninja
On Wed, 10 Nov 2021 15:40:37 + "Bresalier, Rob \(Nokia - US/Murray Hill\) wrote: > Hi: > > This worked fine with Cygwin 3.2.0 but is broken starting with Cygwin 3.3.0, > hence I think it is a Cygwin bug and not a ninja bug. > > When running Cygwin applications under Windows native 'ninja.exe' build tool > (not the Cygwin packaged one) then the stdout is not emitted to the console > starting with Cygwin 3.3.0. It worked fine with Cygwin 3.2.0 and stdout is > emitted to the console. If using Cygwin ninja with 3.3.0 it also works. The > problem is with Windows native ninja and Cygwin programs with Cygwin version > 3.3.0 and later. > > Using Cygwin ninja is not an option for us as a solution. We need to use the > Windows native ninja for reasons that I won't go into here. > > To reproduce the issue: > > 1) Download windows native ninja from here: > https://github.com/ninja-build/ninja/releases >a. Use ninja-win.zip that has the ninja.exe executable >b. DO NOT USE the Cygwin version of ninja > > 2) Below is a sample build.ninja file that demonstrates the problem. This > sample build.ninja simply causes bash -help to run. Create this build.ninja > text file in some directory. > > 3) cd to the directory where you have the build.ninja, and then run the > native ninja.exe, you won't see the bash --help output with Cygwin 3.3.0 and > later. > a. I suggesting using -v option with ninja.exe: "path/to/native/ninja.exe > -v" > > 4) If you try it with Cygwin 3.2.0 it works fine you will see the bash --help > output. > > 5) If you run c:/cygwin64/bin/bash --help outside of ninja it works fine. > > 6) This happens if you run the native ninja.exe from either a command window > or from the Cygwin/minty/bash > > Here is the sample build.ninja to be used to reproduce the problem: > > start build.ninja -- > rule CUSTOM_COMMAND > command = $COMMAND > description = $DESC > > build MC5U_BMDCO6_versions.txt: CUSTOM_COMMAND > COMMAND = c:/cygwin64/bin/bash --help > DESC = Running bash --help > restat = 1 > end build.ninja -- > > Thanks for having a look. Thanks for the report. I could reproduce your problem and found the cause. Windows native ninja creates pipe with size zero, which cannot be handled correctly by current cygwin pipe code (raw_write()). I will submit a patch for this issue shortly. -- Takashi Yano -- 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
