[ANNOUNCEMENT] Updated: python-2.7.8-1
The following packages have been updated in the Cygwin distribution: * python-2.7.8-1 * python-test-2.7.8-1 * python-tkinter-2.7.8-1 * idle-2.7.8-1 Python is an interpreted, interactive, object-oriented programming language. It incorporates modules, exceptions, dynamic typing, very high level dynamic data types, and classes. Python combines remarkable power with very clear syntax. It has interfaces to many system calls and libraries, as well as to various window systems, and is extensible in C or C++. It is also usable as an extension language for applications that need a programmable interface. This is an update to the latest upstream bugfix release for the 2.7 branch. python2 and python2-config symlinks have been added in accordance with PEP 394. -- Yaakov (on behalf of Jason Tishler) 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: llvm/clang-3.4.2-3
The following packages have been updated in the Cygwin distribution: * llvm-3.4.2-3 * llvm-doc-3.4.2-3 * libllvm3.4-3.4.2-3 * libllvm-devel-3.4.2-3 * libllvm-devel-static-3.4.2-3 * clang-3.4.2-3 * clang-analyzer-3.4.2-3 * libclang-3.4.2-3 * libclang-devel-3.4.2-3 * libclang-devel-static-3.4.2-3 * python-clang-3.4.2-3 * python3-clang-3.4.2-3 * cygwin32-clang-3.4.2-1 (NEW for x86_64) * cygwin64-clang-3.4.2-1 (NEW for x86) The LLVM suite provides libraries and tools for code generation and optimization. Also included is Clang, an LLVM native C/C++/ObjC compiler, and the Clang Static Analyzer, a tool that automatically finds bugs in code. This release fixes basic usage of clang for the x86_64-cygwin target by defaulting to the medium code model along with a few other minor fixes. Please note that while clang technically works now, it still has not been extensively tested for Cygwin and therefore (possibly serious) bugs may remain. I have also added cross-cygwin clang compilers for each arch. -- 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: postgresql-9.3.5-1
Version 9.3.5.1 of packages libecpg-compat3 libecpg-devel libecpg6 libpgtypes3 libpq-devel libpq5 postgresql postgresql-client postgresql-contrib postgresql-devel postgresql-doc postgresql-plperl postgresql-plpython are available in the Cygwin distribution: KNOWN BUG "set statement_timeout" does not work. See BUG #9074: prepared_xacts test freezes http://www.postgresql.org/message-id/20140202181323.8089.65...@wrigleys.postgresql.org Investigation running. CHANGES Full upstream changes: http://www.postgresql.org/docs/9.3/static/release-9-3-5.html http://www.postgresql.org/about/news/1534/ Migration to Version 9.3.5 A dump/restore is not required for those running 9.3.X. However, the error fixed in the first changelog entry below could have resulted in corrupt data on standby servers. It may be prudent to reinitialize standby servers from fresh base backups after installing this update. ADVISE for major version UPGRADE http://www.postgresql.org/support/versioning/ Major releases usually change the internal format of system tables and data files. These changes are often complex, so we do not maintain backward compatibility of all stored data. A dump/reload of the database or use of the pg_upgrade module is required for major upgrades. DESCRIPTION PostgreSQL is a powerful, open source object-relational database system. It has a proven architecture that has earned it a strong reputation for reliability, data integrity, and correctness. It is fully ACID compliant, has full support for foreign keys, joins, views, triggers, and stored procedures (in multiple languages). It includes most SQL:2008 data types HOMEPAGE http://www.postgresql.org Marco Atzeri If you have questions or comments, please send them to the cygwin mailing list at: cygwin (at) cygwin (dot) com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, 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
Re: Re: [ANNOUNCEMENT] Updated: rsync 3.0.9-1 -- fast, versatile file synchronizing tool
Roland, Please send your replies to the list! 2014-07-28 22:18 GMT+02:00 Roland Kletzing: >>Did you know that 3.1.0 has performance issues on cygwin? See almost >>at the bottom of the "BUG FIXED" at >>http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.1.1pre2-NEWS > > if you refer to > > - Switched Cygwin back to using socketpair "pipes" to try to speed it up. Yes, that is what I was referring to. > then its not a performance issue of 3.1.0 but the issue is much older, see > https://bugzilla.samba.org/show_bug.cgi?id=10322 and > http://git.samba.org/rsync.git/?p=rsync.git&a=search&h=HEAD&st=commit&s=socketpair All I did was: grabbed the 3.0.9 source package from the cygwin mirror. Build it and ran "cygport test" and all test succeeded (some were skipped). After that I updated that cygport file, downloaded and build 3.1.0 and ran "cygport test". Some test failed. With 3.1.1pre1, pre2 and 3.1.1 release it worked again. So for me there was a cygwin related bug in 3.1.0 and was fixed in 3.1.1, just like it says in NEWS. > btw, maybe someone has a clue why cygwin rsync build lost xattr support? > http://marc.info/?l=rsync&m=140653072002534&w=2 ? I don't know. Just used the vanilla build options. So apparently the developers of rsync disabled xattr on cygwin. Regards, Frank -- 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: The eternal uid issue
Corinna Vinschen wrote: > The permissions of the home folder are set to 01777 by default (S_ISVTX > bit!). Since we can't rely on central administration for Cygwin, this > allows a user to create her own homedir automatically at first start of > a Cygwin shell. > > You might consider to disable this full patch check in sendmail for > Cygwin. Is there some configuration flag, maybe? > If I make the 'Users' group owner of the /home folder and remove the world-writable bit, Sendmail doesn't complain anymore. I found out that everybody who is logged on, will be put in the 'Users' group anyway. Regards, 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
Please test AD integration changes, documentation attached (was Re: timeout in LDAP access)
On Jul 28 20:51, Denis Excoffier wrote: > On 2014-07-28 11:21, Corinna Vinschen wrote: > > Ping? > > > > On Jul 18 21:18, Corinna Vinschen wrote: > >> > >> We really should do that to avoid collisions with system accounts, IMHO. > >> > >> But maybe we should handle it as a border case of a border case, and > >> reliably. Rather than using the default fake mechanism, what if > >> we use default offsets for the two cases: > >> > >> Case 1: posix offset is < 0x10 ==> Enforce posix 0ffset 0xfe8 > >> Case 2: posix offset can't be fetched (this points to a local user > >>having no access to this kind of domain information) > >>==> Enforce posix offset 0xfe00. > >> > >> This would result in potential collisions in very rare border cases, > >> but it would result in reliable mappings throught all processes. > >> And, the complexity would be quite small. > > > > any feedback on this one? Shall I create a snapshot with a matching > > patch? > I have nothing to add except that i am a great fan of cygwin snapshots in > general, and i suppose that if several posix offsets are set to 0, it is > a minor problem if all of them get replaced by the same 0xfe8. I chose even more unlikely offsets 0xfea0 and 0xfe50, but otherwise, the 2014-07-29 snapshot I just uploaded implements the above method, see http://cygwin.com/snapshots/ I also described this briefly in my preliminary documentation (attached), which, I fear, it's time to merge into the official docs. I'm inclined to create a new official Cygwin version with the AD integration changes pretty soon. There seem to be no other way to get more feedback on these changes :| Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat === History === For as long as Cygwin has existed, it has stored user and group information in /etc/passwd and /etc/group files. Under the assumption that these files would never be too large, the first process in a process tree, as well as every execing process within the tree would parse them into structures in memory. Thus every Cygwin process would contain an expanded copy of the full information from /etc/passwd and /etc/group. This approach has a few downsides. One of them is that the idea to have always small files is flawed. Another one is that reading the entire file is most of the time entirely useless, since most processes only need information on their own user and the primary group. Last but not least, the passwd and group files have to be maintained separately from the already existing Windows user databases, the local SAM and Active Directory. On the other hand, we have to have a mapping between Windows SIDs and POSIX uid/gid values (see [1]), so we rely on some mechanism to convert SIDs to uid/gid values and vice versa. Microsoft "Services for UNIX" (SFU) (which are unfortunately deprecated since Windows 8/Server 2012) never used passwd/group files. Rather, SFU used a fixed, computational mapping between SIDs and POSIX uid/gid. It allows to generate uid/gid values from SIDs and vice versa. The mechanism is documented, albeit in a confusing way and spread over multiple MSDN articles. The Cygwin approach clones the mapping, with just tiny differences for backward compatibility. = How does it work? = The following description assumes you're comfortable with the concept of Windows SIDs and RIDs. For a brief introduction, please read [1]. Cygwin's new mapping between SIDs and uid/gid values works in two ways. - Read /etc/passwd and /etc/group files, like before, mainly for backward compatibility. - If no files are present, or if an entry is missing in the files, ask Windows. At least, that's the default behaviour now. It will be configurable using a file /etc/nsswitch.conf, which is discussed in a later section. Let's explore the default for now. If files are present, they will be scanned on demand as soon as a mapping from SIDs to uid/gid or account names is required. The new mechanism will never read the entire file into memory, but only scan for the requested entry and cache this one in memory[2]. If no entry is found, or no passwd or group file was present, Cygwin will ask the OS. Note: If the first process in a Cygwin process tree determines that no /etc/passwd or /etc/group file is present, no other process in the entire process tree will try to read the files later on. This is done for self-preservation. It's rather bad if the uid or gid of a user changes during the lifetime of a process tree. For the same reason, if you delete the /etc/passwd or /etc/group file, this will be ignored. The passwd and group records read from the files will persist in memory until either a new /etc/passwd or /etc/group files is created, or you exit all processes in the cur
