xz 5.2.3-1

The following packages have been uploaded to the Cygwin distribution: * xz-5.2.3-1 * liblzma5-5.2.3-1 * liblzma-devel-5.2.3-1 * mingw64-i686-xz-5.2.3-1 * mingw64-x86_64-xz-5.2.3-1 XZ Utils is free general-purpose data compression software with high compression ratio. XZ Utils are the successor

[ANNOUNCEMENT] xz 5.2.3-1

The following packages have been uploaded to the Cygwin distribution: * xz-5.2.3-1 * liblzma5-5.2.3-1 * liblzma-devel-5.2.3-1 * mingw64-i686-xz-5.2.3-1 * mingw64-x86_64-xz-5.2.3-1 XZ Utils is free general-purpose data compression software with high compression ratio. XZ Utils are the successor

[ANNOUNCEMENT] opus-tools 0.1.10-1

The following packages have been uploaded to the Cygwin distribution: * opus-tools-0.1.10-1 Opus-tools provides command-line utilities to encode, inspect, and decode .opus files. This is an initial release for Cygwin. -- Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ:

[ANNOUNCEMENT] libgpg-error 1.27-1, libgcrypt 1.7.6-1

The following packages have been uploaded to the Cygwin distribution: * libgcrypt20-1.7.6-1 * libgcrypt-devel-1.7.6-1 * libgpg-error0-1.27-1 * libgpg-error-devel-1.27-1 * mingw64-i686-libgcrypt-1.7.6-1 * mingw64-i686-libgpg-error-1.27-1 * mingw64-x86_64-libgcrypt-1.7.6-1 *

opus-tools 0.1.10-1

The following packages have been uploaded to the Cygwin distribution: * opus-tools-0.1.10-1 Opus-tools provides command-line utilities to encode, inspect, and decode .opus files. This is an initial release for Cygwin. -- Yaakov

libgpg-error 1.27-1, libgcrypt 1.7.6-1

The following packages have been uploaded to the Cygwin distribution: * libgcrypt20-1.7.6-1 * libgcrypt-devel-1.7.6-1 * libgpg-error0-1.27-1 * libgpg-error-devel-1.27-1 * mingw64-i686-libgcrypt-1.7.6-1 * mingw64-i686-libgpg-error-1.27-1 * mingw64-x86_64-libgcrypt-1.7.6-1 *

Re: Access windows environment variable via cygwin

On 05/11/2017 10:44 PM, Eliot Moss wrote: On 5/11/2017 9:14 PM, ChampS wrote: Hi, I want to use Cygwin to access all Windows applications installed on my Windows 7 system. The Problem is that Windows is using spaces in its environment variable 'Path' and Cygwin can not handle the spaces. Is

Re: Access windows environment variable via cygwin

On 2017-05-11 19:14, ChampS wrote: > I want to use Cygwin to access all Windows applications installed on > my Windows 7 system. The Problem is that Windows is using spaces in > its environment variable 'Path' and Cygwin can not handle the spaces. > Is there a way to use the Windows environment

Re: Access windows environment variable via cygwin

On 5/11/2017 9:14 PM, ChampS wrote: Hi, I want to use Cygwin to access all Windows applications installed on my Windows 7 system. The Problem is that Windows is using spaces in its environment variable 'Path' and Cygwin can not handle the spaces. Is there a way to use the Windows environment

Re: [ITP] python2-future and python3-future

On 2017-05-11 15:21, Jon Turney wrote: On 11/05/2017 18:52, Yaakov Selkowitz wrote: On 2017-05-11 12:11, Jon Turney wrote: python-future is a compatibility layer for Python 2 and Python 3 This is a pre-requisite of buildbot-worker 0.9.x The preferred packaging scheme for Python modules is

[ANNOUNCEMENT] cygport 0.24.1-1

The following packages have been uploaded to the Cygwin distribution: * cygport-0.24.1-1 cygport is the standard method for building and maintaining packages for the Cygwin distribution. This release contains assorted bugfixes. Jon Turney (1): Update documentation of all Ken Brown (1):

cygport 0.24.1-1

The following packages have been uploaded to the Cygwin distribution: * cygport-0.24.1-1 cygport is the standard method for building and maintaining packages for the Cygwin distribution. This release contains assorted bugfixes. Jon Turney (1): Update documentation of all Ken Brown (1):

Access windows environment variable via cygwin

Hi, I want to use Cygwin to access all Windows applications installed on my Windows 7 system. The Problem is that Windows is using spaces in its environment variable 'Path' and Cygwin can not handle the spaces. Is there a way to use the Windows environment variable 'Path' even with spaces in

[ANNOUNCEMENT] Updated: Git v2.12.3-1

Version 2.12.3-1 of Git has been uploaded and should be coming soon to a mirror near you. This update includes the following packages: - git - git-cvs - git-debuginfo - git-email - git-gui - gitk - git-svn This is an update to the latest upstream release. For a full list of the upstream changes

Updated: Git v2.12.3-1

