[ANNOUNCEMENT] Updated: setup.exe (Release 2.876)
A new version of Setup, release 2.876, has been uploaded to https://cygwin.com/setup-x86.exe (32 bit version) https://cygwin.com/setup-x86_64.exe (64 bit version) Changes compared to 2.875: - Refuse to run on Windows XP/2003 and earlier, as they are no longer supported by Cygwin. - Fix the code for C++11 std::string, which was the underlying issue causing an error with a root install path of more than 15 characters. Please send bug reports, as usual, to the public mailing list cygwin AT cygwin DOT com. -- Yaakov -- 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
Suggestion for chere
Hi Dave, I have a suggestion for chere. It would be really nice if the Cygwin icon/logo would be shown in front of the menu entry. Right now I only have one "Bash Prompt Here" menu item, but other bash implementations (MSYS2, Windows Git) also have a chere-like feature. They add there icon in front of the menu item. Take a look at this github issue: https://github.com/Microsoft/BashOnWindows/issues/603 It shows two variants of "bash here" in the context menu. Adding the icon is not that hard. See the .reg sample below. Just add an extra entry named "Icon" with a full path to the Cygwin.ico file. [HKEY_CLASSES_ROOT\Directory\Background\shell\cygwin64_bash] @="&Bash Prompt Here" "Icon"="C:\\Cygwin\\Cygwin.ico" If you want to make this optional, the command line flag -I (capital i) is the most logical available letter. Regards, Frank -- 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
Re: Can you modify how Cygwin prepends domain name to username?
Hi Carl, Please don't https://cygwin.com/acronyms/#TOFU Thank you. On Sep 9 09:39, Carl wrote: > Hi Linda, > > On 9 September 2016 at 05:44, Linda Walsh wrote: > > Carl wrote: > > ADUNSW+root:*:2149521262:2147484161:U-ADUNSW\root, > > S-1-5-21-1140405718-358989843-3445714273-2037614:/home/root:/bin/bash > > --- > > Where does the '+' come from? Is that in Win10 or some newer domain > > control software? > > The plus character is the default separator for mkpasswd. > > In the help for it (mkpasswd -h), you will see > >-S,--separator char For -L use character char as domain\user >separator in username instead of the default '+'. No, no. Mkpasswd uses the '+' only by default because Cygwin uses it. The full answer to the question is in the docs: https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
Re: unzip, find broken by auto handling of .exe file extension
See also: http://stackoverflow.com/questions/32467871/unzip-gives-checkdir-error-directory-exists-but-is-not-a-directory#32468314 The fact that 7z handles this and unzip does not indicates that the problem is fixable.. sja -Original Message- From: Stephen Anderson Sent: Friday, September 02, 2016 4:19 PM To: cygwin@cygwin.com ; cyg Simple Subject: Re: unzip, find broken by auto handling of .exe file extension Thanks for looking at the problem. Unfortunately not resolved... 1. As demonstrated by the provided ruby test case, it is very possible to have a directory and base filename be the same. Open bash and try it. $ mkdir mything $ touch mything.exe $ ls mything* mything.exe mything: $ 2. Even if cygwin somehow prevented it (it can't), zip archives do not preclude the presence of a base filename with exe extension and same directory name. 3. The problem is not simply exe - batch files (.bat, .cmd), powershell (.ps1) and others are automatically picked up by cmd.exe processing, and can all have common base names. 4. I tried unzip -x and it does not workaround the problem. 7z remains my workaround and the only one I have found so far. 5. Terminating the find -path with / results in 'find: warning: -path testAutoExeExpansion/test/ will not match anything because it ends with /'. 6. Terminating the target with / does not help. 7. Rmdir fails with 'directory not empty'. 8. I am NOT trying to run the executable, so the globbing should NOT automatically be expanding 'test' to match 'test.exe'. I would think that the only utilities that really should do that would be 'which', 'whereis' or shell command completion (not file completion). Attached updated test case. sja -Original Message- From: cyg Simple Sent: Friday, September 02, 2016 2:40 PM To: cygwin@cygwin.com Subject: Re: unzip, find broken by auto handling of .exe file extension On 9/1/2016 12:00 PM, Stephen Anderson wrote: I am in the process of importing zip archive contents into an SVN repo and have encountered problems when unzip-6.00 expands an archive containing an executable file in a directory that contains a subdirectory with the same base name as the executable. If the executable happens to occur after the subdirectory, unzip works, however if the executable is first, unzip fails with the error: checkdir error: testAutoExeExpansion/test exists but is not directory unable to process testAutoExeExpansion/test/. How can a directory and a file of the same name exist? It can't and because Cygwin stats the foo.exe to be foo then that is the filename comparison. Luckily I am able to use 7z extract, which does not exhibit the unzip problem and even allows me to exclude the culprit subdirectory (which luckily contains nothing I am interested in). Unzip has the -x option to exclude archive items. In the process of trying to solve this problem, I used find-4.6.0 to try and delete the subdirectory after extracting with 7z to no avail. Even preceding the path match with a type directory spec find gets confused (so did the svn commit BTW). Did you trail the name with / for the delete? The rmdir command should work. You would use the -exec option with find to execute rmdir rather than the delete function of find. The enclosed ruby unit test reproduces the minimal circumstances of the issue for both unzip and find. It is likely that this is a common problem somewhere in the bowels of file 'globbing' in cygwin only. Yes and one that allows the stat of foo.exe by foo only so that it can launch the application. It has existed since the beginning of Cygwin and I doubt it will ever be resolved without requiring the full file name for executables. -- cyg Simple -- 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 -- 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
RE: unzip, find broken by auto handling of .exe file extension
From: Stephen Anderson > > See also: > > http://stackoverflow.com/questions/32467871/unzip-gives-checkdir-error- > directory-exists-but-is-not-a-directory#32468314 > > The fact that 7z handles this and unzip does not indicates that the > problem > is fixable.. FWIW, it seems that the same issue is present with tar: $ touch foo.exe $ mkdir -v foo mkdir: created directory 'foo' $ ls -l total 0 drwxr-x---+ 1 knellis Domain Users 0 Sep 9 09:46 foo -rw-r- 1 knellis Domain Users 0 Sep 9 09:46 foo.exe $ tar cvf bar.tar foo foo/ $ rmdir -v foo rmdir: removing directory, 'foo' $ tar rvf bar.tar foo foo $ rm -v foo removed 'foo' $ ls -l total 12 -rw-r- 1 knellis Domain Users 10240 Sep 9 09:47 bar.tar $ tar tf bar.tar foo/ foo $ tar xvf bar.tar foo/ foo $ ls -l total 12 -rw-r- 1 knellis Domain Users 10240 Sep 9 09:47 bar.tar -rw-r- 1 knellis Domain Users 0 Sep 9 09:46 foo $ So, tar indicates that it extracted both directory foo/ and file foo, but the result indicates that the file won the conflict. If tar actually did extract the directory first, I'd think that it's next attempt to extract the file with the same name would fail, but that's not what happened. --Ken Nellis -- 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
Windows 7 update broke Cygwin X?
Hi, After a recent Windows update, I am unable to start Cygwin's X server anymore. I tried updating to the latest Cygwin by running setup again, /usr/bin/rebaseall and rebooting. There are no obvious errors from the X server if I run /usr/bin/startxwin from a Cygwin console, but it seems to exit after 20 seconds or so: $ date; /usr/bin/startxwin; date Fri, Sep 09, 2016 12:00:58 PM Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.18.4.0 OS: CYGWIN_NT-6.1-WOW 3QGH462 2.6.0(0.304/5/3) 2016-08-31 14:27 i686 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64) Package: version 1.18.4-1 built 2016-07-22 XWin was started with the following command line: /usr/bin/XWin :0 -multiwindow -auth /home/jhoke/.serverauth.5404 (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information LoadPreferences: /home/jhoke/.XWinrc not found LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winDetectSupportedEngines - RemoteSession: no winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - Returning, supported engines 0005 xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error Fri, Sep 09, 2016 12:01:19 PM Any ideas about what how to fix or troubleshoot this? I use it all the time and it worked before this update. -- Joshua Hoke -- 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
Re: Windows 7 update broke Cygwin X?
On 09/09/2016 18:03, Joshua Hoke wrote: Hi, After a recent Windows update, I am unable to start Cygwin's X server anymore. I tried updating to the latest Cygwin by running setup again, /usr/bin/rebaseall and rebooting. There are no obvious errors from the X server if I run /usr/bin/startxwin from a Cygwin console, but it seems to exit after 20 seconds or so: $ date; /usr/bin/startxwin; date Fri, Sep 09, 2016 12:00:58 PM Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.18.4.0 OS: CYGWIN_NT-6.1-WOW 3QGH462 2.6.0(0.304/5/3) 2016-08-31 14:27 i686 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64) Package: version 1.18.4-1 built 2016-07-22 works fine for me. Same configuration Any ideas about what how to fix or troubleshoot this? I use it all the time and it worked before this update. Problem reports: http://cygwin.com/problems.html please provide the cygcheck.out as attachement -- 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
Re: Windows 7 update broke Cygwin X?
On Fri, Sep 9, 2016 at 12:42 PM, Marco Atzeri wrote: > On 09/09/2016 18:03, Joshua Hoke wrote: >> >> Hi, >> >> After a recent Windows update, I am unable to start Cygwin's X server >> anymore. I tried updating to the latest Cygwin by running setup again, >> /usr/bin/rebaseall and rebooting. There are no obvious errors from the >> X server if I run /usr/bin/startxwin from a Cygwin console, but it >> seems to exit after 20 seconds or so: >> >> $ date; /usr/bin/startxwin; date >> Fri, Sep 09, 2016 12:00:58 PM >> >> Welcome to the XWin X Server >> Vendor: The Cygwin/X Project >> Release: 1.18.4.0 >> OS: CYGWIN_NT-6.1-WOW 3QGH462 2.6.0(0.304/5/3) 2016-08-31 14:27 i686 >> OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64) >> Package: version 1.18.4-1 built 2016-07-22 > > > works fine for me. Same configuration > >> >> Any ideas about what how to fix or troubleshoot this? I use it all the >> time and it worked before this update. >> > > Problem reports: http://cygwin.com/problems.html > > please provide the cygcheck.out as attachement Please find attached cygcheck.out (redacted some environment variables, a network share and local Windows groups) and also XWin.0.log (though it appears the same as stdout in this case). Note "this update" in my previous email could be unclear, I meant to refer to the Windows update installed this morning. Looking at the update history it appears that includes: Update for Windows 7 for x64-based Systems (KB3177723): 2016 — Egypt cancels DST Update for Windows 7 for x64-based Systems (KB3172605): July 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1 Update for Windows 7 for x64-based Systems (KB3161102): Update for Windows Journal component removal Windows Malicious Software Removal Tool x64 - August 2016 (KB890830) Update for Windows 7 for x64-based Systems (KB3179573): August 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1 Thanks in advance for any help. cygcheck.out Description: Binary data XWin.0.log Description: Binary data -- 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
[ANNOUNCEMENT] mDNSResponder 625.41.2-1
The following packages have been uploaded to the Cygwin distribution: * mDNSResponder-625.41.2-1 * libdns_sd1-625.41.2-1 * libdns_sd-devel-625.41.2-1 Bonjour, also known as zero-configuration networking, enables automatic discovery of computers, devices, and services on IP networks using industry standard IP protocols. This is an update to the latest upstream release, with the following notable packaging change: * The mDNSResolver daemon is now included in the main package. Out of necessity, the daemon itself was compiled with the MinGW-w64 toolchain as a native Windows executable. Users may continue to use the binaries from Apple as before, or choose to use this one instead. This daemon can install itself as a Windows service with the -install flag, or the init script can be used. -- Yaakov -- 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
[ANNOUNCEMENT] avahi 0.6.32-1
The following packages have been uploaded to the Cygwin distribution: * avahi-0.6.32-1 * avahi-tools-0.6.32-1 * avahi-ui-tools-0.6.32-1 * libavahi-client3-0.6.32-1 * libavahi-client-devel-0.6.32-1 * libavahi-common3-0.6.32-1 * libavahi-common-devel-0.6.32-1 * libavahi-core7-0.6.32-1 * libavahi-core-devel-0.6.32-1 * libavahi-glib1-0.6.32-1 * libavahi-glib-devel-0.6.32-1 * libavahi-gobject0-0.6.32-1 * libavahi-gobject-devel-0.6.32-1 * libavahi-qt4_1-0.6.32-1 * libavahi-qt4-devel-0.6.32-1 * libavahi-ui0-0.6.32-1 * libavahi-ui-devel-0.6.32-1 * libavahi-ui-gtk3_0-0.6.32-1 * libavahi-ui-gtk3-devel-0.6.32-1 * girepository-Avahi0.6-0.6.32-1 * python-avahi-0.6.32-1 Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. This enables you to plug your laptop or computer into a network and instantly be able to view other people who you can chat with, find printers to print to or find files being shared. This is an update to the latest upstream release. As before, this version still requires the Bonjour Service to also be running; to that end, the main package adds mDNSResponder as a dependency now that it includes one. -- Yaakov -- 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
[ANNOUNCEMENT] pidgin 2.11.0-2
The following packages have been uploaded to the Cygwin distribution: * pidgin-2.11.0-2 * pidgin-devel-2.11.0-2 * pidgin-bonjour-2.11.0-2 * pidgin-gadugadu-2.11.0-2 * pidgin-sametime-2.11.0-2 * pidgin-tcl-2.11.0-2 * libpurple0-2.11.0-2 * libpurple-devel-2.11.0-2 * finch-2.11.0-2 * finch-devel-2.11.0-2 * libgnt0-2.11.0-2 * libgnt-devel-2.11.0-2 Pidgin is a chat program which lets you log in to accounts on multiple chat networks simultaneously. This means that you can be chatting with friends on MSN, talking to a friend on Google Talk, and sitting in a Yahoo chat room all at the same time. Pidgin is cross-platform, supports numerous chat protocols, and can be extended through plugins. This release includes relevant parts of Fedora's patchset. Note that the Yahoo protocol plugin is no longer compatible with the Yahoo Messenger service. Please install pidgin-funyahoo-plusplus and use the Yahoo (2016) protocol instead. -- Yaakov -- 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
Re: Bash shell script issue
On 7 September 2016 at 21:27, Eric Blake wrote:
>>> project_root=$PWD
>>
>> Still bad.
>
> No, that one's good. Quotes are only REQUIRED when you want to ensure
> that there is no word splitting or globbing going on, and assignment
> context has neither of those. However, although the quotes are optional
> in that context, using them out of habit makes it easier to remember to
> use quotes in the contexts where it does matter.
I was going to say that. Consider the following example:
# path1='/mnt/c/Program Files (x86)'
22:12:49 ~
# path2=$path1
22:12:54 ~
# path3=$path2/tools
22:13:00 ~
# echo $path1
/mnt/c/Program Files (x86)
22:13:05 ~
# echo $path2
/mnt/c/Program Files (x86)
22:13:06 ~
# echo $path3
/mnt/c/Program Files (x86)/tools
Assignment requires no extra quoting.
However if you try
# test -d $path2 && echo $path2 is a directory
bash: test: too many arguments
Because $path2 becomes split by space into words, while `test -d`
expects only one argument.
# test -d "$path2" && echo $path2 is a directory
/mnt/c/Program Files (x86) is a directory
This is really bash basics, and you should read Bash Beginner's Guide:
http://tldp.org/LDP/Bash-Beginners-Guide/html/
And just remember that UNIX tools such as bash, sed, awk etc. expect
scripts to use UNIX-style line endings (one LF character ends the
line), as opposed to a pair of CR and LF characters used in Windows.
Whenever you encounter problems or error messages that don't seem to
make any sense, check the file line endings. You can use the `file`
command to check the file's line endings. An example bash session:
22:22:49 ~
# cat >test.sh < #!/bin/sh
>
> echo line ending test script
> EOF
22:23:29 ~
# chmod 755 test.sh
22:23:14 ~
# u2d test.sh
unix2dos: converting file test.sh to DOS format...
22:23:24 ~
# file test.sh
test.sh: POSIX shell script, ASCII text executable, with CRLF line terminators
22:23:36 ~
# ./test.sh
./test.sh: line 2: $'\r': command not found
line ending test script
22:23:37 ~
# d2u test.sh
dos2unix: converting file test.sh to Unix format...
22:23:41 ~
# file test.sh
test.sh: POSIX shell script, ASCII text executable
22:23:43 ~
# ./test.sh
line ending test script
Here I've created a test shell script, and deliberately converted it
to DOS (Windows) line endings. The `file` command explicitly tells you
it has CRLF line terminators.
Next try to run the script and it will not work, because the
supposedly empty line is considered as a single `\r` (CR) character,
which is not a valid command.
After converting the file back to UNIX line endings, the `file`
command doesn't mention anything about line endings, because they are
the standard/default/normal UNIX-style ones (`\n` = LF). The script
runs.
Personally I use Notepad2-mod to edit shell scripts, the `File > Line
Endings` shows you the current line endings, allows to convert between
different line ending styles, and allows to set UNIX style as default.
Link if you're interested: http://xhmikosr.io/notepad2-mod/
> No, that one's okay. In fact, if you are going for minimalism, you
> could use:
>
> x=$project_root/tools
>
> as the ${} form is only REQUIRED when you are using operators inside {}
> or when the next character after } is ambiguous with a continuation of
> the name of the variable in after the $.
Minimalism is good, but when writing anything more or less
complicated, consistent style and coding conventions become more
important. Quoting a variable in one context, but not the other, using
${var1}_${var2} here, but plain $var1$var2 etc. - it will work, but it
might not be best idea to code/script like this. Same as sometimes
it's better to put an extra set of otherwise unnecessary parenthesis
in a math expression, just to group terms and make the expression more
readable and operator precedence more obvious.
Bash has a lot of different syntax, and beginners would bump into less
problems if they overquote rather than underquote...
This is personal opinion based on my software development experience,
mostly working with high-level languages, involving complicated
architectural frameworks: sometimes you write more than strictly
necessary, to prevent problems in the future, make code more readable,
maintainable etc.
Regards,
--Gene
--
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
where to download cygwin 2.5.2???
I'm sorry to bother maillist with this - but i've searched EVERYWHERE, and i can NOT find a link to download cygwin x86 setup version 2.5.2. could someone please point me in a good direction??? TX Bob -- 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
Re: where to download cygwin 2.5.2???
On Fri, Sep 9, 2016 at 4:15 PM, wrote: >I'm sorry to bother maillist with this - but i've searched EVERYWHERE, and > i can NOT find a link to download cygwin x86 setup version 2.5.2. > >could someone please point me in a good direction??? the "cygwin time machine" http://www.fruitbat.org/Cygwin/index.html#cygwintimemachine -- 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
Re: [ANNOUNCEMENT] Updated: setup.exe (Release 2.876)
On Fri, Sep 9, 2016 at 2:35 AM, Yaakov Selkowitz wrote: > A new version of Setup, release 2.876, has been uploaded to [...] The change from a button to a dropdown list for the View seems like a nice usability improvement, but it sadly takes away my main method of changing the view -- I used to always press Alt-V to cycle the View button. It was actually a really nice way to do updates without using the mouse at all: keep pressing enter until the package-search page comes up, press Alt-V twice, review the list of updatable packages, and press enter again to begin installing. Perhaps someone could bind Alt-V to dropping down the view list? (Similar to how the S in Search is underlined to indicate that Alt-S takes you to the search box.) ..wayne.. -- 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
