Latest setup.exe not code-signed?
Hello, It looks like the new setup-x86_64.exe is not code-signed? Is that on purpose? IIRC, the previous versions were code-signed. Do we now only rely on the .sig signature file to verify it? Cheers, Kal -- 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: mintty window gets tilde characters "pressed" in it
On Wed, Dec 14, 2016 at 1:33 PM, David Karr wrote: > On Wed, Dec 14, 2016 at 12:06 PM, Thomas Wolff wrote: >> I've checked with Caffeine and traced mintty. It receives F15 key down, the >> key up. Caffeine claims to send key up only but that's not true. Please >> report this as a bug to Caffeine. > > Understood. I just did that. However, will that really make any > difference? If mintty only receives the keyup event, will that make it > ignore it entirely? I think I have a solution. I've looked at the command line options for caffeine many times, and I never noticed the "-useshift" option, which makes it use the shift key instead of f15. That should do the trick for me. I'm testing it now, and it appears to be fine (and it also doesn't appear to cause trouble if I'm typing while the event is emitted). -- 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: Installer names not meaningful enough
On Wed, Dec 14, 2016 at 4:50 PM, cyg Simple wrote: > And if we were purely *nix your argument might hold merit but this setup > executable provides a Windows OS based install of a Windows based > application set known as Cygwin. If we were purely *nix, we wouldn't be on Windows in the first place. > The name of the executable has never been a problem; why are you trying > to create one? There are just as many that would keep it simple and > leave the name as is. I don't recall anyone trying to create a problem so much as find out the reasoning behind the decision and ask for the setup executable version information to be more accessible than it currently is. At present, it does not appear that the cygwin pages list the current setup executable version at all, forcing either an aborted setup run when the setup executable itself reports that the setup.ini file indicates the currently running executable is outdated, or downloading *something* to see if the version of setup available for download has changed. -- Erik -- 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: Installer names not meaningful enough
On 12/14/2016 4:17 PM, Erik Soderquist wrote: > On Fri, Dec 9, 2016 at 6:28 AM, Vlado wrote: >> Erik (and others), >> >> don't worry about Setup version, please. >> >> Use this script: >> https://gist.github.com/Vlado-99/1d59bf05b70481377ff90bb53e13bb2d >> >> - Setup is downloaded only if gpg signature changes (only very small .sig >> file is re-downloaded every time) > > > While work arounds are great and appreciated, they still don't address > the original question of why the version of the setup executable isn't > part of the filename like it is in most of the *nix packages and > installers (or at least most of the ones I have been exposed to). > And if we were purely *nix your argument might hold merit but this setup executable provides a Windows OS based install of a Windows based application set known as Cygwin. The name of the executable has never been a problem; why are you trying to create one? There are just as many that would keep it simple and leave the name as is. -- 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
Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
On 12/14/2016 10:28 AM, Christopher Faylor wrote: > On Wed, Dec 14, 2016 at 09:15:46AM -0500, cyg Simple wrote: >> On 12/10/2016 3:39 PM, Christopher Faylor wrote: >>> On Wed, Nov 30, 2016 at 11:00:12AM -0500, Christopher Faylor wrote: On Wed, Nov 30, 2016 at 10:55:49AM -0500, Frank Ch. Eigler wrote: > cygsimple wrote: >> See the description below of a problem that is occurring because of >> DMARC rules in place by yahoo.com. Is there anything you can do for >> this? > > cgf, any chance of updating our copy of ezmlm-toaster etc.? > Newer-than-2014 versions of ezmlm-idx seem to have some DMARC > capabilities. I started looking at this when it came in. No ETA yet. >>> >>> Huh. I thought I sent an update about this but it vanished in the aether. >>> >>> I just turned on a new DMARC-aware version of ezmlm-send which rewrites >>> the From address for any domain that is DMARC sensitive to something like: >>> >>> "User name via mailinglist " >>> >>> when the mail is broadcast to the mailing list. I would have done this >>> sooner but my ezmlm skills were really rusty and I almost ran out of >>> extremities to shoot. >>> >>> Please send any errors or issues encountered to overse...@sourceware.org. >> >> The issue continues. >> >> Here are the message numbers: >> >> 206020 >> 206062 > > I sent the above on 12/10. Those messages were sent on 12/1 and 12/7 > respectively. The change was not retroactive. But I only received the reject notice today. Yes, I understand the delay mechanism across multiple systems. Thanks for checking. -- 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
Re: mintty window gets tilde characters "pressed" in it
On Wed, Dec 14, 2016 at 12:06 PM, Thomas Wolff wrote: > I've checked with Caffeine and traced mintty. It receives F15 key down, the > key up. Caffeine claims to send key up only but that's not true. Please > report this as a bug to Caffeine. Understood. I just did that. However, will that really make any difference? If mintty only receives the keyup event, will that make it ignore it entirely? > X11 does not seem to handle F13...F24 at all because they don't appear on a > typical PC keyboard (that's my assumption), so it doesn't occur in xterm. It > generates a ~ only in terminal applications because a number of key escape > sequences end with ~. > > The key event from Caffeine can be distinguished from a real key event, > because it does not include keyboard scancode information. So a workaround > is possible in theory. I'm not sure though whether that's a good idea as > there may be other applications that inject keys the same way, e.g. drivers > of other input devices, like Braille. > Opinions and information are appreciated. -- 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: Installer names not meaningful enough
On Fri, Dec 9, 2016 at 6:28 AM, Vlado wrote: > Erik (and others), > > don't worry about Setup version, please. > > Use this script: > https://gist.github.com/Vlado-99/1d59bf05b70481377ff90bb53e13bb2d > > - Setup is downloaded only if gpg signature changes (only very small .sig > file is re-downloaded every time) While work arounds are great and appreciated, they still don't address the original question of why the version of the setup executable isn't part of the filename like it is in most of the *nix packages and installers (or at least most of the ones I have been exposed to). -- Erik -- 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: Editors set x-bit (sometimes)
From: Achim Gratz > I said "-exec +", although I concur it was too easy to miss. Indeed, I overlooked the "+" and was unfamiliar with that option to find. Glad I asked. Learned something today. Thanx for the clarification. ☺ --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
Re: mintty window gets tilde characters "pressed" in it
Greetings, David Karr! > I use a tool called "Windows Caffeine" that is used to keep the > display awake. What's wrong with correctly configured power saving settings?… -- With best regards, Andrey Repin Wednesday, December 14, 2016 23:07:16 Sorry for my terrible english...
Re: mintty window gets tilde characters "pressed" in it
Am 14.12.2016 um 18:48 schrieb David Karr: On Mon, Dec 12, 2016 at 10:18 AM, David Karr wrote: Win7. I believe my Cygwin version info is "2.5.2(0.297/5/3) 2016-06-23 14:29". I've been annoyed for a while with a symptom in my mintty windows. I will be typing along, or not, and suddenly a "~" character gets injected into the stream. It often is the only character at the prompt, so I can erase it and type my command, but it's really annoying when it appears while I'm typing. I was just reminded of it now when it injected the "~" right before I pressed enter on a "mkdir", so I had to then remove the dir I just created and recreate it. Is this something that Cygwin can control? I've determined what "instigates" this, but I find that it only mainly affects mintty and somewhat affects emacs. I've never seen a symptom in any other application. I use a tool called "Windows Caffeine" that is used to keep the display awake. It sends a "f15 key up" event every 59 seconds. That is what is producing the "~" character in the mintty window. I've also seen a symptom from this in Emacs, but it's harder to produce. It's not as simple as just having a text buffer in focus. I haven't been able to reliably produce it in Emacs, but the mintty symptom is very reproducible. I've checked with Caffeine and traced mintty. It receives F15 key down, the key up. Caffeine claims to send key up only but that's not true. Please report this as a bug to Caffeine. X11 does not seem to handle F13...F24 at all because they don't appear on a typical PC keyboard (that's my assumption), so it doesn't occur in xterm. It generates a ~ only in terminal applications because a number of key escape sequences end with ~. The key event from Caffeine can be distinguished from a real key event, because it does not include keyboard scancode information. So a workaround is possible in theory. I'm not sure though whether that's a good idea as there may be other applications that inject keys the same way, e.g. drivers of other input devices, like Braille. Opinions and information are appreciated. -- 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
Re: Editors set x-bit (sometimes)
Nellis, Kenneth writes:
> Really? I always thought the opposite. With -exec, doesn't
> find invoke the command for each single found object? While xargs
> allows a single command to operate on a whole slew of objects.
I said "-exec +", although I concur it was too easy to miss.
> For example:
> find ... -exec pgm {} \;
Try replacing the "\;" with "+", depending on whether pgm can deal with
multiple arguments.
> executes pgm separately for each found object while
> find ... | xargs pgm
> invokes pgm only once for as many files as will fit on the
> command line, which is quite a few.
Which is what
find ... -exec pgm {} +
will do, without piping the data to xarg and without you having to
remember that you really, really wanted to say
find … -print0 | xargs -0 pgm
unless you already know that there are no spaces or funny characters
anywhere in your filenames.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
--
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: Periodic search for FAQ link update for clean_setup.pl?
On 13/12/2016 16:57, Ian Lambert via cygwin wrote: Looking for suggestions on cleaning up package directories, https://cygwin.com/faq/faq.html#faq.setup.disk-space has a broken link, again, to clean_setup.pl ? Mailing list search finds: https://sourceware.org/ml/cygwin/2009-06/msg00573.html that has an old version attached, 1.0700 (2003-07-02). Is a newer version available or is that the latest, and could the FAQ link be fixed? Thanks for pointing this out. Since direct downloads from cygwin.com haven't been allowed for a long time, this FAQ should say something like "available at unsupported/clean_setup.pl in a Cygwin mirror" I'm not sure if this script still works, and it is, well..., unsupported :) -- 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: mintty window gets tilde characters "pressed" in it
On Mon, Dec 12, 2016 at 10:18 AM, David Karr wrote: > Win7. I believe my Cygwin version info is "2.5.2(0.297/5/3) 2016-06-23 > 14:29". > > I've been annoyed for a while with a symptom in my mintty windows. I > will be typing along, or not, and suddenly a "~" character gets > injected into the stream. It often is the only character at the > prompt, so I can erase it and type my command, but it's really > annoying when it appears while I'm typing. I was just reminded of it > now when it injected the "~" right before I pressed enter on a > "mkdir", so I had to then remove the dir I just created and recreate > it. > > Is this something that Cygwin can control? I've determined what "instigates" this, but I find that it only mainly affects mintty and somewhat affects emacs. I've never seen a symptom in any other application. I use a tool called "Windows Caffeine" that is used to keep the display awake. It sends a "f15 key up" event every 59 seconds. That is what is producing the "~" character in the mintty window. I've also seen a symptom from this in Emacs, but it's harder to produce. It's not as simple as just having a text buffer in focus. I haven't been able to reliably produce it in Emacs, but the mintty symptom is very reproducible. -- 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: Editors set x-bit (sometimes)
Greetings, Nellis, Kenneth!
>> From: Achim Gratz
>> .. the latter is slightly less efficient and you have to
>> do -print0/-0, but I tend to get it right more easily then the -exec
>> stuff.
> Really? I always thought the opposite. With -exec, doesn't
> find invoke the command for each single found object?
Depends, how do you set the find, and what the net effect you wan to achieve.
> While xargs allows a single command to operate on a whole slew of objects.
Which boils down to executing command every time for each argument.
> For example:
> find ... -exec pgm {} \;
> executes pgm separately for each found object
What about
find ... -exec pgm '{}' +
?
> while
> find ... | xargs pgm
> invokes pgm only once for as many files as will fit on the
> command line, which is quite a few.
> If I'm wrong about this, please share.
It really depends on what you are doing with find.
find . -iname *.php -execdir grep -qP '(?<=function )funcname' '{}' \; -print
is one thing, but
find . -date +7 -exec mv -t /dir '{}' +
is completely another.
> Or, perhaps we are talking about commands that only take
> a single object. In that case, you would need to say
> xargs -n1
> in which case, I agree, it is less efficient.
--
With best regards,
Andrey Repin
Wednesday, December 14, 2016 20:13:08
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: PHP 7.0.14 crashing with minimal set of extensions
Greetings, Yaakov Selkowitz! > On 2016-12-13 12:06, Andrey Repin wrote: >> Here's strace and stackdump from latest crash with Cygwin 2.6.1-2 >> project.rootdir.org/.offload/crash-php-7.14.tar.xz > Are you 100% sure that your code is compatible with PHP 7? The only > segfaults I have seen so far is with old code. It's Composer. It runs with native PHP7 of the same version just fine. -- With best regards, Andrey Repin Wednesday, December 14, 2016 13:05:58 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: Fwd: Re: DMARC - gmail.com or is it yahoo.com
On Wed, Dec 14, 2016 at 09:15:46AM -0500, cyg Simple wrote: >On 12/10/2016 3:39 PM, Christopher Faylor wrote: >> On Wed, Nov 30, 2016 at 11:00:12AM -0500, Christopher Faylor wrote: >>> On Wed, Nov 30, 2016 at 10:55:49AM -0500, Frank Ch. Eigler wrote: cygsimple wrote: > See the description below of a problem that is occurring because of > DMARC rules in place by yahoo.com. Is there anything you can do for this? cgf, any chance of updating our copy of ezmlm-toaster etc.? Newer-than-2014 versions of ezmlm-idx seem to have some DMARC capabilities. >>> >>> I started looking at this when it came in. No ETA yet. >> >> Huh. I thought I sent an update about this but it vanished in the aether. >> >> I just turned on a new DMARC-aware version of ezmlm-send which rewrites >> the From address for any domain that is DMARC sensitive to something like: >> >> "User name via mailinglist " >> >> when the mail is broadcast to the mailing list. I would have done this >> sooner but my ezmlm skills were really rusty and I almost ran out of >> extremities to shoot. >> >> Please send any errors or issues encountered to overse...@sourceware.org. > >The issue continues. > >Here are the message numbers: > > 206020 > 206062 I sent the above on 12/10. Those messages were sent on 12/1 and 12/7 respectively. The change was not retroactive. -- 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: PHP 7.0.14 crashing with minimal set of extensions
On 12/14/2016 2:34 AM, Yaakov Selkowitz wrote: > On 2016-12-13 12:06, Andrey Repin wrote: >> Here's strace and stackdump from latest crash with Cygwin 2.6.1-2 >> project.rootdir.org/.offload/crash-php-7.14.tar.xz > > Are you 100% sure that your code is compatible with PHP 7? The only > segfaults I have seen so far is with old code. > That was my first thought on the issue and I haven't even tried php 7.x.x yet. If the code works with php 5.x.x then you may need to modify the use of the API. -- 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
Re: Fwd: Re: DMARC - gmail.com or is it yahoo.com
On 12/10/2016 3:39 PM, Christopher Faylor wrote: > On Wed, Nov 30, 2016 at 11:00:12AM -0500, Christopher Faylor wrote: >> On Wed, Nov 30, 2016 at 10:55:49AM -0500, Frank Ch. Eigler wrote: >>> cygsimple wrote: See the description below of a problem that is occurring because of DMARC rules in place by yahoo.com. Is there anything you can do for this? >>> >>> cgf, any chance of updating our copy of ezmlm-toaster etc.? >>> Newer-than-2014 versions of ezmlm-idx seem to have some DMARC >>> capabilities. >> >> I started looking at this when it came in. No ETA yet. > > Huh. I thought I sent an update about this but it vanished in the aether. > > I just turned on a new DMARC-aware version of ezmlm-send which rewrites > the From address for any domain that is DMARC sensitive to something like: > > "User name via mailinglist " > > when the mail is broadcast to the mailing list. I would have done this > sooner but my ezmlm skills were really rusty and I almost ran out of > extremities to shoot. > > Please send any errors or issues encountered to overse...@sourceware.org. The issue continues. Here are the message numbers: 206020 206062 --- Enclosed is a copy of the bounce message I received. Return-Path: <> Received: (qmail 128079 invoked for bounce); 2 Dec 2016 17:38:50 - Date: 2 Dec 2016 17:38:50 - From: mailer-dae...@sourceware.org To: cygwin-return-2060...@cygwin.com Subject: failure notice Hi. This is the qmail-send program at sourceware.org. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. : User and password not set, continuing without authentication. 173.194.203.26 failed after I sent the message. Remote host said: 550-5.7.1 Unauthenticated email from yahoo.com is not accepted due to domain's 550-5.7.1 DMARC policy. Please contact the administrator of yahoo.com domain if 550-5.7.1 this was a legitimate mail. Please visit 550-5.7.1 https://support.google.com/mail/answer/2451690 to learn about the 550 5.7.1 DMARC initiative. e85si746691pfj.218 - gsmtp -- 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
[ANNOUNCEMENT] TEST RELEASE: Cygwin 2.6.1-0.3
Hi folks, I uploaded a new Cygwin test release 2.6.1-0.3. 2.6.1 will be a bugfix release only and the last release in 2016. This 0.3 only contains an internal change which hardens reads and writes on /dev/random and /dev/urandom against crashes. This version will likely become the official release so please test. === What's new: --- - Add _PC_CASE_INSENSITIVE flag to [f]pathconf(3). Bug Fixes - - Fix regression in console charset handling Addresses: https://cygwin.com/ml/cygwin/2016-10/msg0.html - Fix case-sensitivity problem when renaming directories Addresses: https://cygwin.com/ml/cygwin/2016-09/msg00264.html - Fix SetThreadName with gdb 7.10 on x86 Addresses: https://cygwin.com/ml/cygwin/2016-09/msg00143.html - Fix broken newlocale handling with empty local string "". Found by Coverity. - Fix assorted buffer overflows and resource leaks found by Coverity. - Correctly define __hidden macro on Cygwin. Addresses: https://cygwin.com/ml/cygwin/2016-10/msg00294.html - Fix page count in /proc//statm and /proc//status. Addresses: https://cygwin.com/ml/cygwin-patches/2016-q4/msg8.html - Don't allow sending invalid signals from user space - Fix path handling of ".//" sequences. Addresses: https://cygwin.com/ml/cygwin/2016-11/msg00295.html - cygwin_conv_path/cygwin_create_path now also check for .exe suffix when converting a POSIX path to Windows notation. - Address Windows bug in path conversion on network shares for non-existing paths. Addresses: https://cygwin.com/ml/cygwin-developers/2016-12/msg8.html === Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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: Editors set x-bit (sometimes)
> From: Achim Gratz
> .. the latter is slightly less efficient and you have to
> do -print0/-0, but I tend to get it right more easily then the -exec
> stuff.
Really? I always thought the opposite. With -exec, doesn't
find invoke the command for each single found object? While xargs
allows a single command to operate on a whole slew of objects.
For example:
find ... -exec pgm {} \;
executes pgm separately for each found object while
find ... | xargs pgm
invokes pgm only once for as many files as will fit on the
command line, which is quite a few.
If I'm wrong about this, please share.
Or, perhaps we are talking about commands that only take
a single object. In that case, you would need to say
xargs -n1
in which case, I agree, it is less efficient.
--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
