bug-fileutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

*test* release of the GNU fileutils: fileutils-4.0.32: PLEASE test it


From: Jim Meyering
Subject: *test* release of the GNU fileutils: fileutils-4.0.32: PLEASE test it
Date: 11 Nov 2000 17:01:46 +0100
User-agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7

I've just made the 32nd test release of the GNU fileutils since
version 4.0, and hope to release fileutils-4.1 within the next
month or two.

The gzip-compressed tar archive is here:

  ftp://alpha.gnu.org/gnu/fetish/fileutils-4.0.32.tar.gz

Here are its MD5 and SHA1 signatures:

8bf7f110208df9bd488831761ec5f582  fileutils-4.0.32.tar.gz
1b18712dc47009d82df6d46c83030ed358b44328  fileutils-4.0.32.tar.gz

I've vowed not to introduce any more changes before 4.1 that seem like
they might be destabilizing.  Of course, if a serious problem is exposed,
it'll be fixed before the release.

Please test this release on as many different types of systems and with
as many different compilers as you can.  You can perform a basic sanity
test with these commands:

  gzip -dc fileutils-4.0.32.tar.gz|tar xf -
  cd fileutils-4.0.32 && ./configure && make && make check

Or better still, actually install and use the tools (I do).
But remember this is a _test_ release, so treat it with caution.

If you see a failure of the tools or test suite, please report
it to the address@hidden mailing list.  You can subscribe
to that list and get to the archives from here:

  http://mail.gnu.org/mailman/listinfo/bug-fileutils

If any of you have access to unusual systems like Unicos, Acorn, Ultrix
etc., please be sure to test this release on them.  I don't have access
to such systems.  If you are willing and able to give me ssh access
to such an unusual system, please let me know:  then I'll be able to
ensure that each subsequent test release of the fileutils, textutils,
and sh-utils builds and passes some sanity tests on that system.

I'd really like to make the 4.1 release soon.  If you know of folks who
do the translations, please let them know that there are a few messages
that are new or updated and need the corresponding translations.
This test release of the fileutils can produce diagnostics in the
following languages:

  cs Czech
  da Danish
  de German
  el Greek
  es Spanish
  fr French
  gl Galician
  it Italian
  ja Japanese
  ko Korean
  nl Dutch
  no Norwegian
  pl Polish
  pt Portuguese
  pt_BR Brazilian
  ru ìÏËÁÌÉÚÁÃÉÑ
  sk Slovak
  sl Slovenian
  sv Swedish
  zh Chinese

If you want to help, see the Translation Project's home page:

  http://www.iro.umontreal.ca/contrib/po/HTML/index.html

There have been many changes since fileutils-4.0.
I've included the entries from the NEWS file below:

Thanks,
Jim
------------------------

[4.0.32]
* touch now interprets a lone numeric argument of 8 or 10 digits as a file name,
  rather than as a date/time in the obsolescent `MMDDhhmm[YY]' format.
* mkdir no longer sets the permissions of the final directory component
  if it already exists (this bug, too, was introduced recently)
* ls's --full-time format string is now locale dependent
[4.0.31]
* mkdir: fix a bug introduced in 4.0.30 whereby `mkdir existing-dir' would
  succeed.  Now it fails, as it should (and used to).
[4.0.30]
* mkdir: fix a bug introduced in 4.0.28 whereby parent directories created
  via `mkdir -p' would have permissions that did not account for the umask
[4.0.29]
* ls.c wouldn't compile on some systems: fix it
* `cp -R --parents dir1/ dir2' failed on NetBSD, due to a portability problem
[4.0.28]
* ls is much more efficient on systems (e.g., linux-2.4.*) that store file
    type information in directory entries.
* shred now automatically determines the size of each block device argument
* ls's date/time format strings are now local dependent
* mkdir, mknod, mkfifo, and chmod work better in conjunction with ACLs
* `cp --parents dir1/ dir2' no longer gets a failed assertion
* shred now determines the size of block devices like /dev/fd0
* `shred --exact file1 file2' now erases `file1', too
[4.0.27]
* install once again unlinks an existing destination before trying to open it
* mv no longer gets a failed assertion when moving a directory (specified with
    a trailing slash) from one partition to another, and giving it a different
    name at the destination.
* `cp --link -f src existing-dest' no longer fails (bug introduced in 4.0z)
* cp's new --remove-destination option now works with -R
[4.0z]
* `cp -p' once again preserves `special' permission bits (this bug was
    introduced in 4.0y)
