updated ssh key
Name: Andrew Schulman Package: screen BEGIN SSH2 PUBLIC KEY Comment: "2048-bit RSA, converted from OpenSSH" B3NzaC1yc2EDAQABAAABAQDJHwg85y9fnaw7qYzRF32vmwY2GW5Bwcgc/hOxsG AWrpQJ9wsfFK5yHUmQnTmyyuttXhrOjrGsrUK1vtv59bFdJwsbh/i3jwnajBConXZwo3lU rMBnqn5rXTiG/TM4zX18qPErvuKci4/KvDK6b3LG/byo80PrX7r4u50XVgCIAUsdCKIFSQ kMh4rg/WWesXroFUZVFv3MooYpQ4kxrOgyan/uaVJU9+YYQPYFYYCUQteONzqiUty2Dp1/ JRpbsl9Gukcjy0GVN4bSSm96gtiGcUM6LnzIhD1UvKbvuAtjRGkqTm7OTjHVIV8xRcOtdH OUjN751mQnb7IwJPWfcFuv END SSH2 PUBLIC KEY
Re: urgent help for tool
> On Oct 24, 2018, at 4:05 PM, Hans-Bernhard Bröker wrote: > > A less disruptive approach would be just a) switch this list from > anybody-can-post to subscribers-only, at least for the time being, and > then b) put the FAQ pointers about FAST_CWD prominently into the > auto-reply for non-subscribed users. At the very least this would have > the benefit of not breaking the continuity of the mailing list archives. An even less disruptive approach would be to just auto-reply to the original FAST_CWD message, which is what Corinna has already indicated in this thread that she look into as she has time. -- 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: urgent help for tool
Am 24.10.2018 um 22:49 schrieb Andrey Repin: > Greetings, Stefan Baur! > >> if you can either get hold of the current mailing list's subscriber >> list, to auto-subscribe everyone to a new list, or you are able change >> the current mailinglist's address to, say, cygwin...@cygwin.com, you >> could set up an autoresponder at cygwin@cygwin.com instead. > > That's a long shot, but… given the increased traffic of this noise, it may be > an option. A less disruptive approach would be just a) switch this list from anybody-can-post to subscribers-only, at least for the time being, and then b) put the FAQ pointers about FAST_CWD prominently into the auto-reply for non-subscribed users. At the very least this would have the benefit of not breaking the continuity of the mailing list archives. All this based on two assumptions I cannot vouch for: 1) that ezmlm even has the requisite functionality 2) that totally uncontrolled access to the primry mailing list is not on someone's list of non-negotiable requirements -- 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: erro
Greetings, Lee! > On 10/23/18, Andrey Repin wrote: >> Greetings, Lee! >> https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings >> >>> Except that the faq is wrong in this case: >>> The solution is simply downloading and running Cygwin Setup ... >> >>> The solution for programs that come bundled with cygwin1.dll (like jtr >>> here) is to replace the old cygwin1.dll >> >> Which is unlikely to succeed for such an old version. > Yup - looks like you're right. > I thought I remembered copying the current cygwin1.dll to my jtr > directory when moving to win10 about 1.5 yrs ago. ABI has changed several times since then. Adding to that, rebasing may cause its own load of issues. > But the only john-xxx.zip I can find in my backup that has just cygwin1.dll > & no other cygwin dlls doesn't work on win10 > Sorry for the noise No problem, but please avoid undocumented "solutions", or at least clearly label them as "personal experience, use at your own risk". -- With best regards, Andrey Repin Wednesday, October 24, 2018 23:44:30 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: urgent help for tool
Greetings, Stefan Baur! > if you can either get hold of the current mailing list's subscriber > list, to auto-subscribe everyone to a new list, or you are able change > the current mailinglist's address to, say, cygwin...@cygwin.com, you > could set up an autoresponder at cygwin@cygwin.com instead. That's a long shot, but… given the increased traffic of this noise, it may be an option. > That autoresponder would then point people at the FAQ entry, and also > contain a message that the mailing list has moved to the new address. -- With best regards, Andrey Repin Wednesday, October 24, 2018 23:48:43 Sorry for my terrible english...
Re: erro
On 10/23/18, Andrey Repin wrote: > Greetings, Lee! > >>> https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings > >> Except that the faq is wrong in this case: >> The solution is simply downloading and running Cygwin Setup ... > >> The solution for programs that come bundled with cygwin1.dll (like jtr >> here) is to replace the old cygwin1.dll > > Which is unlikely to succeed for such an old version. Yup - looks like you're right. I thought I remembered copying the current cygwin1.dll to my jtr directory when moving to win10 about 1.5 yrs ago. But the only john-xxx.zip I can find in my backup that has just cygwin1.dll & no other cygwin dlls doesn't work on win10 Sorry for the noise Lee -- 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] gdb-8.1.1-1 (TEST)
The following package has been updated in the Cygwin distribution: * gdb-8.1.1-1 The GNU debugger allows you to debug programs written in C, C++, and other languages, by executing them in a controlled fashion and printing their data. This is an update to a later upstream version: https://sourceware.org/ml/gdb-announce/2018/msg2.html See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes. In addition, it contains the following patches carried forward from the previous Cygwin package: * Teach the demangler to deal with '@'-decorated __stdcall functions * Various fixes for Cygwin signal handling * (experimental) Teach gdb how to unwind frames for the Cygwin signal delivery wrapper functions _sigbe and sigdelayed * Warn rather than stopping with an error if realpath() for a DLL fails (Tim Chick) Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00401.html * Fix a memory leak which would occur in the case when the result of realpath() is greater than or equal to SO_NAME_MAX_PATH_SIZE (Corinna Vinschen) * Fix inferior stopping with SIGTTIN, if it tries to read from the terminal after it has been continued Addresses: https://cygwin.com/ml/cygwin/2016-09/msg00285.html * Workaround https://sourceware.org/bugzilla/show_bug.cgi?id=21078 by linking with shared libstc++ and libgcc. Addresses: https://cygwin.com/ml/cygwin/2017-10/msg00109.html x86: b6b2bcca48a63ff2142b39cfa1ca082732e2130e7f43cf53c35e9a62ff5880ffcceadb038aaf809c2b8b4dc1c5de6c6c81629c81ce6fc5ab3505821ba844339a *gdb-8.1.1-1-src.tar.xz 2b4d91f5ccf740c0165c21d3adf200e71d884f69118292885a5a033da76f23e9738c4fed8383bfc5b57699146b8a5517e0b76d61de74ea3ec65e12631f73d3cc *gdb-8.1.1-1.tar.xz 466d0cbffc4f4fb73b064698e8f7a75608a8726dbe2d7be33e194168c094797c75380c819b87dba7592233af5895cb25f89beaac76e35338ed1ba04403e6b5aa *gdb-debuginfo-8.1.1-1.tar.xz x86_64: ee5df80d5b9f33ce3c0d30ecad517781482f79ab7290d72a2cf3b6d193ab6ef5687c410b9d7ea63e96cd3cae121adeff3855d5b3bf3f7f6f5c7c9df99f84bfef *gdb-8.1.1-1-src.tar.xz 8b1d00b14ba114cd16b25b2688d934b9da922091bd236e2b7cb0196f360eeaad588ae1a092c35ddbab49dad023f9fe5cd55ea51291551afa3490facd45a3d330 *gdb-8.1.1-1.tar.xz 95b5f662918941bcea6bfcf0aaeee0657c05149b34ea45a6ad4194e53dec7e993e5c17e75104802f1ad0e281d4cdc6a4f603b4722a6c84a044c0682946f1b732 *gdb-debuginfo-8.1.1-1.tar.xz -- 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
gdb-8.1.1-1 (TEST)
The following package has been updated in the Cygwin distribution: * gdb-8.1.1-1 The GNU debugger allows you to debug programs written in C, C++, and other languages, by executing them in a controlled fashion and printing their data. This is an update to a later upstream version: https://sourceware.org/ml/gdb-announce/2018/msg2.html See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes. In addition, it contains the following patches carried forward from the previous Cygwin package: * Teach the demangler to deal with '@'-decorated __stdcall functions * Various fixes for Cygwin signal handling * (experimental) Teach gdb how to unwind frames for the Cygwin signal delivery wrapper functions _sigbe and sigdelayed * Warn rather than stopping with an error if realpath() for a DLL fails (Tim Chick) Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00401.html * Fix a memory leak which would occur in the case when the result of realpath() is greater than or equal to SO_NAME_MAX_PATH_SIZE (Corinna Vinschen) * Fix inferior stopping with SIGTTIN, if it tries to read from the terminal after it has been continued Addresses: https://cygwin.com/ml/cygwin/2016-09/msg00285.html * Workaround https://sourceware.org/bugzilla/show_bug.cgi?id=21078 by linking with shared libstc++ and libgcc. Addresses: https://cygwin.com/ml/cygwin/2017-10/msg00109.html x86: b6b2bcca48a63ff2142b39cfa1ca082732e2130e7f43cf53c35e9a62ff5880ffcceadb038aaf809c2b8b4dc1c5de6c6c81629c81ce6fc5ab3505821ba844339a *gdb-8.1.1-1-src.tar.xz 2b4d91f5ccf740c0165c21d3adf200e71d884f69118292885a5a033da76f23e9738c4fed8383bfc5b57699146b8a5517e0b76d61de74ea3ec65e12631f73d3cc *gdb-8.1.1-1.tar.xz 466d0cbffc4f4fb73b064698e8f7a75608a8726dbe2d7be33e194168c094797c75380c819b87dba7592233af5895cb25f89beaac76e35338ed1ba04403e6b5aa *gdb-debuginfo-8.1.1-1.tar.xz x86_64: ee5df80d5b9f33ce3c0d30ecad517781482f79ab7290d72a2cf3b6d193ab6ef5687c410b9d7ea63e96cd3cae121adeff3855d5b3bf3f7f6f5c7c9df99f84bfef *gdb-8.1.1-1-src.tar.xz 8b1d00b14ba114cd16b25b2688d934b9da922091bd236e2b7cb0196f360eeaad588ae1a092c35ddbab49dad023f9fe5cd55ea51291551afa3490facd45a3d330 *gdb-8.1.1-1.tar.xz 95b5f662918941bcea6bfcf0aaeee0657c05149b34ea45a6ad4194e53dec7e993e5c17e75104802f1ad0e281d4cdc6a4f603b4722a6c84a044c0682946f1b732 *gdb-debuginfo-8.1.1-1.tar.xz
Re: [ANNOUNCEMENT] gdb-8.0.1-1 (TEST)
On 14/07/2018 13:38, Jon Turney wrote: The following package has been updated in the Cygwin distribution: * gdb-8.0.1-1 The GNU debugger allows you to debug programs written in C, C++, and other languages, by executing them in a controlled fashion and printing their data. This is an update to a later upstream version: https://sourceware.org/ml/gdb-announce/2017/msg4.html See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes. This package has been promoted from test to current. -- 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] icu 63.1-1
On 10/22/2018 11:01 AM, Stefan Weil wrote: > Am 22.10.2018 um 16:04 schrieb Ken Brown: >> The following packages have been uploaded to the Cygwin distribution: >> >> * libicu63-63.1-1 >> * libicu-devel-63.1-1 >> * icu-doc-63.1-1 >> > > What about mingw64-x86_64-icu and mingw64-i686-icu? Will they get an > update, too? Currently they are still at 57.1-2. Sorry, but I can only point you to my previous answer: http://www.cygwin.org/ml/cygwin/2018-06/msg00255.html I suspect that Yaakov is just busy with other things. Are you willing to take over as maintainer of those packages (assuming that Yaakov is willing to give them up)? If so, an email to the cygwin-apps mailing list offering to do that would be appropriate. Ken
Re: WARNING: Couldn't compute FAST_CWD pointer
On 10/24/2018 10:41 AM, john doe wrote: > On 10/24/2018 4:36 PM, Stephen John Smoogen wrote: >> On Wed, 24 Oct 2018 at 10:32, Ng Wai Kin wrote: >>> >>> Windows 10. >> >> That is not enough information to help anyone here. What software is >> showing this and what is the course you are using it in. The problem >> is that the software needs to be updated and recompiled to work with >> newer Cygwin versions, and whoever is the provider did not change the >> error message to say contact them versus this list. >> > > See also the below URL or the archive of this mailing list:: > > https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings > Including the OP in the distribution. -- 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: WARNING: Couldn't compute FAST_CWD pointer
On 10/24/2018 4:36 PM, Stephen John Smoogen wrote: > On Wed, 24 Oct 2018 at 10:32, Ng Wai Kin wrote: >> >> Windows 10. > > That is not enough information to help anyone here. What software is > showing this and what is the course you are using it in. The problem > is that the software needs to be updated and recompiled to work with > newer Cygwin versions, and whoever is the provider did not change the > error message to say contact them versus this list. > See also the below URL or the archive of this mailing list:: https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings -- John Doe -- 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: urgent help for tool
Am 23.10.18 um 09:55 schrieb Corinna Vinschen: >> It doesn't help for the old versions of cygwin that are being >> reported. That's why they're getting that message—because it's an old >> version. They're not spamming, they're doing exactly what the message >> told them to do. The message was unfortunate from the get-go. > Indeed. It seemd like a good idea at the time... > >> Now that has come up yet again, I do wonder if the mailing list >> software could somehow trap an unquoted FAST_CWD message and just >> reply with a message that includes a link to the FAQ entry, rather >> than send the message onto the list. Probably more trouble than it's >> worth. > We're just users of the sourceware infrastructure. What we could try > by ourselves is to create an automated reply. The mail and the > automated reply would still hit the mailing list, but nobody would > have to bother to reply anymore. This could even be a simple > procmail filter. I'll look into it (but will need time). Now this may be a nasty hack, bt ... if you can either get hold of the current mailing list's subscriber list, to auto-subscribe everyone to a new list, or you are able change the current mailinglist's address to, say, cygwin...@cygwin.com, you could set up an autoresponder at cygwin@cygwin.com instead. That autoresponder would then point people at the FAQ entry, and also contain a message that the mailing list has moved to the new address. Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 signature.asc Description: OpenPGP digital signature
Re: WARNING: Couldn't compute FAST_CWD pointer
On Wed, 24 Oct 2018 at 10:32, Ng Wai Kin wrote: > > Windows 10. That is not enough information to help anyone here. What software is showing this and what is the course you are using it in. The problem is that the software needs to be updated and recompiled to work with newer Cygwin versions, and whoever is the provider did not change the error message to say contact them versus this list. > > -- > 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 > -- Stephen J Smoogen. -- 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
WARNING: Couldn't compute FAST_CWD pointer
Windows 10. -- 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: erro
On 10/23/2018 1:17 PM, Andrey Repin wrote: > Greetings, Lee! > >>> https://cygwin.com/faq/faq.html#faq.using.fixing-find_fast_cwd-warnings > >> Except that the faq is wrong in this case: >> The solution is simply downloading and running Cygwin Setup ... > >> The solution for programs that come bundled with cygwin1.dll (like jtr >> here) is to replace the old cygwin1.dll > > Which is unlikely to succeed for such an old version. Andrey, it's been cygwin1.dll since Version 1.0 which indicates that every version has been backward compatible API. Replacing only cygwin1.dll shouldn't be a problem. The problem comes from if the software dependent on cygwin1.dll also has changes required for newer versions of Windows. -- 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