Version 2.12.3-1 of Git has been uploaded and should be coming soon to a mirror near you. This update includes the following packages: - git - git-cvs - git-debuginfo - git-email - git-gui - gitk - git-svn This is an update to the latest upstream release. For a full list of the upstream changes

Re: [ITP] python2-future and python3-future

On 11/05/2017 18:52, Yaakov Selkowitz wrote: On 2017-05-11 12:11, Jon Turney wrote: python-future is a compatibility layer for Python 2 and Python 3 This is a pre-requisite of buildbot-worker 0.9.x [...] The preferred packaging scheme for Python modules is now python-wheel cygclass. So

Re: opam package

On 10/05/2017 08:44, Andy Li wrote: Hi, I would like to create and maintain a cygwin package for OPAM, i.e. OCaml Package Manager. It would be a dependency of the next version Haxe, which I would like to package too. The initial cygport file I created can be found at:

Re: setup release candidate - please test

Symantec Endpoint Protection v. 12.1.6 did not like this file, but I was able to exclude it. -- Jim Reisert AD1C, , http://www.ad1c.us -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Re: [ITP] python2-future and python3-future

On 2017-05-11 12:11, Jon Turney wrote: python-future is a compatibility layer for Python 2 and Python 3 This is a pre-requisite of buildbot-worker 0.9.x cygport files: https://github.com/jon-turney/python2-future-cygport/blob/master/python2-future.cygport

[ITP] python2-future and python3-future

python-future is a compatibility layer for Python 2 and Python 3 This is a pre-requisite of buildbot-worker 0.9.x cygport files: https://github.com/jon-turney/python2-future-cygport/blob/master/python2-future.cygport

Re: hdparm windows phisical disks question

What does ls /dev/hd* or ls /dev/sd* give you? On 11/05/2017 16:21, Emanuele Belfiore wrote: I'm using hdparm on windows, eg: hdparm -y /dev/hda My question is: if I have more than 26 phisical disks, what parameter I have to pass (/dev/hd?) ? -- Problem reports:

hdparm windows phisical disks question

Hello, I'm using hdparm on windows, eg: hdparm -y /dev/hda My question is: if I have more than 26 phisical disks, what parameter I have to pass (/dev/hd?) ? Thank You Emanuele Belfiore -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/

Re: adopt and update libatomic_ops and libgc

Oh, that was unexpected! Thank you :D Best, Andy On Thu, May 11, 2017 at 10:27 PM, Andrew Schulman wrote: >> I added libatomic_ops and libgc to your package list. > > Gold stars awarded! https://cygwin.com/goldstars/#AL >

Re: adopt and update libatomic_ops and libgc

> I added libatomic_ops and libgc to your package list. Gold stars awarded! https://cygwin.com/goldstars/#AL

[PATCH] Ensure that a blocking send() on a socket returns (with success) if a signal is handled mid-transition and SA_RESTART is not set.

--- winsup/cygwin/fhandler_socket.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/winsup/cygwin/fhandler_socket.cc b/winsup/cygwin/fhandler_socket.cc index f3d1d69..c7ed681 100644 --- a/winsup/cygwin/fhandler_socket.cc +++ b/winsup/cygwin/fhandler_socket.cc @@ -1851,7

Re: [PATCH cygport 2/3] Don't allow SRC_URI or PATCH_URI to depend on ARCH

On 06/05/2017 12:32, Jon Turney wrote: On 05/05/2017 23:06, Yaakov Selkowitz wrote: On 2017-05-02 08:13, Jon Turney wrote: The values which SRC_URI and PATCH_URI evaluate to should not change depending on ARCH, as this will make the source package arch-dependent I think this would require a

Re: grep3.0 of cygwin changed treatment of CR/LF.

On 11/05/2017 08:56, 川崎 正貴 wrote: I found a problem on grep 3.0 on command prompt of Windows10 with 64bit cygwin. It seems that treatment of CR/LF is changed. I expect cygwin disposes of CR/LF. See announcement https://sourceware.org/ml/cygwin-announce/2017-02/msg00035.html use d2u to remove

Re: 'cygport dep' is empty for orpie

> On 2017-05-10 07:03, Andrew Schulman wrote: > > $ cygport orpie.cygport finish all > > ... > orpie requires: > > $ cygport orpie.cygport dep > > $ grep requires: orpie-1.5.2-3.x86_64/dist/orpie/orpie-1.5.2-3.hint > > requires: > > > > And yet... > > > > $ ll

cygwin@cygwin.com your Ref is 52114-975

Attn: % cygwin@cygwin.com % Some days ago your email cygwin@cygwin.com was rewarded, please did you get the details of the email? Angy Omari (Contact Manager) omaria...@yandex.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/

grep3.0 of cygwin changed treatment of CR/LF.

I found a problem on grep 3.0 on command prompt of Windows10 with 64bit cygwin. It seems that treatment of CR/LF is changed. I expect cygwin disposes of CR/LF. grep 2.25(correct) >uname -a CYGWIN_NT-10.0 PCNAME 2.6.0(0.304/5/3) 2016-08-31 14:32 x86_64 Cygwin >env LC_ALL=C grep --version grep (GNU