* mv's --force (-f) option now controls solely whether mv prompts (per POSIX)
* `cp -f' now first attempts to open an existing destination file, and only
    if that fails does it resort to unlinking the file and retrying the open.
    Before, it would unlink the file before trying to open it.
* cp accepts a new option, --remove-destination, that provides the old behavior
* cp's -f option no longer cancels the effect of --interactive (-i) (per POSIX)
* when ls sorts directory entries, it now honors the current locale settings
* dd's `skip=BLOCKS' operator once again works on systems with a buggy lseek
  function (Linux, at least on SCSI tape devices)
* fix a typo in install-sh
[4.0y]
* cp now accepts the POSIX-mandated -H and -L options.
* cp -p and mv now try to preserve uid even if you're not root, as per POSIX.2.
  This affects behavior only on hosts that let you give files away via chmod.
* du would fail when given `.' or `..' followed by other command line arguments
* Using cp's short-named `-P' option evokes the warning that that the
   meaning of `-P' will soon change.  Use `--parents' instead.
* chgrp, chmod, and chown: when used with the --verbose option, might give an
  invalid diagnostic (due to clobbered errno) when failing.
[4.0x]
* Fix cp so that `cp -r DIR1/ DIR2' works properly once again.
* New ls option --quoting-style=clocale acts like --quoting-style=locale,
  except that it quotes "like this" by default instead of `like this'.
[4.0w]
* When `cp -pR' fails to copy a file, it now preserves permissions, owner,
   and group of the containing directory.
[4.0v]
* df, du, and ls now round disk usage up and disk free space down
* df, du, ls: --block-size=N now works for values of N that are e.g.,
    not a multiple of the file's block size
[4.0u]
* give proper diagnostic for mv usage error
* fix compile problem with lib/strnlen.c
[4.0t]
* `cp -d -u' no longer fails with certain existing destination symlinks
* rmdir and mkdir accept -v as synonym for --verbose
[4.0s]
* rm no longer segfaults on certain very deep hierarchies
* IMPORTANT SECURITY FIX: a running `rm -r' may no longer be subverted to
  remove unintended directories
* cp can now remove unwritable files in interactive mode; contrary to how mv
   works, cp's --interactive (-i) option does *not* cancel the effect of a
   preceding --force (-f) option.
* all programs fail when printing --help or --version output to a full device
* install no longer performs chmod if chown fails (see ChangeLog for example)
[4.0r]
* `du dir/subdir1 dir/subdir2' no longer fails
* chown accepts new option: --from=CURRENT_OWNER:CURRENT_GROUP
* cp accepts new option: --strip-trailing-slashes
* install --directory (-d) may now be used to set special bits
    e.g., `install -m a=rwx,o+t -d DIR' now honors the `o+t' part
* cp, mv, ln, install: document that while the --backup option takes an
  optional argument, the -b option accepts none
* `ls -e' fails with a more useful diagnostic
* df produces better output for loop file system mount points
[4.0q]
* install -D bug is fixed
* chown now works properly when the specified login name contains a period
  This is at the expense of always looking up the entire USER.GROUP string
  as a login name first, and only then (upon failure) interpreting the `.'
  as a separator and looking up `USER'.  To avoid the extra getpwnam call,
  always use the POSIX-mandated `:' character as the separator.
* `du some-other-dir' no longer fails if it can't open the current directory
* `mv DIR EXISTING-FILE' no longer removes EXISTING-FILE.  Now it gets an error
  as POSIX says it must.
* touch no longer hangs on fifos
[4.0p]
* various tools: quote multibyte characters correctly in diagnostics
* mv: portability fix for alpha
* dd: portability fix
* unified lib/: now that directory and most of the configuration framework
  is common between fileutils, textutils, and sh-utils
[4.0o]
* Include lib/nanosleep.h.
[4.0n]
* cp, install, ln, and mv: when making backup files in verbose mode, these
  commands now print the backup file name on the same line as the rest of the
  information, e.g., `a -> b (backup: b.~13~)' rather than on a separate line
  as all but ln used to do.  ln didn't output the backup file name at all.
[4.0m]
* mv accepts new option: --strip-trailing-slashes (soon, many other
  programs will, too)
* df no longer hangs when there is an inaccessible mount point unrelated to PATH
* rmdir --verbose no longer prints extra, bogus diagnosic upon failure
* fix df bug that made it print bogus values in the `Use%' column.
* touch -d once again parses dates with `hh:mm ZONE' time zone info.
[4.0l]
* ls -l honors a trailing slash on a symlink argument, per POSIX.
* shred no longer appears to infloop when asked to remove files in
  unwritable directories
* `ls -ul' and `ls -uc' sort by name once again, as they should
[4.0k]
* mv may now be used to move a file onto a symlink to itself when that
  symlink is on a separate partition.  With fileutils-4.0j, it would
  fail with a diagnostic saying they were the same file.
