Just noticed that Windows 8.1 compatibility was missing from
setup*.exe.manifest; patch attached.
Yaakov
2014-02-25 Yaakov Selkowitz yselkow...@users.sourceforge.net
* setup.exe.manifest: Add Windows 8.1 to compatibility list.
* setup64.exe.manifest: Ditto.
Index:
On Feb 25 10:56, Yaakov (Cygwin/X) wrote:
Just noticed that Windows 8.1 compatibility was missing from
setup*.exe.manifest; patch attached.
Yaakov
2014-02-25 Yaakov Selkowitz yselkow...@users.sourceforge.net
* setup.exe.manifest: Add Windows 8.1 to compatibility list.
*
Corinna Vinschen writes:
I added the 8.1 GUID to setup on 2013-11-19 already. Did we have no new
release since then?
I don't think that version was ever released on cygwin.com.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Wavetables for the Terratec
On Tue, Feb 25, 2014 at 07:06:27PM +0100, Achim Gratz wrote:
Corinna Vinschen writes:
I added the 8.1 GUID to setup on 2013-11-19 already. Did we have no new
release since then?
I don't think that version was ever released on cygwin.com.
I'll release a new version ASAP.
cgf
On Tue, Feb 25, 2014 at 01:13:29PM -0500, Christopher Faylor wrote:
On Tue, Feb 25, 2014 at 07:06:27PM +0100, Achim Gratz wrote:
Corinna Vinschen writes:
I added the 8.1 GUID to setup on 2013-11-19 already. Did we have no new
release since then?
I don't think that version was ever released on
Christopher Faylor writes:
On Tue, Feb 25, 2014 at 01:13:29PM -0500, Christopher Faylor wrote:
On Tue, Feb 25, 2014 at 07:06:27PM +0100, Achim Gratz wrote:
Corinna Vinschen writes:
I added the 8.1 GUID to setup on 2013-11-19 already. Did we have no new
release since then?
I don't think that
On Feb 25 19:58, Achim Gratz wrote:
Christopher Faylor writes:
On Tue, Feb 25, 2014 at 01:13:29PM -0500, Christopher Faylor wrote:
On Tue, Feb 25, 2014 at 07:06:27PM +0100, Achim Gratz wrote:
Corinna Vinschen writes:
I added the 8.1 GUID to setup on 2013-11-19 already. Did we have no new
Corinna Vinschen writes:
I'm not sure what you're doing.
I'm making two builds from two Cygwin installations (one 32bit and one
64bit) with the native toolchain (not cross-compiled). I've had some
disk space problems that prevented installation of the cross compilation
toolchain(s) originally.
On Tue, Feb 25, 2014 at 09:32:20PM +0100, Achim Gratz wrote:
Corinna Vinschen writes:
I'm not sure what you're doing.
I'm making two builds from two Cygwin installations (one 32bit and one
64bit) with the native toolchain (not cross-compiled). I've had some
disk space problems that prevented
The following packages have been updated in the Cygwin distribution:
*** xorg-server-*1.15.0-3
These packages contain XWin and the other X.Org X11 servers.
The following cygwin-specific changes have been made since 1.15.0-2:
* Repair clipboard thread restart to fix clipboard integration when
CVSROOT:/cvs/src
Module name:src
Branch: cygwin-1_7_29-release-branchpoint
Changes by: c...@sourceware.org 2014-02-26 01:40:49
Modified files:
winsup/cygwin : ChangeLog fhandler.h fhandler_console.cc
Log message:
* fhandler.h
On 2/25/2014 3:10 AM, Thomalla, Martin wrote:
Hello,
in order to get additional features into vim (lua and python) I need to
build it from source.
So I have downloaded the source and gcc through the cygwin setup-x86_64.exe
and build vim from source.
$ cd /usr/src/vim74
$ ./configure
Which vim sources that work in cygwin should I use instead?
A quick review of the files you've provided and your description of
what
you've done doesn't raise any red flags. I'll suggest trying to
remove the
Cygwin-provided VIM packages to be sure there is no
On 2/25/2014 10:20 AM, Thomalla, Martin wrote:
A quick review of the files you've provided and your description of what
you've done doesn't raise any red flags. I'll suggest trying to remove the
Cygwin-provided VIM packages to be sure there is no collision/interaction.
If
On 2014-02-25 16:35, Larry Hall (Cygwin) wrote:
On 2/25/2014 10:20 AM, Thomalla, Martin wrote:
A quick review of the files you've provided and your description
of what
you've done doesn't raise any red flags. I'll suggest trying to
remove the
Cygwin-provided VIM packages to be
On 2/25/2014 10:43 AM, Thomalla, Martin wrote:
On 2014-02-25 16:35, Larry Hall (Cygwin) wrote:
On 2/25/2014 10:20 AM, Thomalla, Martin wrote:
A quick review of the files you've provided and your description of
what
you've done doesn't raise any red flags. I'll suggest trying to
Corinna Vinschen writes:
This is a pretty intrusive change, in need of some serious testing, so
I'd like to ask for volunteers. The latest 2014-02-13 snapshot from
http://cygwin.com/snapshots/ contains the changes, including the latest
bugfix.
I've tested the 2014-02-19 snapshot at work.
On Tue, Feb 25, 2014 at 06:25:18PM +, Shaun Gosse wrote:
Oh, and http://cygwin.com/problems.html suggested running cygcheck, but it's
not found:
-sh-4.1$ cygcheck
-sh: cygcheck: command not found
It's there if you have a shell prompt. You likely just have to
specify the complete path.
You
Greetings, Achim Gratz!
2. I use a few volumes on NetApp filers that have security set up so
that you can't change attributes. That means POSIX permissions are
always listed as .
That seems like a bug elsewhere. Being able to change permissions shouldn't
restrict you from requesting
Andrey Repin writes:
That seems like a bug elsewhere. Being able to change permissions shouldn't
restrict you from requesting them.
There is no bug, not in Cygwin nor anywhere else. The standard file
attributes are all cleared and since I can't set any of them (a policy
which gets inherited)
On Feb 25 19:14, Achim Gratz wrote:
Corinna Vinschen writes:
This is a pretty intrusive change, in need of some serious testing, so
I'd like to ask for volunteers. The latest 2014-02-13 snapshot from
http://cygwin.com/snapshots/ contains the changes, including the latest
bugfix.
I've
Corinna Vinschen writes:
The stuff in the `id' application is not cached at all. Caching is
inherited from the parent process, but the parent never asked for all
your groups so it hasn't cached this information. Every invocation of
id has to request the group info anew.
OK, then I was
On Wed, Feb 19, 2014 at 7:42 PM, Steven Penny wrote:
I found a problem with the new snapshots. If you
1. start Cygwin with Cygwin.bat
2. enter man bash
3. enter Page Down then Page Up
This is still happening with 2014-02-24 snapshot.
--
Problem reports: http://cygwin.com/problems.html
My previous send didn't go through apparently; needs address obfuscation, now
done.
-Original Message-
From: Shaun Gosse
Sent: Tuesday, February 25, 2014 2:00 PM
To: 'cygwin AT cygwin DOT com'
Subject: RE: postinstall script errors (-1073741819 / STATUS_ACCESS_VIOLATION)
on default
Apologies for the spam...forgot to reattach the results of the cygcheck when
resending.
-Original Message-
From: Shaun Gosse
Sent: Tuesday, February 25, 2014 3:07 PM
To: 'cygwin AT Cygwin DOT com'
Subject: RE: postinstall script errors (-1073741819 / STATUS_ACCESS_VIOLATION)
on default
Hi,
I've noticed after installing an update the Cygwin64 appears to ignore
the contents of the shell field in /etc/passwd. I normally run
/bin/tcsh as my shell, and changing this field used to result in any new
login shells running tcsh. Now it just runs bash regardless.
Has something changed?
On Feb 25 21:25, Achim Gratz wrote:
Corinna Vinschen writes:
The stuff in the `id' application is not cached at all. Caching is
inherited from the parent process, but the parent never asked for all
your groups so it hasn't cached this information. Every invocation of
id has to request
On Feb 25 13:52, Jim Burwell wrote:
Hi,
I've noticed after installing an update the Cygwin64 appears to ignore
the contents of the shell field in /etc/passwd. I normally run
/bin/tcsh as my shell, and changing this field used to result in any new
login shells running tcsh. Now it just
Greetings, Jim Burwell!
Please don't attach to existing threads, if you're opening a new topic.
Post a new message to the list instead.
I've noticed after installing an update the Cygwin64 appears to ignore
the contents of the shell field in /etc/passwd. I normally run
/bin/tcsh as my shell,
Greetings, Corinna Vinschen!
Also, more radically, if we drop the functionality to define another
group name for a group, we could drop the requirement to open an LDAP
connection to fetch group information to the DC entirely(*). This would
only affect domain groups, local groups could still
David Stacey sent the following at Monday, February 24, 2014 3:27 PM
On 24/02/2014 17:27, Dr. Alexander Kleinsorge wrote:
But after (export AUDIODRIVER=ao ; play ding.wav)
I see messages indicating successfull playing and application is waiting
the time the wav-file takes,
but no sound. But I
On 2/25/2014 13:55, Corinna Vinschen wrote:
On Feb 25 13:52, Jim Burwell wrote:
Hi,
I've noticed after installing an update the Cygwin64 appears to ignore
the contents of the shell field in /etc/passwd. I normally run
/bin/tcsh as my shell, and changing this field used to result in any new
On 2/25/2014 6:24 PM, Jim Burwell wrote:
On 2/25/2014 13:55, Corinna Vinschen wrote:
On Feb 25 13:52, Jim Burwell wrote:
Hi,
I've noticed after installing an update the Cygwin64 appears to ignore
the contents of the shell field in /etc/passwd. I normally run
/bin/tcsh as my shell, and
Hi,
i have a strange problem with tcp_wrappers in conjunction with stunnel cygwin
port. (cc`ing stunnel cygwin maintainer because of that).
I`m trying to secure an rsync which is started in daemon-mode in an inetd-style
via stunnel. I`m on Win8 64Bit with a recent 64bit Cygwin installation.
Greetings, Corinna Vinschen!
Other than that, I just had an in-shower inspiration how to speed up
`id' specificially. The getgroups(2) call is in the center of this and
I could probably speed up the stuiff a lot by opening the LDAP
connection in getgroups only once.
Isn't local SAM
I'm trying to verify the signatures on the latest setup.exe files and I'm
finding that they don't match:
$ gpg --verify setup-x86.exe.sig
gpg: Signature made Fri 13 Dec 2013 17:24:37 GMT using DSA key ID 676041BA
gpg: BAD signature from Cygwin Cygwin AT cygwin.com
$ gpg --verify
Hi,
Risking the wrath that I should just report the bug, I would like to
just get some advice on how to go about it.
I'm encountering a problem with a rather new Cygwin package/feature that
if reproducible, has serious consequence on the hosting Windows
platform.
My concern is that if I list
37 matches
Mail list logo
