Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: Eric Blake To: cygwin AT cygwin DOT com Subject: [ANNOUNCEMENT] Updated: coreutils-5.3.0-5 Reply-To: cygwin AT cygwin DOT com Message-Id: <20050415134511.6B20657D97@cygbert.vinschen.de> Date: Fri, 15 Apr 2005 15:45:11 +0200 (CEST) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A new release of coreutils, 5.3.0-5, is available. NEWS ==== This is a minor patch release. The overall 5.3.0 series was designated unstable by the upstream author (compared to the stable 5.2.1), because it introduces some POSIX-compliance fixes for the first time; but there have been few complaints so the 5.2.1 series is no longer available via setup.exe. See /usr/share/doc/coreutils-5.3.0/NEWS for the changes since 5.2.1-5. This release reverts the implicit .exe magic in rm(1) introduced in 5.3.0-4. It turns out that it broke libtool, and didn't always behave properly on symlinks. I hope to add a command-line option to all the tools that experience .exe magic, to make it user-selectable whether .exe can be added as needed, but that will take more time to implement. Note that su(1) is UNSUPPORTED; for more details, see http://cygwin.com/faq/faq_3.html#SEC42. This package REQUIRES cygwin 1.5.13 or newer snapshots, and has been tested with cygwin 1.5.14. If you are running on a Windows 95, 98, or ME system, cygwin 1.5.14 still has some known bugs that may affect several coreutils, such as touch(1). To avoid those bugs, you can use a snapshot or wait for cygwin 1.5.15. When building from source, you will need your own version of automake 1.9.5 or later (until the cygwin automake version is updated) if you want `make -k check' to get past the spurious failures caused by bugs in the testsuite. DESCRIPTION =========== GNU coreutils provides a collection of commonly used utilities essential to a standard POSIX environment. It comprises the former textutils, sh-utils, and fileutils packages. The following executables are included: [ basename cat chgrp chmod chown chroot cksum comm cp csplit cut date dd df dir dircolors dirname du echo env expand expr factor false fmt fold gkill groups head hostid hostname id install join link ln logname ls md5sum mkdir mkfifo mknod mv nice nl nohup od paste pathchk pinky pr printenv printf ptx pwd readlink rm rmdir seq sha1sum shred sleep sort split stat stty sum sync tac tail tee test touch tr true tsort tty uname unexpand uniq unlink users vdir wc who whoami yes UPDATE ====== To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions, then look for 'coreutils' in the 'Base' category. Because of packaging conflicts between coreutils-5.2.1-5, cygutils-1.2.5-1, gettext-0.14.1-1, libiconv-1.9.2-1, and procps-010801-2, upgrading any of these packages may delete a file provided by another. Running `cygcheck -c' will show you if upgrading left a package incomplete, in which case you should reinstall that package. DOWNLOAD: ========= Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: ========== If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. - -- Eric Blake -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCXmj584KuGfSFAYARAiytAJ0QHFf20imZYvQbblygHDlA6tUC0ACgpFiU z9NxNUpq9Aog9JDBLe0JziM= =UnZJ -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/