* touch would fail with the misleading diagnostic `no such file' when asked
  to create a file in an unwritable directory.  Now it says something like
  `permission denied' or `read-only file system'.
[4.0j]
* mkdir may now be used to set special bits  e.g., `mkdir -m o+t dir' works
* touch can now change the time(s) of a file you own even if you don't have
  read or write access to it
* rm no longer dumps core after warning about directory cycles
* mv now refuses to move a file onto a symlink to itself when that symlink
  is on a separate partition.  Before, it would remove the file and leave
  only the symlink.
* `install -d -g foo 1/2' now sets the `group' of the final component as well
  as that of the leading one.
* df, du, and ls no longer divide by zero when an invalid block size is
  specified through an environment variable
* under certain conditions, chgrp would fail to affect files referenced
  through symlinks.  Now it does.
* ln now makes hard links to symlinks on systems that support it.
* touch: no longer infloop on dangling symlinks
* cp, install, ln, mv: deprecate the --version-control option.  Use --backup's
  new optional argument instead.  The old option still works, but now evokes a
  warning.
* cp, install, ln, mv: the --backup option now accepts an optional argument
* cp, install, ln, mv: accept new option: --target-directory=DIR
* chgrp: accept new option, --dereference.  --no-dereference is now the default.
* New ls option --quoting-style=locale acts like --quoting-style=c, except
  with locale-specific quoting symbols (` and ' by default) instead of ".
* `df DIR' is less likely to hang due to bad NFS mounts
* As per POSIX.2, `df -P' now uses ceiling rather than rounding, and its
  header now says `1024-blocks ... Capacity' instead of `1k-blocks ... Use%'.
[4.0i]
* `cp -f FILE FILE' and `mv -f FILE FILE' no longer remove FILE
* touch works once again (DST-wise) when certain `--date DATE-TIME'
  values are specified.
* shred's -u option (short form of --remove) is now accepted
[4.0h]
* cp --one-file-system (-x) no longer crosses filesystem boundaries.
* touch can once again operate on directories
[4.0g]
* New large-file support for AIX and HP-UX, and for cross-compiles.
* shred's default options are now suitable for devices, not files, since
  shred is more reliable on devices.  shred now does not remove by default;
  the old -p or --preserve option was inverted and renamed to -u or --remove.
* shred -u now attempts to truncate devices before removing them.
* shred -v no longer outputs carriage-returns; shred -vv has no extra effect;
  shred -v now outputs to stderr.
* shred now tries to find the size of a non-regular file by seeking to its end.
* dd now opens the output file for *read* access only if `seek=' is used.
[4.0f]
* `ls --color' no longer segfaults
* dd works once again
[4.0e]
* shred --devices option renamed to -D so that -d, -i and -r can be
  compatible with rm.
* shred -s/--size=N option added to specify the size of the object to be
  shredded.
* `shred -' now shreds stdout rather than stdin.  This is incompatible with -v.
* shred now does not need to read from its output file, so opens it O_WRONLY
* `ls -l' uses `+' to designate each file that has a custom ACL
* eliminate race condition that could make touch truncate a nonempty file
* No longer use *_unlocked I/O macros on systems (like solaris5.5.1) where
  they're not declared, so selected executables (e.g., rm) that are linked
  with shared libraries will once again run on solaris5.6 systems.
[4.0d (aka 4.1-b3)]
* ls recognizes solaris 2 `doors'
* new program: shred
* ln: Allow creation of a hard link to a dangling symlink
* cp, mv, install: --verbose now prints a message for each backup-related
  renaming
* portability fixes for copy.c's code to detect move-directory-into-self
* upgrade to automake-1.3b
* upgrade to autoconf-2.13, and...
* remove some of the kludges in m4/*.m4 that permitted
[4.1-b2]
* concurrent `mkdir -p' processes no longer fail when creating the
  same hierarchy
* argmatch.c has been fixed so that the unambiguous usage `ls --color=n'
  no longer evokes an error.
* now, specifying an improper argument for an option that accepts enumerated
  values evokes diagnostics like this:
    $ src/touch --time=x file
    src/touch: invalid argument `x' for `--time'
    Valid arguments are:
      - `atime', `access', `use'
      - `mtime', `modify'
    Try `src/touch --help' for more information.
[4.1-b1]
* ls --quoting-style=c prints correct octal escapes for certain nonprinting
  characters in file names.
* fix `ls -R .' formatting bug that broke mktexlsr
* moving a directory into itself is properly diagnosed in more cases
* moving a directory containing hard-linked files now works



reply via email to

[Prev in Thread] Current Thread [Next in Thread]