Re: More cygwin installations
Greetings, Silver Zachara! > can i install cygwin multiple times to different folders? E.g. > c:\cygwin64, c:\cygwin64_x_test1, c:\cygwin64_x_test2 > I want to know, if there will not be any collisions or something similar. > Or there have to be only one cygwin installation? You MAY use multiple parallel installations. But it is least advisable for people unfamiliar with environment, clashes may occur and you would have a hard(-er) time figuring them out. If you indeed need test installations, a virtual machine is the better route, IMO. -- With best regards, Andrey Repin Sunday, September 25, 2016 11:15:17 Sorry for my terrible english... -- 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: More cygwin installations
I went this path yesterday, it's clearer solution from my view, I think that cygwin have to be adjusted for parallel installations and I don't know if he does. As you wrote, it will work in more cases, but there can be some edge cases, when there can be some problem, may be some services, wm is certainty :-) On 25.09.2016 10:17, Andrey Repin wrote: > Greetings, Silver Zachara! > >> can i install cygwin multiple times to different folders? E.g. >> c:\cygwin64, c:\cygwin64_x_test1, c:\cygwin64_x_test2 > >> I want to know, if there will not be any collisions or something similar. >> Or there have to be only one cygwin installation? > > You MAY use multiple parallel installations. But it is least advisable for > people unfamiliar with environment, clashes may occur and you would have a > hard(-er) time figuring them out. > If you indeed need test installations, a virtual machine is the better route, > IMO. > > -- 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
Bug in arguments in console
There is a bug with arguments in the console since 2.6.0. C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo åäö åäö C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo "åäö" "åäö" (the quote marks are left in) C:\Users\Bengt\Desktop\src\mg2a\temp>ls -l total 1 -rw-r--r-- 1 Bengt None 0 Sep 7 01:07 blah.txt -rw-r--r-- 1 Bengt None 23 Sep 7 04:53 versions -rw-r--r-- 1 Bengt None 0 Sep 7 11:05 åäö.txt C:\Users\Bengt\Desktop\src\mg2a\temp>ls *.txt ls: cannot access '*.txt': No such file or directory -- 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: Bug in arguments in console
On 25/09/16 12:00, Bengt Larsson wrote: C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo åäö åäö C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo "åäö" "åäö" (the quote marks are left in) C:\Users\Bengt\Desktop\src\mg2a\temp>ls -l total 1 -rw-r--r-- 1 Bengt None 0 Sep 7 01:07 blah.txt -rw-r--r-- 1 Bengt None 23 Sep 7 04:53 versions -rw-r--r-- 1 Bengt None 0 Sep 7 11:05 åäö.txt C:\Users\Bengt\Desktop\src\mg2a\temp>ls *.txt ls: cannot access '*.txt': No such file or directory It looks as if you're using a Windows command prompt rather than Bash. Both 'problems' are actually a feature of the command prompt. Try again from a Bash shell. Dave. -- 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: Bug in arguments in console
David Stacey wrote: >On 25/09/16 12:00, Bengt Larsson wrote: >> C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo åäö >> åäö >> >> C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo "åäö" >> "åäö" >> >> (the quote marks are left in) >> >> C:\Users\Bengt\Desktop\src\mg2a\temp>ls -l >> total 1 >> -rw-r--r-- 1 Bengt None 0 Sep 7 01:07 blah.txt >> -rw-r--r-- 1 Bengt None 23 Sep 7 04:53 versions >> -rw-r--r-- 1 Bengt None 0 Sep 7 11:05 åäö.txt >> >> C:\Users\Bengt\Desktop\src\mg2a\temp>ls *.txt >> ls: cannot access '*.txt': No such file or directory > >It looks as if you're using a Windows command prompt rather than Bash. >Both 'problems' are actually a feature of the command prompt. No they're not. It worked in 2.5.2. >Try again >from a Bash shell. The arrogance of it. -- 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: More cygwin installations
On Sun, Sep 25, 2016 at 10:17 AM, Andrey Repin wrote: > Greetings, Silver Zachara! > >> can i install cygwin multiple times to different folders? E.g. >> c:\cygwin64, c:\cygwin64_x_test1, c:\cygwin64_x_test2 > >> I want to know, if there will not be any collisions or something similar. >> Or there have to be only one cygwin installation? > > You MAY use multiple parallel installations. But it is least advisable for > people unfamiliar with environment, clashes may occur and you would have a > hard(-er) time figuring them out. I don not see such big risk with multiple installations. Basic rules appliy: - separate PATH between the diffent installations. defining CYGWIN_NOWINPATH help on it - don't mix services as they will be called all in the same way by the different installation. > If you indeed need test installations, a virtual machine is the better route, > IMO. Usually if Virtual Machines are possible there are less motives to use cygwin; people developing for cygwin are of course the exception. > With best regards, > Andrey Repin Regards Marco -- 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: Bug in arguments in console
On 25/09/2016 13:31, Bengt Larsson wrote: David Stacey wrote: On 25/09/16 12:00, Bengt Larsson wrote: C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo åäö åäö C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo "åäö" "åäö" (the quote marks are left in) C:\Users\Bengt\Desktop\src\mg2a\temp>ls -l total 1 -rw-r--r-- 1 Bengt None 0 Sep 7 01:07 blah.txt -rw-r--r-- 1 Bengt None 23 Sep 7 04:53 versions -rw-r--r-- 1 Bengt None 0 Sep 7 11:05 åäö.txt C:\Users\Bengt\Desktop\src\mg2a\temp>ls *.txt ls: cannot access '*.txt': No such file or directory It looks as if you're using a Windows command prompt rather than Bash. Both 'problems' are actually a feature of the command prompt. No they're not. It worked in 2.5.2. Try again from a Bash shell. The arrogance of it. Hi Bengt, your answer is for me puzzling. What do you mean ? I see no problem on bash, for both case with mintty and with windows console; but I have not understood what are you using for your test. $ uname -srm CYGWIN_NT-6.1 2.6.0(0.304/5/3) x86_64 $ ls -l total 0 -rw-r--r-- 1 marco Administrators 0 Sep 25 18:43 ÜÖÄöäpß.txt $ ls *.txt ÜÖÄöäpß.txt I have also no problem on echo, also for both (mintty and console) $ echo ÖÄöäüß ÖÄöäüß Regards Marco -- 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: Bug in arguments in console
Greetings, Bengt Larsson! > David Stacey wrote: >>On 25/09/16 12:00, Bengt Larsson wrote: >>> C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo åäö >>> åäö >>> >>> C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo "åäö" >>> "åäö" >>> >>> (the quote marks are left in) >>> >>> C:\Users\Bengt\Desktop\src\mg2a\temp>ls -l >>> total 1 >>> -rw-r--r-- 1 Bengt None 0 Sep 7 01:07 blah.txt >>> -rw-r--r-- 1 Bengt None 23 Sep 7 04:53 versions >>> -rw-r--r-- 1 Bengt None 0 Sep 7 11:05 åäö.txt >>> >>> C:\Users\Bengt\Desktop\src\mg2a\temp>ls *.txt >>> ls: cannot access '*.txt': No such file or directory >> >>It looks as if you're using a Windows command prompt rather than Bash. >>Both 'problems' are actually a feature of the command prompt. > No they're not. It worked in 2.5.2. As David said, this is a "feature" of a Windows CMD shell. >>Try again >>from a Bash shell. > The arrogance of it. ...is yours. -- With best regards, Andrey Repin Sunday, September 25, 2016 20:06:39 Sorry for my terrible english...
[ANNOUNCEMENT] Updated: irssi-0.8.20-1
New version 0.8.20-1 irssi irssi-devel have been uploaded. CHANGES This is a new upstream release focused on bug fix. https://irssi.org/2016/09/21/irssi-0.8.20-released/ full list of changes https://github.com/irssi/irssi/releases DESCRIPTION Irssi is a terminal based IRC client for UNIX systems. It also supports SILC and ICB protocols via plugins. HOMEPAGE http://www.irssi.org Regards Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) com . -- 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: moving Cygwin64 to another drive
Thanks Marco, the -zb option to robocopy did the trick. (Now for the next issues...) -ernie On 9/23/2016 9:59 PM, Marco Atzeri wrote: On 24/09/2016 03:26, Ernie Rael wrote: On 9/23/2016 4:28 PM, Brian Inglis wrote: On 2016-09-23 17:11, Ernie Rael wrote: I found a thread, https://cygwin.com/ml/cygwin/2015-04/msg8.html, from last year where Corinna suggests the following (which works for her; she notes YMMV) robocopy C:\cygwin64 F:\cygwin64 /e /purge /z /copyall /sl Run robocopy as admin from an elevated command shell (bash or cmd) with Administrator privileges. Simply running as admin doesn't solve the problem. $ robocopy C:/cygwin64 F:/cygwin64 -e -purge -z -copyall -sl 100%New File 210shells 100%New File1595ssh_config New File 668 ssh_host_dsa_key 2016/09/23 18:06:38 ERROR 5 (0x0005) Copying File C:\cygwin64\etc\ssh_host_dsa_key Access is denied. Waiting 30 seconds... ADMIN erra@spirit ~ $ id uid=1000(erra) gid=513(None) groups=513(None),544(Administrators),545(Users),1007(HomeOffice) try with options /ZB :: use restartable mode; if access denied use Backup mode. Regards Marco -- 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: Bug in arguments in console
Am 25.09.2016 um 13:11 schrieb David Stacey: On 25/09/16 12:00, Bengt Larsson wrote: C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo åäö åäö C:\Users\Bengt\Desktop\src\mg2a\temp>\cygwin64\bin\echo "åäö" "åäö" (the quote marks are left in) C:\Users\Bengt\Desktop\src\mg2a\temp>ls -l total 1 -rw-r--r-- 1 Bengt None 0 Sep 7 01:07 blah.txt -rw-r--r-- 1 Bengt None 23 Sep 7 04:53 versions -rw-r--r-- 1 Bengt None 0 Sep 7 11:05 åäö.txt C:\Users\Bengt\Desktop\src\mg2a\temp>ls *.txt ls: cannot access '*.txt': No such file or directory It looks as if you're using a Windows command prompt rather than Bash. Both 'problems' are actually a feature of the command prompt. Try again from a Bash shell. He's talking about an interworking issue between Windows cmd and cygwin (which isn't completely out of scope of cygwin); and in fact, there has been a recent change, look for the mail thread "pass arguments enclosed with double quotes from bash shell to windows program". In fact, with two files, one of them containing non-ASCII characters, like ab.txt and äö.txt, the simplified test case C:\whatever>echo *.txt displays this with cygwin 2.5.2: ab.txt äö.txt and this with cygwin 2.6.0: *.txt Considering that the change, as I remember, was a quite successful workaround for problems with quote marks, it may be considered a trade-off with changed bias, rather than a bug, however :) -- Thomas -- 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] texlive 20160520-3
The following packages have been uploaded to the Cygwin distribution: * texlive-20160520-3 * libkpathsea6-20160520-3 * libkpathsea-devel-20160520-3 * libptexenc1-20160520-3 * libptexenc-devel-20160520-3 * libsynctex1-20160520-3 * libsynctex-devel-20160520-3 * libtexlua52_5-20160520-3 * libtexlua52-devel-20160520-3 * libtexluajit2-20160520-3 * libtexluajit-devel-20160520-3 TeX Live provides a comprehensive, cross-platform TeX system. It includes all the major TeX-related programs, macro packages, and fonts that are free software, including support for many languages around the world. This release is a rebuild of the TeX Live 2016 binaries and supporting libraries to incorporate an upstream bugfix: http://tug.org/svn/texlive/trunk/Build/source/texk/tex4htk/tex4ht.c?view=log&pathrev=42110 The bug only affected htxelatex and related programs. Ken Brown Cygwin's TeX Live maintainer -- 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
Setting up cygrunsrv after moving installation to another drive
I have just moved (robocopy) cygwin installation from C:/cygwin64 to F:/cygwin64 (win7). My stumbling block is handling cygrunsrv. For cygrunsrv, I thought I could change the service properties to start it from F:/..., but I can't figure out how to do that on Win7. Any suggestions on how best to get cygrunsrv going/installed after moving cygwin installation? -ernie -- 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: Setting up cygrunsrv after moving installation to another drive
On 2016-09-25 17:28, Ernie Rael wrote: I have just moved (robocopy) cygwin installation from C:/cygwin64 to F:/cygwin64 (win7). My stumbling block is handling cygrunsrv. For cygrunsrv, I thought I could change the service properties to start it from F:/..., but I can't figure out how to do that on Win7. Any suggestions on how best to get cygrunsrv going/installed after moving cygwin installation? $ sc qc cygserver will show how the service is currently configured e.g. [SC] QueryServiceConfig SUCCESS SERVICE_NAME: cygserver TYPE : 10 WIN32_OWN_PROCESS START_TYPE : 2 AUTO_START (DELAYED) ERROR_CONTROL : 1 NORMAL BINARY_PATH_NAME : C:\cygwin64\bin\cygrunsrv.exe LOAD_ORDER_GROUP : TAG: 0 DISPLAY_NAME : CYGWIN cygserver DEPENDENCIES : SERVICE_START_NAME : LocalSystem From an elevated prompt (run as Admin): $ sc config cygserver binPath= $(cygpath -w $(which cygrunsrv)) or the Windows equivalent from an elevated cmd prompt: sc config cygserver binPath= F:\cygwin64\bin\cygrunsrv.exe IIRC the space after the = is required. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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] openjpeg2 2.1.1-1
The following packages have been uploaded to the Cygwin distribution: * openjpeg2-2.1.1-1 * libopenjp2_7-2.1.1-1 * libopenjp2-devel-2.1.1-1 * libopenjp2-doc-2.1.1-1 * mingw64-i686-openjpeg2-2.1.1-1 * mingw64-x86_64-openjpeg2-2.1.1-1 The OpenJPEG library is an open-source JPEG 2000 codec written in C language. It has been developed in order to promote the use of JPEG 2000, the new still-image compression standard from the Joint Photographic Experts Group (JPEG). This is an update to the latest upstream release, plus patches for CVE-2016-7163: https://bugzilla.redhat.com/show_bug.cgi?id=1374329 -- 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
