RE: [ITP] onc-rpc-devel-2.19_20140211-1
Hello! NAME=onc-rpc-devel VERSION=2.19_20140211 RELEASE=1 CATEGORY=Devel # for instance SUMMARY=This is the sdesc text for setup.hint DESCRIPTION=This is the ldesc text for setup.hint The setup.hint file will get auto-generated then, you don't have to maintain it outside the cygport file. I have just tried to do this, but here is what i get from cygport onc-rpc-devel.cygport package': --- cut --- /usr/lib/ruby/1.9.1/optparse.rb:214:in `gm': time out of range (ArgumentError) from /usr/lib/ruby/1.9.1/optparse.rb:214:in `class:OptionParser' from /usr/lib/ruby/1.9.1/optparse.rb:210:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/command.rb:7:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/command_manager.rb:7:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/gem_runner.rb:8:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/bin/gem:9:in `main' onc-rpc-devel requires: libintl8 --- cut --- And in 'dist' subdirectory nothing is created. Looks like there's some problem with Ruby. Can anybody help ? Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia
Re: [ITP] onc-rpc-devel-2.19_20140211-1
On 14/08/2014 08:11, Pavel Fedin wrote: Hello! NAME=onc-rpc-devel VERSION=2.19_20140211 RELEASE=1 CATEGORY=Devel # for instance SUMMARY=This is the sdesc text for setup.hint DESCRIPTION=This is the ldesc text for setup.hint The setup.hint file will get auto-generated then, you don't have to maintain it outside the cygport file. I have just tried to do this, but here is what i get from cygport onc-rpc-devel.cygport package': --- cut --- /usr/lib/ruby/1.9.1/optparse.rb:214:in `gm': time out of range (ArgumentError) from /usr/lib/ruby/1.9.1/optparse.rb:214:in `class:OptionParser' from /usr/lib/ruby/1.9.1/optparse.rb:210:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/command.rb:7:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/command_manager.rb:7:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/gem_runner.rb:8:in `top (required)' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /usr/bin/gem:9:in `main' onc-rpc-devel requires: libintl8 --- cut --- And in 'dist' subdirectory nothing is created. Looks like there's some problem with Ruby. Can anybody help ? Kind regards, Pavel Fedin Hi Pavel, can you share the onc-rpc-devel.cygport ? I assume you already have the inherit ruby command in it, correct ? Regards Marco
RE: [ITP] onc-rpc-devel-2.19_20140211-1
Hello! I have worked around the problem with Ruby gem just by renaming 'gem' script. Looks like gem is broken on Cygwin. I have updated my Dropbox folder, and here is forgotten setup.hint. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia setup.hint Description: Binary data
RE: [ITP] onc-rpc-devel-2.19_20140211-1
Hello! can you share the onc-rpc-devel.cygport ? I assume you already have the inherit ruby command in it, correct ? No, i don't. Here it is. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia onc-rpc-devel.cygport Description: Binary data
Re: [ITP] onc-rpc-devel-2.19_20140211-1
Hi Pavel, On Aug 14 10:54, Pavel Fedin wrote: Hello! I have worked around the problem with Ruby gem just by renaming 'gem' script. Looks like gem is broken on Cygwin. I have updated my Dropbox folder, and here is forgotten setup.hint. Your build has a tiny problem: rpcgen -C -h rpcsvc/bootparam_prot.x -o rpcsvc/bootparam_prot.h make: rpcgen: Command not found The Makefile apparently expects that rpcgen can be found in $PATH, but . is not part of $PATH by default. Your Makefile should call rpcgen with prefix as in ./rpcgen to work reliably. Care to fix this before uploading? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpJQuCgwGp5_.pgp Description: PGP signature
Re: [ITP] onc-rpc-devel-2.19_20140211-1
On Aug 14 11:26, Corinna Vinschen wrote: Hi Pavel, On Aug 14 10:54, Pavel Fedin wrote: Hello! I have worked around the problem with Ruby gem just by renaming 'gem' script. Looks like gem is broken on Cygwin. I have updated my Dropbox folder, and here is forgotten setup.hint. Your build has a tiny problem: rpcgen -C -h rpcsvc/bootparam_prot.x -o rpcsvc/bootparam_prot.h make: rpcgen: Command not found The Makefile apparently expects that rpcgen can be found in $PATH, but . is not part of $PATH by default. Your Makefile should call rpcgen with prefix as in ./rpcgen to work reliably. Care to fix this before uploading? Btw., after fixing this locally, the full build including installation and packaging worked fine. No problems with gem. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpX6KAVJQ8qr.pgp Description: PGP signature
Re: [ITP] onc-rpc-devel-2.19_20140211-1
On Aug 14 15:06, Pavel Fedin wrote: Hello! Your build has a tiny problem: rpcgen -C -h rpcsvc/bootparam_prot.x -o rpcsvc/bootparam_prot.h make: rpcgen: Command not found The Makefile apparently expects that rpcgen can be found in $PATH, Thank you, fixed. Now it just calls ./rpcgen, which is just built. Btw., after fixing this locally, the full build including installation and packaging worked fine. No problems with gem. Perhaps you don't have Ruby and gem installed ? These are optional, and cygport behaves correctly if there's no gem. I have learned on the Internet that gem is a package manager for Ruby. On my system simply running it produces the same result. Perhaps some problem with Ruby. No, I have ruby and gem installed. Works still fine for me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpK_t2iIZe_l.pgp Description: PGP signature
RE: [ITP] onc-rpc-devel-2.19_20140211-1
Hello! No, I have ruby and gem installed. Works still fine for me. Just installed i386 version of Ruby, indeed works fine. Perhaps this happens because i use older cygwin1.dll. If you remember, i reported about memory trashing with newer DLL, but nobody could reproduce it, and i could not find time to fix it. Kind regards, Pavel Fedin Expert Engineer Samsung Electronics Research center Russia
Re: cygwin-pkg-maint maintance [gold star]
On 2014-08-11 17:03, Marco Atzeri wrote: attached 2 files. The first is basically what should be the new cygwin-pkg-maint that cover all the active package in both 32bit and 64 bit. This was great, thank you. After rearranging the release areas, I was able to get a more reliable list of what is currently on the server, and made a few more tweaks. All packages are reported as lower case. That always annoyed be about this list, so I did change the list to use proper case. The second one is the list of packages reported in the current file that do not exist as package or source package. We don't need those, so they're all gone, as well as those packages which are now nothing more than upgrade helpers. Could you check the latest cygwin-pkg-maint and see if I missed anything? Andrew: could you polish a gold star for Marco for showing initiative wrt Cygwin infrastructure at this juncture? Awarded! http://cygwin.com/goldstars/#MA
Re: [ITP] onc-rpc-devel-2.19_20140211-1
On Thu, 2014-08-14 at 18:35 +0400, Pavel Fedin wrote: No, I have ruby and gem installed. Works still fine for me. Just installed i386 version of Ruby, indeed works fine. The Cygwin gem command itself is working just fine. Are you, or were you, trying to use a Windows version of ruby, or did you have such first in your PATH? That wouldn't work. Yaakov
Re: cygwin-pkg-maint maintance
Yaakov Selkowitz writes: […] Yes, these are obvious fixes. […] I've looked at the file today. It seems that perl_vendor has been removed, but not all Perl distributions that were bundled are listed. I'll prepare a list of those over the weekend. Given the purpose of the file and that it's meant to be consumed by scripts, how about switching to something more easily parseable like JSON or YAML (much like Perl does)? That would enable to incorporate more meta-information for each package which could easily be generated by cygport. 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
Re: cygwin-pkg-maint maintance
On Thu, 2014-08-14 at 19:55 +0200, Achim Gratz wrote: I've looked at the file today. It seems that perl_vendor has been removed, but not all Perl distributions that were bundled are listed. I'll prepare a list of those over the weekend. perl_vendor was a subpackage of the perl source package (it does not have its own -src), so this is correct. All perl-* packages currently in either arch should be listed; if not, PTC. As for whatever other perl module packages that need to be added in order to replace perl_vendor, those will be added when we have an approved update or ITA for them. Given the purpose of the file and that it's meant to be consumed by scripts, how about switching to something more easily parseable like JSON or YAML (much like Perl does)? That would enable to incorporate more meta-information for each package which could easily be generated by cygport. This is a package ownership database, not a package information database. What additional information do you think would be useful here? Yaakov
[ITA] Procmail 3.22
Hi group, I intend to adopt the Cygwin package for the procmail program, version 3.22. The original maintainer, Jason Tishler has given me permission to do so. The difference with previous Cygwin releases is that the procmail program has been made 'multiple root' aware and suid/guid, provided that it is started by a privileged user. This was needed to make procmail work together with Sendmail, which I intend to package (see next post). sdesc: Mail processing program ldesc: The procmail program is used by Red Hat Linux for all local mail delivery. In addition to just delivering mail, procmail can be used for automatic filtering, presorting, and other mail handling jobs. Procmail is also the basis for the SmartList mailing list processor. category: Mail requires: bash cygwin version: 3.22-11 http://cygwin.boland.nl/x86/release/procmail/ Note: after making from source, use 'make install-suid' and make install.man to install. All GTG's are welcome. Cheers, Daniel
[ITP] Sendmail 8.14.9
Hi group, I intend to package the Cygwin version of Sendmail, version 8.14.9. sdesc: The Mail Transfer Agent ldesc: General purpose internetwork email routing facility that supports many kinds of mail-transfer and delivery methods, including SMTP, SMTPS (STARTTLS), SMTPA (AUTH) used for email transport over the internet. category: Mail requires: m4 procmail tcp_wrappers cyrus-sasl cygrunsrv cygwin version: 18.14.9-0 http://cygwin.boland.nl/x86/release/sendmail/ All GTG's are welcome. Cheers, Daniel
Re: [ITP] onc-rpc-devel-2.19_20140211-1
Hello! I have uploaded the package. Hopefully i've done everything right, and it will appear on the list. If so, what should i do in order to tell that it supersedes rpcgen ? IIRC something has to be done manually ? Or should i upload -rpcgen* file ? -- Kind regards, Pavel
Re: cygwin-pkg-maint maintance
Yaakov Selkowitz writes: This is a package ownership database, not a package information database. What additional information do you think would be useful here? Whether the package is available for both architectures and if it's already converted to cygport for instance. From that database the current file can easily be created if necessary and any manual changes to the file could bootstrap a new entry in the database (so the new maintainer can upload). 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
Re: [ITP] Sendmail 8.14.9
On Aug 14 21:05, D. Boland wrote: Hi group, I intend to package the Cygwin version of Sendmail, version 8.14.9. sdesc: The Mail Transfer Agent ldesc: General purpose internetwork email routing facility that supports many kinds of mail-transfer and delivery methods, including SMTP, SMTPS (STARTTLS), SMTPA (AUTH) used for email transport over the internet. category: Mail requires: m4 procmail tcp_wrappers cyrus-sasl cygrunsrv cygwin version: 18.14.9-0 http://cygwin.boland.nl/x86/release/sendmail/ Same as with procmail. There's no version tag and the package should be using cygport packaging. This also makes sure that the setup.hint file will be crated correctly, btw., since that's automatic then. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp7Rri7YcCbi.pgp Description: PGP signature
Re: cygwin-pkg-maint maintance
On 14/08/2014 21:21, Achim Gratz wrote: Yaakov Selkowitz writes: This is a package ownership database, not a package information database. What additional information do you think would be useful here? Whether the package is available for both architectures Wrong expectation. It is in both architectures if it appears in both setup.ini; any other solution will create duplicated information that finally need alignment and it is error prone. I plan to produce a list of sources by arch as by product of the current analysis. Please note that the two trees are not exactly equal so there are packages available only in 64 and not in 32bit (biber is the first in alphabetical order) and if it's already converted to cygport for instance. From that database the current file can easily be created if necessary and any manual changes to the file could bootstrap a new entry in the database (so the new maintainer can upload). The build methods is maintainer choice. I use cygport but I don't see a reason to mandate it. I do not follow the rest of your statement, could you clarify the expected outcome ? Regards, Achim. Regards Marco
Re: cygwin-pkg-maint maintance
Marco Atzeri writes: Whether the package is available for both architectures Wrong expectation. So what? I get how things are right now, that doesn't mean it has to stay forever that way. It is in both architectures if it appears in both setup.ini; any other solution will create duplicated information that finally need alignment and it is error prone. Ultimately the need for this file sholud go away except for bootstrapping a new maintainer. I plan to produce a list of sources by arch as by product of the current analysis. Please note that the two trees are not exactly equal so there are packages available only in 64 and not in 32bit (biber is the first in alphabetical order) I know, I've done similar analysis before (in Perl, if that matters). The build methods is maintainer choice. I use cygport but I don't see a reason to mandate it. Corinna has already motioned in that direction and I'd say it makes good sense to converge onto a single package building method. That's the only way to ever get an automatic build off the ground. If and when that happens the only thing a maintainer has to do is upload a new cygport file and check the build logs before release. I do not follow the rest of your statement, could you clarify the expected outcome ? Long term: You enter a new maintainer manually and when the package is finally uploaded an extended setup.hint provides all the information that goes into the package database to fill the temporary blanks. And with a little bit of extra effort each package could eben be checked for (formal) correctness. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: cygwin-pkg-maint maintance
On Aug 14 22:28, Marco Atzeri wrote: On 14/08/2014 21:21, Achim Gratz wrote: Yaakov Selkowitz writes: This is a package ownership database, not a package information database. What additional information do you think would be useful here? Whether the package is available for both architectures Wrong expectation. It is in both architectures if it appears in both setup.ini; any other solution will create duplicated information that finally need alignment and it is error prone. I plan to produce a list of sources by arch as by product of the current analysis. Please note that the two trees are not exactly equal so there are packages available only in 64 and not in 32bit (biber is the first in alphabetical order) and if it's already converted to cygport for instance. From that database the current file can easily be created if necessary and any manual changes to the file could bootstrap a new entry in the database (so the new maintainer can upload). The build methods is maintainer choice. I use cygport but I don't see a reason to mandate it. Tiny correction: New packages should use cygport. We should really all use the same packaging system. After all, you don't use rpm files on Debian or dpkg files on Fedora. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpG6pvXUg72v.pgp Description: PGP signature
Re: cygwin-pkg-maint maintance
On 14/08/2014 22:51, Corinna Vinschen wrote: On Aug 14 22:28, Marco Atzeri wrote: The build methods is maintainer choice. I use cygport but I don't see a reason to mandate it. Tiny correction: New packages should use cygport. We should really all use the same packaging system. After all, you don't use rpm files on Debian or dpkg files on Fedora. should is not must. ;-) Of course it is the preferred and major way and the alternatives are not so efficient. Corinna Marco
Re: [ITP] onc-rpc-devel-2.19_20140211-1
On Thu, 2014-08-14 at 23:14 +0400, Pavel Fedin wrote: I have uploaded the package. Hopefully i've done everything right, and it will appear on the list. If so, what should i do in order to tell that it supersedes rpcgen ? IIRC something has to be done manually ? Or should i upload -rpcgen* file ? Add the following line to your onc-rpc-devel.cygport: OBSOLETES=rpcgen This will add a dummy rpcgen subpackage and a special setup.hint which will cause users with rpcgen installed to be automatically upgraded to onc-rpc-devel. HTH, Yaakov
Re: [ITA] Git et al
On 08/13/2014 01:37 PM, Eric Blake wrote: The packages and setup.hint files are all ready to use and/or upload from http://tastycake.net/~adam/cygwin/. Before I can go ahead and release, I think I need to be added to cygwin-pkg-maint so I can send in an SSH key, and I possibly need a GTG from another maintainer. I'll look over your latest packaging, and if it works for me (aka builds fine, and lets me do a git checkout of some of my usual repos), I'll update cygwin-pkg-maint to list you as maintainer and reply back. It may be this weekend before I actually get the time to spend on it, though. Packaging isn't quite right. After unpacking the -src tarball, I see a file git-2.0.4-1.src.patch, with contents: Binary files origsrc/git/t/lib-gpg/random_seed and src/git/t/lib-gpg/random_seed differ Binary files origsrc/git/t/lib-gpg/trustdb.gpg and src/git/t/lib-gpg/trustdb.gpg differ As a result, the prep phase fails with: *** ERROR: patch git-2.0.4-1.src.patch will not apply It's probably possible to patch git.cygport to cause the diff engine to ignore these files, and once they are ignored, then the file would not be created. Removing that file lets cygport get further, but you'll need to respin the package so that it builds the first time without me having to delete the file. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: [ITA] Git et al
On 15/08/2014 06:24, Eric Blake wrote: On 08/13/2014 01:37 PM, Eric Blake wrote: Packaging isn't quite right. After unpacking the -src tarball, I see a file git-2.0.4-1.src.patch, with contents: Binary files origsrc/git/t/lib-gpg/random_seed and src/git/t/lib-gpg/random_seed differ Binary files origsrc/git/t/lib-gpg/trustdb.gpg and src/git/t/lib-gpg/trustdb.gpg differ As a result, the prep phase fails with: *** ERROR: patch git-2.0.4-1.src.patch will not apply It's probably possible to patch git.cygport to cause the diff engine to ignore these files, and once they are ignored, then the file would not be created. Adam, just add DIFF_EXCLUDES=random_seed trustdb.gpg Removing that file lets cygport get further, but you'll need to respin the package so that it builds the first time without me having to delete the file. Marco
[ANNOUNCEMENT] Various X.Org updates
The following packages have been added in the Cygwin distribution: * fontsproto-2.1.3-1 * gccmakedep-1.0.3-1 * imake-1.0.7-1 * inputproto-2.3.1-1 * libICE-1.0.9-1 * libXaw-1.0.12-2 * libXaw3d-1.6.2-2 * libXext-1.3.3-1 * libXfont-1.5.0-1 * libXft-2.3.2-1 * libXi-1.7.4-1 * libXt-1.1.4-2 * libxkbcommon-0.4.2-1 * mesa-10.2.5-1 * motif-2.3.4-2 * xauth-1.0.9-1 * xcb-util-cursor-0.1.1-1 * xcb-util-renderutil-0.3.9-1 * xcb-util-wm-0.4.1-1 * xcursorgen-1.0.6-1 * xfs-1.1.3-20140603-1 * xkeyboard-config-2.12-1 * xorg-util-macros-1.19.0-1 * xproto-7.0.26-1 * xrandr-1.4.3-1 * xtrans-1.3.4-1 This batch of updates consists mostly of bugfixes and some new features required by the upcoming xorg-server 1.16 release. The issue on x86_64 where Xaw/Motif apps would not work depending on where they were rebased should now be fixed. -- Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO == If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
src/winsup/cygwin malloc.cc ChangeLog dlmalloc ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-08-14 17:36:24 Modified files: winsup/cygwin : malloc.cc ChangeLog Removed files: winsup/cygwin : dlmalloc.c dlmalloc.h Log message: * dlmalloc.c: Remove unused file. * dlmalloc.h: Ditto. * malloc.cc: Update to Doug Lea's malloc version 2.8.6. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/malloc.cc.diff?cvsroot=srcr1=1.11r2=1.12 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.6487r2=1.6488 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dlmalloc.c.diff?cvsroot=srcr1=1.9r2=NONE http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dlmalloc.h.diff?cvsroot=srcr1=1.4r2=NONE
src/winsup/cygwin ChangeLog posix.sgml path.sgml
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-08-14 19:31:33 Modified files: winsup/cygwin : ChangeLog Removed files: winsup/cygwin : posix.sgml path.sgml Log message: * path.sgml: Move to ../doc dir and rename to path.xml. * posix.sgml: Move to ../doc dir and rename to posix.xml. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.6488r2=1.6489 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/posix.sgml.diff?cvsroot=srcr1=1.87r2=NONE http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/path.sgml.diff?cvsroot=srcr1=1.11r2=NONE
src/winsup/utils ChangeLog utils.xml
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-08-14 19:33:57 Modified files: winsup/utils : ChangeLog Removed files: winsup/utils : utils.xml Log message: * utils.xml: Move to ../doc. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/utils/ChangeLog.diff?cvsroot=srcr1=1.629r2=1.630 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/utils/utils.xml.diff?cvsroot=srcr1=1.6r2=NONE
src/winsup/doc ChangeLog Makefile.in faq-progr ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-08-14 19:44:29 Modified files: winsup/doc : ChangeLog Makefile.in faq-programming.xml using.xml Added files: winsup/doc : cygwin-api.xml path.xml posix.xml utils.xml Removed files: winsup/doc : cygwin-api.in.xml doctool.c doctool.txt Log message: * Makefile.in: Throughout use parenthesis instead of braces where appropriate. (DBXDIRS): Remove. (XSLTPROC): Define for symmetry. Use throughout. (clean): Drop removing cygwin-api.xml and doctool.*. (cygwin-api.xml): Drop rule. (doctool): Drop rule. (Makefile.dep): Add dependency to cygwin-api.xml. * cygwin-api.in.xml: Rename to cygwin-api.xml. Convert includes to XML XInclude style. * doctool.c: Remove. * doctool.txt: Remove. * faq-programming.xml: Drop reference to local utils.xml file. * path.xml: Moved from ../cygwin and converted to XML. * posix.xml: Ditto. * using.xml: Drop relative path from utils.xml include. * utils.xml: Moved from ../utils. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/cygwin-api.xml.diff?cvsroot=srcr1=NONEr2=1.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/path.xml.diff?cvsroot=srcr1=NONEr2=1.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/posix.xml.diff?cvsroot=srcr1=NONEr2=1.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/utils.xml.diff?cvsroot=srcr1=NONEr2=1.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/ChangeLog.diff?cvsroot=srcr1=1.483r2=1.484 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/Makefile.in.diff?cvsroot=srcr1=1.36r2=1.37 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/faq-programming.xml.diff?cvsroot=srcr1=1.29r2=1.30 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/using.xml.diff?cvsroot=srcr1=1.1r2=1.2 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/cygwin-api.in.xml.diff?cvsroot=srcr1=1.2r2=NONE http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/doctool.c.diff?cvsroot=srcr1=1.3r2=NONE http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/doctool.txt.diff?cvsroot=srcr1=1.1.1.1r2=NONE
src/winsup/cygwin ChangeLog security.sgml
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-08-14 20:12:50 Modified files: winsup/cygwin : ChangeLog Removed files: winsup/cygwin : security.sgml Log message: * security.sgml: Move to ../doc dir and rename to logon-funcs.xml. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.6489r2=1.6490 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/security.sgml.diff?cvsroot=srcr1=1.1r2=NONE
src/winsup/doc ChangeLog cygwin-api.xml path.x ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-08-14 20:15:49 Modified files: winsup/doc : ChangeLog cygwin-api.xml path.xml Added files: winsup/doc : logon-funcs.xml Log message: * cygwin-api.xml: Move chapter tags from path.xml back here. Include logon-funcs.xml. * logon-funcs.xml: Moved from ../cygwin here and converted to XML. * path.xml: Drop chapter tags. Create subsections. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/logon-funcs.xml.diff?cvsroot=srcr1=NONEr2=1.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/ChangeLog.diff?cvsroot=srcr1=1.484r2=1.485 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/cygwin-api.xml.diff?cvsroot=srcr1=1.1r2=1.2 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/path.xml.diff?cvsroot=srcr1=1.1r2=1.2
src/winsup/cygwin ChangeLog dll_init.sgml dtab ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-08-14 20:46:29 Modified files: winsup/cygwin : ChangeLog Removed files: winsup/cygwin : dll_init.sgml dtable.sgml external.sgml stackdump.sgml Log message: * dll_init.sgml: Remove. * dtable.sgml: Move into ../doc/misc-funcs.xml. * external.sgml: Ditto. * stackdump.sgml: Ditto. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.6490r2=1.6491 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dll_init.sgml.diff?cvsroot=srcr1=1.5r2=NONE http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dtable.sgml.diff?cvsroot=srcr1=1.5r2=NONE http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/external.sgml.diff?cvsroot=srcr1=1.6r2=NONE http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/stackdump.sgml.diff?cvsroot=srcr1=1.5r2=NONE
src/winsup/doc ChangeLog cygwin-api.xml misc-f ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-08-14 20:47:14 Modified files: winsup/doc : ChangeLog cygwin-api.xml Added files: winsup/doc : misc-funcs.xml Log message: * cygwin-api.xml: Include misc-funcs.xml. * misc-funcs.xml: New file. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/misc-funcs.xml.diff?cvsroot=srcr1=NONEr2=1.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/ChangeLog.diff?cvsroot=srcr1=1.485r2=1.486 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/cygwin-api.xml.diff?cvsroot=srcr1=1.2r2=1.3
sshd default user PATH
I'm trying to figure out how sshd comes up with the PATH for the initial environment. Currently I get the Windows sytem PATH (converted to POSIX) and then /bin appended. This is no good, at least /bin should be at the beginning of that PATH. I've not been able to change this system-wide so far. Apparently sshd has been built on a machine where /etc/default/login wasn't present, at least it doesn't appear to try to read that file (or any other system file) for setting up the initial environment. The /etc/sshrc is run if I create it, but you can't set any environment variables from within it. I don't want to enable user environments. I think it would be nice if there was a system file that could set the initial environment for sshd, maybe setting external_path_file to /etc/ssh_environment fits in better with the default Cygwin /etc layout, though. Regards, Achim. -- 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] New package: rng-tools-5-1
On 2014-08-13 11:43, Corinna Vinschen wrote: On Aug 13 10:55, Peter Rosin wrote: This seemed like something I could waste a little time on, and learn something in the process. Which I did, so not all is lost. :-) Ok, I see how the above could be misread easily, since it appeared in the context it did. But the key to interpreting it is that it is all past tense; it was meant as a comment to the whole thread. Cool! I'm glad for any help, you know. If you want to take over the rng-tools package to play further with it, feel free. I'll look into the fake entropy pool size in a not so distant future. What I'm saying is that I have no further input. Sorry. Figuring out how to write device drivers or otherwise access the PCI bus is not something I have done previously (not for any current Windows version anyway), and it feels too much like a black hole regarding time. So, again, sorry if that's disappointing. That said, I could still adopt the rng-tools package if that would be any help (but I don't see myself hacking on any new HW features) Cheers, Peter -- 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] Updated: Cygwin 1.7.32-1
Hi Cygwin friends and users, I just released Cygwin 1.7.32-1. This release comes with a few bug fixes in header files and a slightly improved /proc/cpuinfo output, but otherwise it concentrates on a new feature which isn't readily user visible. The new feature requires a new GCC which will be released by Jon_Y shorty. This combination, cygwin 1.7.32 / gcc 4.8.3-3, also allows to handle C++11 thread local objects for the first time. What's new: --- - Export __cxa_atexit and __cxa_finalize to allow C++ standards-compliant destructor handling in libstdc++ and g++ compiled code. Please note that, in order to benefit from this new feature, C++ code must be recompiled with the upcoming gcc 4.8.3-3 release which will enable the -fuse-cxa-atexit flag by default, and that C++ applications using this feature will not run on older Cygwin releases. - Support more recent CPU flags in /proc/cpuinfo. Bug Fixes - - Decorate attribute names with __, for namespace safety in various header files. Addresses: https://cygwin.com/ml/cygwin/2014-07/msg00371.html - Fix sys/file.h for using in C++ code. Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00122.html To install 32-bit Cygwin use http://cygwin.com/setup-x86.exe To install 64 bit Cygwin use http://cygwin.com/setup-x86_64.exe The 64 bit Cygwin distribution doesn't yet come with as many packages as the 32 bit version, but more packages will be available over time. If you're already running a 32 bit version of Cygwin on 64 bit Windows machines, you can continue to do so. If you're planning a new install of Cygwin on a 64 bit Windows machine, consider to use the new 64 bit Cygwin version, unless you need certain packages not yet available in the 64 bit release. Have fun, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader 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: [ANNOUNCEMENT] Updated: Cygwin 1.7.32-1
Corinna Vinschen wrote on 2014/8/14 18:27: Hi Cygwin friends and users, I just released Cygwin 1.7.32-1. This release comes with a few bug fixes in header files and a slightly improved /proc/cpuinfo output, but otherwise it concentrates on a new feature which isn't readily user visible. The new feature requires a new GCC which will be released by Jon_Y shorty. This combination, cygwin 1.7.32 / gcc 4.8.3-3, also allows to handle C++11 thread local objects for the first time. What's new: --- - Export __cxa_atexit and __cxa_finalize to allow C++ standards-compliant destructor handling in libstdc++ and g++ compiled code. Please note that, in order to benefit from this new feature, C++ code must be recompiled with the upcoming gcc 4.8.3-3 release which will enable the -fuse-cxa-atexit flag by default, and that C++ applications using this feature will not run on older Cygwin releases. - Support more recent CPU flags in /proc/cpuinfo. Bug Fixes - - Decorate attribute names with __, for namespace safety in various header files. Addresses: https://cygwin.com/ml/cygwin/2014-07/msg00371.html - Fix sys/file.h for using in C++ code. Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00122.html To install 32-bit Cygwin use http://cygwin.com/setup-x86.exe To install 64 bit Cygwin use http://cygwin.com/setup-x86_64.exe The 64 bit Cygwin distribution doesn't yet come with as many packages as the 32 bit version, but more packages will be available over time. If you're already running a 32 bit version of Cygwin on 64 bit Windows machines, you can continue to do so. If you're planning a new install of Cygwin on a 64 bit Windows machine, consider to use the new 64 bit Cygwin version, unless you need certain packages not yet available in the 64 bit release. Have fun, Corinna Hi Corinna, Would you kindly test the usage of repo in Cygwin if CYGWIN=winsymlinks:nativestrict? Regards Robert -- 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: sshd default user PATH
On Aug 14 09:56, Achim Gratz wrote: I'm trying to figure out how sshd comes up with the PATH for the initial environment. Currently I get the Windows sytem PATH (converted to POSIX) and then /bin appended. This is no good, at least /bin should be at the beginning of that PATH. On other systems sshd sets $PATH to /usr/bin:/bin:/usr/sbin:/sbin, but on Cygwin it doesn't change $PATH and just takes what it got from cygrunsrv so as not to break the search path for DLLs not in the system directories. So this is kind of a cygrunsrv problem. It simply appends /bin to $PATH, rather than prepending it. I've not been able to change this system-wide so far. Apparently sshd has been built on a machine where /etc/default/login wasn't present, at least it doesn't appear to try to read that file (or any other system file) for setting up the initial environment. Right, /etc/default/login and, fwiw, any method to change $PATH from the default path is disabled on Cygwin deliberately for the reason outlined above. The /etc/sshrc is run if I create it, but you can't set any environment variables from within it. I don't want to enable user environments. I think it would be nice if there was a system file that could set the initial environment for sshd, maybe setting external_path_file to /etc/ssh_environment fits in better with the default Cygwin /etc layout, though. It's not that simple. It requires a code change in sshd. However, maybe the rigorous handling is not required anymore these days. Anyway, even if I re-enable /etc/default/login and the standard PATH handling in sshd, there's no way to set an arbitrary environment. For security reasons, sshd is very selective in the environment variables it sets up. From /etc/default/login, it takes *only* PATH and UMASK, for instance. Everything else should be set in the shell profiles. So, here's what I'll do: - Change cygrunsrv to prepend /bin to $PATH rather then appending it. - Drop the Cygwin specific ignorance of /etc/default/login from the source code and build a new OpenSSH package. Does that sound ok? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpI8hJVqS03B.pgp Description: PGP signature
Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.32-1
Please don't hijack threads. On Aug 14 18:54, Robert Bu wrote: Hi Corinna, Would you kindly test the usage of repo in Cygwin if CYGWIN=winsymlinks:nativestrict? No, I won't. If it works with normal Cygwin symlinks it's ok from my POV. Patches are welcome, of course. See http://cygwin.com/contrib.html Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpQmwK1iW2Zp.pgp Description: PGP signature
Re: [ANNOUNCEMENT] New package: rng-tools-5-1
On Aug 14 12:09, Peter Rosin wrote: On 2014-08-13 11:43, Corinna Vinschen wrote: On Aug 13 10:55, Peter Rosin wrote: This seemed like something I could waste a little time on, and learn something in the process. Which I did, so not all is lost. :-) Ok, I see how the above could be misread easily, since it appeared in the context it did. But the key to interpreting it is that it is all past tense; it was meant as a comment to the whole thread. Cool! I'm glad for any help, you know. If you want to take over the rng-tools package to play further with it, feel free. I'll look into the fake entropy pool size in a not so distant future. What I'm saying is that I have no further input. Sorry. Figuring out how to write device drivers or otherwise access the PCI bus is not something I have done previously (not for any current Windows version anyway), and it feels too much like a black hole regarding time. So, again, sorry if that's disappointing. Yeah, but no worries. That said, I could still adopt the rng-tools package if that would be any help (but I don't see myself hacking on any new HW features) Only if you like. I'm not trying to press gang you into service, though I'm glad for each package taken over by an active maintainer of course. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpIq5HFdr3zu.pgp Description: PGP signature
repo with CYGWIN=winsymlinks:nativestrict
Hi, If I set CYGWIN=winsymlinks:lnk, repo works. However, Windows native Git tool, such as TortoiseGit cannot read the symlink file. I think it treats the symlink file as a normal file and tries to parse the file format as Git specifies. (repo is a tool from Google for Android source management, which works with Git). I guess Windows native tool can handle the symlink if CYGWIN=winsymlinks:nativestrict. However, if I set CYGWIN=winsymlinks:nativestrict, repo init fails with os.symlink(os.path.relpath(src, os.path.dirname(dst)), dst) OSError: [Errno 2] No such file or directory Any advice, idea is greatly helpful. -- Best regards. Robert -- 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: sshd default user PATH
On Aug 14 13:20, Corinna Vinschen wrote: On Aug 14 09:56, Achim Gratz wrote: I'm trying to figure out how sshd comes up with the PATH for the initial environment. Currently I get the Windows sytem PATH (converted to POSIX) and then /bin appended. This is no good, at least /bin should be at the beginning of that PATH. On other systems sshd sets $PATH to /usr/bin:/bin:/usr/sbin:/sbin, but on Cygwin it doesn't change $PATH and just takes what it got from cygrunsrv so as not to break the search path for DLLs not in the system directories. So this is kind of a cygrunsrv problem. It simply appends /bin to $PATH, rather than prepending it. I've not been able to change this system-wide so far. Apparently sshd has been built on a machine where /etc/default/login wasn't present, at least it doesn't appear to try to read that file (or any other system file) for setting up the initial environment. Right, /etc/default/login and, fwiw, any method to change $PATH from the default path is disabled on Cygwin deliberately for the reason outlined above. The /etc/sshrc is run if I create it, but you can't set any environment variables from within it. I don't want to enable user environments. I think it would be nice if there was a system file that could set the initial environment for sshd, maybe setting external_path_file to /etc/ssh_environment fits in better with the default Cygwin /etc layout, though. It's not that simple. It requires a code change in sshd. However, maybe the rigorous handling is not required anymore these days. Anyway, even if I re-enable /etc/default/login and the standard PATH handling in sshd, there's no way to set an arbitrary environment. For security reasons, sshd is very selective in the environment variables it sets up. From /etc/default/login, it takes *only* PATH and UMASK, for instance. Everything else should be set in the shell profiles. So, here's what I'll do: - Change cygrunsrv to prepend /bin to $PATH rather then appending it. - Drop the Cygwin specific ignorance of /etc/default/login from the source code and build a new OpenSSH package. Does that sound ok? There's a problem. On Cygwin it's not /etc/default, but /etc/defaults. Note the trailing s. OpenSSH only provides support for /etc/default/login with no way to influence the name or path. This would require a patch to openssh just for the sake of Cygwin. I asked upstream, but I don't expect that this will be changed any time soon. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp5AdYFLp3TI.pgp Description: PGP signature
Re: sshd default user PATH
Corinna Vinschen corinna-cygwin at cygwin.com writes: On other systems sshd sets $PATH to /usr/bin:/bin:/usr/sbin:/sbin, but on Cygwin it doesn't change $PATH and just takes what it got from cygrunsrv so as not to break the search path for DLLs not in the system directories. I'm running Cygwin since years with all traces of the Windows path deliberately deleted and never hit any problem. That would be different if I tried to mix windows applications in, but I prefer to have wrapper scripts for those anyway. So this is kind of a cygrunsrv problem. It simply appends /bin to $PATH, rather than prepending it. Ah, I was wondering where that comes from since nothing in sshd does it. So sshd just takes over the environment as set up by cygrunsrv? Then it might be a lot easier to just tell cygrunsrv what to put into PATH. Right, /etc/default/login and, fwiw, any method to change $PATH from the default path is disabled on Cygwin deliberately for the reason outlined above. Thanks for confirming, after staring at the configure output for a while I've finally found that #ifdef in the source... It's not that simple. It requires a code change in sshd. However, maybe the rigorous handling is not required anymore these days. May not be necessary anyway. Anyway, even if I re-enable /etc/default/login and the standard PATH handling in sshd, there's no way to set an arbitrary environment. For security reasons, sshd is very selective in the environment variables it sets up. From /etc/default/login, it takes *only* PATH and UMASK, for instance. Everything else should be set in the shell profiles. I really only need PATH at the moment. If I bounce commands directly onto the server without going through a login shell nothing really works as expected at the moment since Cygwin is last in path. I don't want to add Cygwin to the Windows path for other reasons and I really don't have control what else gets added there and in which order. So, here's what I'll do: - Change cygrunsrv to prepend /bin to $PATH rather then appending it. I would appreciate if it could (optionally) look in some configuration file (/etc/environment ?) and use PATH as defined there and store the path as set up in Windows in ORIGINAL_PATH (like done in /etc/profile, where this is conditional on CYGWIN_NOWINPATH being present). - Drop the Cygwin specific ignorance of /etc/default/login from the source code and build a new OpenSSH package. Does that sound ok? Very much. If the environment can be controlled via cygrunsrv, then the changes to sshd might not be necessary. I've just tried using -e PATH=/bin in the sshd service startup, but PATH still seems to be hardcopied from Windows (the setting is ignored if the environment variable already exists?). Regards, Achim. -- 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
Fwd: How to run windows cmd without cygwin
Hi all, I have been using cygwin for several years now and love it. However at the moment I need to run windows command shell (i.e. the cmd) clean and pure without cygwin. For instance if I click start, type cmd and enter, I will open the cmd shell. With cygwin installed, this command shell can be used to execute linux/unix command like ls, grep, env and such. I need this cmd shell to be returned back to original windows cmd shell without the cygwin part. And without having to install cygwin. Best if I can somehow turn on and off the cygwin part as needed. Thanks in Advance Haris -- 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: sshd default user PATH
Greetings, Corinna Vinschen! There's a problem. On Cygwin it's not /etc/default, but /etc/defaults. Note the trailing s. You're confusing /etc/default/ (a directory with default initial values for runtime/startup configurations of [mainly] daemons), which could and SHOULD be changed to suit system needs and Cygwin's /etc/defaults with pristine copy of installation environment, which not supposed to be touched by anything, but installation scripts. OpenSSH only provides support for /etc/default/login with no way to influence the name or path. This would require a patch to openssh just for the sake of Cygwin. I asked upstream, but I don't expect that this will be changed any time soon. I don't expect it to be changed at all, since there's nothing needs to be changed. These two directories serve completely different purposes. -- WBR, Andrey Repin (anrdae...@yandex.ru) 14.08.2014, 16:32 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: How to run windows cmd without cygwin
On 14/08/2014 14:41, Haris Hashim wrote: Hi all, I have been using cygwin for several years now and love it. However at the moment I need to run windows command shell (i.e. the cmd) clean and pure without cygwin. For instance if I click start, type cmd and enter, I will open the cmd shell. With cygwin installed, this command shell can be used to execute linux/unix command like ls, grep, env and such. I need this cmd shell to be returned back to original windows cmd shell without the cygwin part. And without having to install cygwin. Best if I can somehow turn on and off the cygwin part as needed. Thanks in Advance Haris I do not see the problem. Run cmd.exe and define the PATH to not use Cygwin one. 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: sshd default user PATH
Achim Gratz Stromeko at NexGo.DE writes: I've just tried using -e PATH=/bin in the sshd service startup, but PATH still seems to be hardcopied from Windows I did this wrong. I had to re-install the service, not just adding a startup parameter. With -e PATH=/usr/bin the resulting initial PATH from an ssh login is PATH=/usr/bin:/bin. So I can use that as a workaround and we can spend some more time to think about whether that behaviour from cygrunsrv or sshd needs further adjustment or if just the install helper script should ask for these things. Thanks for getting me on the right track. Regards, Achim. -- 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: : How to run windows cmd without cygwin
Greetings, Haris Hashim! I have been using cygwin for several years now and love it. However at the moment I need to run windows command shell (i.e. the cmd) clean and pure without cygwin. For instance if I click start, type cmd and enter, I will open the cmd shell. With cygwin installed, this command shell can be used to execute linux/unix command like ls, grep, env and such. Programs. Not commands. It is no coincidence you can run any program from console. This is, at the end of the day, what console is for - to run programs. I need this cmd shell to be returned back to original windows cmd shell without the cygwin part. It already is. I don't understand your question. And without having to install cygwin. Best if I can somehow turn on and off the cygwin part as needed. Can you please specify more clearly, what you want to achieve? Explaining the problem from the middle doesn't quite help to resolve it. -- WBR, Andrey Repin (anrdae...@yandex.ru) 14.08.2014, 17:25 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: sshd default user PATH
On Aug 14 13:01, Achim Gratz wrote: Achim Gratz Stromeko at NexGo.DE writes: I've just tried using -e PATH=/bin in the sshd service startup, but PATH still seems to be hardcopied from Windows I did this wrong. I had to re-install the service, not just adding a startup parameter. With -e PATH=/usr/bin the resulting initial PATH from an ssh login is PATH=/usr/bin:/bin. So I can use that as a workaround and we can spend some more time to think about whether that behaviour from cygrunsrv or sshd needs further adjustment or if just the install helper script should ask for these things. Thanks for getting me on the right track. That means the patch to sshd isn't that important. Nevertheless, I just released cygrunsrv-1.60-1, which prepends /bin to $PATH. Funny enough, the README file claimed that /bin gets prepended to $PATH since the early days. Just the actual code didn't follow suit :-P Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpoFbkCoyLc_.pgp Description: PGP signature
[ANNOUNCEMENT] Updated: cygrunsrv-1.60-1
I've updated the cygrunsrv package to 1.60-1. Changes and fixes: * This version *finally* prepends /bin to $PATH before starting the actual service process. Up to cygrunsrv-1.50-1, cygrunsrv appended /bin to $PATH, despite being claimed otherwise in the documentation. Have fun, 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
Configure second sshd on the same machine
For building 32bit packages I've set up an additional installation on the same server. To use it from the outside (like) I'm trying to configure a second sshd on the server. So I've installed a cygserver23 and sshd32 service with otherwise identical setup to their 64bit brethren and bumped the port sshd listens on to 3222. The services are starting without any hitch, the port is listening and I can log in via public key or password as I chose. The only problem: after sending the command to the new ssh session, the server closes the connection, claiming that the client had disconnected. the client gets an exit code 5. Does that ring a bell with anyone? I can't find any error in the config. Even when I shut down the 64bit installation completely and let sshd run on the standard port I'm getting the same result. Regards, Achim. -- 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: Configure second sshd on the same machine
On 08/14/2014 12:27 PM, Achim Gratz wrote: For building 32bit packages I've set up an additional installation on the same server. To use it from the outside (like) I'm trying to configure a second sshd on the server. So I've installed a cygserver23 and sshd32 service with otherwise identical setup to their 64bit brethren and bumped the port sshd listens on to 3222. The services are starting without any hitch, the port is listening and I can log in via public key or password as I chose. The only problem: after sending the command to the new ssh session, the server closes the connection, claiming that the client had disconnected. the client gets an exit code 5. Does that ring a bell with anyone? I can't find any error in the config. Even when I shut down the 64bit installation completely and let sshd run on the standard port I'm getting the same result. The only time I've seen that is when I start the server in debug mode. -- Larry _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: repo with CYGWIN=winsymlinks:nativestrict
On Thu, Aug 14, 2014 at 07:38:33PM +0800, Robert Bu wrote: If I set CYGWIN=winsymlinks:lnk, repo works. However, Windows native Git tool, such as TortoiseGit cannot read the symlink file. I think it treats the symlink file as a normal file and tries to parse the file format as Git specifies. I've never used native Windows Git tools, but if they work in a similar way to Windows Subversion tools, they're expecting a symlink to be something that doesn't act like a symlink in any way whatsoever. I suspect this is one of those areas where Cygwin and native-Windows tools aren't going to play nicely without a lot of difficulty because of the fundamental differences between *nix and Windows approaches. The only useful suggestion I have is to abandon Windows Git tools. If you want GUIs you could try gitk and git-gui in Cygwin (you'll need to install an X server to use these). You could also try suggesting the TortoiseGit folk handle the symlinks created by Cygwin (of whatever flavour) as symlinks in the Git repository, but even if they accept that as a feature request I'd guess it'd be a while before it'd be available. I guess Windows native tool can handle the symlink if CYGWIN=winsymlinks:nativestrict. However, if I set CYGWIN=winsymlinks:nativestrict, repo init fails with os.symlink(os.path.relpath(src, os.path.dirname(dst)), dst) OSError: [Errno 2] No such file or directory This seems odd, although the error here really doesn't say very much about what's going on. I've no idea if this is being run in Cygwin Python or Windows Python, and I have no idea of the directory structure and symlink locations in the paths it's using. -- 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: Configure second sshd on the same machine
Larry Hall (Cygwin reply-to-list-only-lh at cygwin.com writes: The only time I've seen that is when I start the server in debug mode. That's not the problem. If I create /etc/nologin, I get the message back, so even that part of the connection works. But here's one step further: in debug mode I can actually run a single command. I can't run a shell since apparently the sshd is unable to locate a tty. Hmmm Regards, Achim. -- 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
Posting ITA/ITP
Hi group, I'm trying to post to gmane.os.cygwin.applications, but I get an NNTP error: 'gmane.os.cygwin.applications is unidirectional' Should I post to another newsgroup? Daniel -- 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: Posting ITA/ITP
On Aug 14 20:22, D. Boland wrote: Hi group, I'm trying to post to gmane.os.cygwin.applications, but I get an NNTP error: 'gmane.os.cygwin.applications is unidirectional' Should I post to another newsgroup? As maintainer you should be subscribed to the mailing list cygwin-apps AT cygwin DOT com. That's also where you should post. See https://cygwin.com/lists.html Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpRRlnMuyuKt.pgp Description: PGP signature
Re: Configure second sshd on the same machine
Greetings, Achim Gratz! The only time I've seen that is when I start the server in debug mode. That's not the problem. If I create /etc/nologin, I get the message back, so even that part of the connection works. But here's one step further: in debug mode I can actually run a single command. I can't run a shell since apparently the sshd is unable to locate a tty. Hmmm Did you checked the $PATH of a running server? 64- and 32-bit installations should not cross $PATH's. (It's kinda obvious, but still important enough to check thoroughly.) -- WBR, Andrey Repin (anrdae...@yandex.ru) 14.08.2014, 22:39 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: Posting ITA/ITP
D. Boland writes: I'm trying to post to gmane.os.cygwin.applications, but I get an NNTP error: 'gmane.os.cygwin.applications is unidirectional' Should I post to another newsgroup? No, you need to subscribe and send your post via mail. Since I don't care about the mails I get since I read the group on NNTP anyway, I've opted for the digest and just auto-delete when it hits my mailbox. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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: Configure second sshd on the same machine
Andrey Repin writes: Did you checked the $PATH of a running server? 64- and 32-bit installations should not cross $PATH's. (It's kinda obvious, but still important enough to check thoroughly.) Yes I did. That is all correctly set up, the error seems to be a failure to allocate a tty (in debug mode sshd complains about an invalid file descriptor -- sorry I can't copy the actual error message since I've gone home for today). Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- 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: repo with CYGWIN=winsymlinks:nativestrict
Thank you for your response. Adam Dinwoodie wrote on 2014/8/15 0:44: On Thu, Aug 14, 2014 at 07:38:33PM +0800, Robert Bu wrote: If I set CYGWIN=winsymlinks:lnk, repo works. However, Windows native Git tool, such as TortoiseGit cannot read the symlink file. I think it treats the symlink file as a normal file and tries to parse the file format as Git specifies. I've never used native Windows Git tools, but if they work in a similar way to Windows Subversion tools, they're expecting a symlink to be something that doesn't act like a symlink in any way whatsoever. I suspect this is one of those areas where Cygwin and native-Windows tools aren't going to play nicely without a lot of difficulty because of the fundamental differences between *nix and Windows approaches. The only useful suggestion I have is to abandon Windows Git tools. If you want GUIs you could try gitk and git-gui in Cygwin (you'll need to install an X server to use these). Yes, I'ved used gitk as in Linux. It's not so user-friendly as TortoiseGit. You could also try suggesting the TortoiseGit folk handle the symlinks created by Cygwin (of whatever flavour) as symlinks in the Git repository, but even if they accept that as a feature request I'd guess it'd be a while before it'd be available. So, I'm trying with winsymlinks:nativestrict. I expect Native Git tool can work with it, since it's 'native'. I guess Windows native tool can handle the symlink if CYGWIN=winsymlinks:nativestrict. However, if I set CYGWIN=winsymlinks:nativestrict, repo init fails with os.symlink(os.path.relpath(src, os.path.dirname(dst)), dst) OSError: [Errno 2] No such file or directory This seems odd, although the error here really doesn't say very much about what's going on. I've no idea if this is being run in Cygwin Python or Windows Python, and I have no idea of the directory structure and symlink locations in the paths it's using. It must be Cygwin Python. I do not install any Windows Python. B.R. Robert. -- 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] Updated: man-db-2.6.7-2
The following packages have been updated in the Cygwin distribution: * man-db-2.6.7-2 man-db is an implementation of the standard Unix documentation system accessed using the man command. It uses a Berkeley DB database in place of the traditional flat-text whatis databases. This release removes the cache database generation from the postinstall step due to its often excessive length. Users will need to manage the database themselves with mandb(1) in order to use whatis/apropos(1). -- Yaakov (on behalf of Chris Breisch) CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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] Updated: curl-7.37.1-1
The following packages have been updated for both arches: * curl-7.37.1-1 * libcurl4-7.37.1-1 * libcurl-devel-7.37.1-1 * libcurl-doc-7.37.1-1 cURL is a library and command line tool for transferring data with URL syntax, supporting numerous protocols, SSL certificates, HTTP POST, HTTP PUT, FTP uploading, HTTP form based upload, proxies, cookies, user+password authentication, file transfer resume, proxy tunneling and more. This is an update to the latest upstream release. -- Yaakov CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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] Updated: ca-certificates-1.97-2
The following package has been updated for the Cygwin distribution: * ca-certificates-1.97-2 ca-certificates contains the Certificate Authority root certificates needed for verifying SSL certificates. This release provides empty anchors and blacklist directories for easier management of third-party CA certificates. -- Yaakov CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
Updated: Cygwin 1.7.32-1
Hi Cygwin friends and users, I just released Cygwin 1.7.32-1. This release comes with a few bug fixes in header files and a slightly improved /proc/cpuinfo output, but otherwise it concentrates on a new feature which isn't readily user visible. The new feature requires a new GCC which will be released by Jon_Y shorty. This combination, cygwin 1.7.32 / gcc 4.8.3-3, also allows to handle C++11 thread local objects for the first time. What's new: --- - Export __cxa_atexit and __cxa_finalize to allow C++ standards-compliant destructor handling in libstdc++ and g++ compiled code. Please note that, in order to benefit from this new feature, C++ code must be recompiled with the upcoming gcc 4.8.3-3 release which will enable the -fuse-cxa-atexit flag by default, and that C++ applications using this feature will not run on older Cygwin releases. - Support more recent CPU flags in /proc/cpuinfo. Bug Fixes - - Decorate attribute names with __, for namespace safety in various header files. Addresses: https://cygwin.com/ml/cygwin/2014-07/msg00371.html - Fix sys/file.h for using in C++ code. Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00122.html To install 32-bit Cygwin use http://cygwin.com/setup-x86.exe To install 64 bit Cygwin use http://cygwin.com/setup-x86_64.exe The 64 bit Cygwin distribution doesn't yet come with as many packages as the 32 bit version, but more packages will be available over time. If you're already running a 32 bit version of Cygwin on 64 bit Windows machines, you can continue to do so. If you're planning a new install of Cygwin on a 64 bit Windows machine, consider to use the new 64 bit Cygwin version, unless you need certain packages not yet available in the 64 bit release. Have fun, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Updated: cygrunsrv-1.60-1
I've updated the cygrunsrv package to 1.60-1. Changes and fixes: * This version *finally* prepends /bin to $PATH before starting the actual service process. Up to cygrunsrv-1.50-1, cygrunsrv appended /bin to $PATH, despite being claimed otherwise in the documentation. Have fun, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Updated: man-db-2.6.7-2
The following packages have been updated in the Cygwin distribution: * man-db-2.6.7-2 man-db is an implementation of the standard Unix documentation system accessed using the man command. It uses a Berkeley DB database in place of the traditional flat-text whatis databases. This release removes the cache database generation from the postinstall step due to its often excessive length. Users will need to manage the database themselves with mandb(1) in order to use whatis/apropos(1). -- Yaakov (on behalf of Chris Breisch) CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Updated: curl-7.37.1-1
The following packages have been updated for both arches: * curl-7.37.1-1 * libcurl4-7.37.1-1 * libcurl-devel-7.37.1-1 * libcurl-doc-7.37.1-1 cURL is a library and command line tool for transferring data with URL syntax, supporting numerous protocols, SSL certificates, HTTP POST, HTTP PUT, FTP uploading, HTTP form based upload, proxies, cookies, user+password authentication, file transfer resume, proxy tunneling and more. This is an update to the latest upstream release. -- Yaakov CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Updated: ca-certificates-1.97-2
The following package has been updated for the Cygwin distribution: * ca-certificates-1.97-2 ca-certificates contains the Certificate Authority root certificates needed for verifying SSL certificates. This release provides empty anchors and blacklist directories for easier management of third-party CA certificates. -- Yaakov CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
