pkgsrc/sysutils/coreutils, branch cube-native-xorg[no description]https://git.osdyson.ru/mirror/pkgsrc/atom?h=cube-native-xorg2008-05-15T20:01:03ZReach over from misc/gnuls to sysutils/coreutils for common logic and2008-05-15T20:01:03Ztnntnn@pkgsrc.org2008-05-15T20:01:03Zurn:sha1:68c71b7dafb49751d4384496251f7735f9c43862
patches. Updates gnuls to 6.11 and makes it track coreutils.Update "coreutils" package to version 6.11. Changes since version 6.10:2008-05-13T09:22:46Ztrontron@pkgsrc.org2008-05-13T09:22:46Zurn:sha1:26c774fd7ce3a0aef0095ccaa9e5b638d175b61d
- "cp -fR fifo E" now succeeds with an existing E. Before this fix, using
-fR to copy a fifo or "special" file onto an existing file would fail
with EEXIST. Now, it once again unlinks the destination before trying
to create the destination file. [bug introduced in coreutils-5.90]
- dd once again works with unnecessary options like if=/dev/stdin and
of=/dev/stdout. [bug introduced in fileutils-4.0h]
- id now uses getgrouplist, when possible. This results in
much better performance when there are many users and/or groups.
- ls no longer segfaults on files in /proc when linked with an older version
of libselinux. E.g., ls -l /proc/sys would dereference a NULL pointer.
- md5sum would segfault for invalid BSD-style input, e.g.,
echo 'MD5 (' | md5sum -c - Now, md5sum ignores that line.
sha1sum, sha224sum, sha384sum, and sha512sum are affected, too.
[bug introduced in coreutils-5.1.0]
- md5sum -c would accept a NUL-containing checksum string like "abcd\0..."
and would unnecessarily read and compute the checksum of the named file,
and then compare that checksum to the invalid one: guaranteed to fail.
Now, it recognizes that the line is not valid and skips it.
sha1sum, sha224sum, sha384sum, and sha512sum are affected, too.
[bug present in the original version, in coreutils-4.5.1, 1995]
- "mkdir -Z x dir" no longer segfaults when diagnosing invalid context "x"
mkfifo and mknod would fail similarly. Now they're fixed.
- mv would mistakenly unlink a destination file before calling rename,
when the destination had two or more hard links. It no longer does that.
[bug introduced in coreutils-5.3.0]
- "paste -d'\' file" no longer overruns memory (heap since coreutils-5.1.2,
stack before then) [bug present in the original version, in 1992]
- "pr -e" with a mix of backspaces and TABs no longer corrupts the heap
[bug present in the original version, in 1992]
- "ptx -F'\' long-file-name" would overrun a malloc'd buffer and corrupt
the heap. That was triggered by a lone backslash (or odd number of them)
at the end of the option argument to --flag-truncation=STRING (-F),
--word-regexp=REGEXP (-W), or --sentence-regexp=REGEXP (-S).
- "rm -r DIR" would mistakenly declare to be "write protected" -- and
prompt about -- full DIR-relative names longer than MIN (PATH_MAX, 8192).
- "rmdir --ignore-fail-on-non-empty" detects and ignores the failure
in more cases when a directory is empty.
- "seq -f % 1" would issue the erroneous diagnostic "seq: memory exhausted"
rather than reporting the invalid string format.
[bug introduced in coreutils-6.0]
- join now verifies that the inputs are in sorted order. This check can
be turned off with the --nocheck-order option.
- sort accepts the new option --sort=WORD, where WORD can be one of
general-numeric, month, numeric or random. These are equivalent to the
options --general-numeric-sort/-g, --month-sort/-M, --numeric-sort/-n
and --random-sort/-R, resp.
- id and groups work around an AFS-related bug whereby those programs
would print an invalid group number, when given no user-name argument.
- ls --color no longer outputs unnecessary escape sequences
- seq gives better diagnostics for invalid formats.
- install, mkdir, rmdir and split now write --verbose output to stdout,
not to stderr.Convert to use PLIST_VARS instead of manually passing "@comment "2008-04-12T22:42:57Zjlamjlam@pkgsrc.org2008-04-12T22:42:57Zurn:sha1:841dfa0e7aaa6a0f0cce2901291d1d938dd0fc0a
through PLIST_SUBST to the plist module.Conflict with sysutils/mktemp iff ${GNU_PROGRAM_PREFIX} == ""2008-03-08T01:09:50Ztnntnn@pkgsrc.org2008-03-08T01:09:50Zurn:sha1:cd15aa65a31d9b74202c5c8a0b344beefffd2ad5Update to coreutils-6.10.2008-03-08T01:06:52Ztnntnn@pkgsrc.org2008-03-08T01:06:52Zurn:sha1:db2fe5ff53206ec228c192c9240d5ea6216c2bee
New tools:
* gmktemp - GNU implementation of mktemp(1)
* gchcon - change the SELinux security context of a file
* gruncon - run a program in a different SELinux security context
Programs now default disabled by upstream (thus not installed):
* ghostname
* gsu (XXX: could make this a PKG_OPTION if requested)
Also assorted bugfixes.Standardize statvfs test. From Sergey Svishchev.2007-12-02T12:55:08Zwizwiz@pkgsrc.org2007-12-02T12:55:08Zurn:sha1:542e6193255e816eb34ea69f2995a5900b90dcf0Don't try to use ACLs under Mac OS X Leopard. acl_get_fd(3) return ENOENT2007-11-26T15:40:45Ztrontron@pkgsrc.org2007-11-26T15:40:45Zurn:sha1:4b7031b19df90c9b9c5e3ef5e9a34e1c8be58aec
all the time which causes "gcp" and "gmv" to complain a lot.
Bump package revision because of this fix.Simply check for Mac OS X Leopard.2007-11-26T09:35:39Ztrontron@pkgsrc.org2007-11-26T09:35:39Zurn:sha1:5321b4a2c48f12c29a7c00e5378bc9a1fa89d0b3Use work around from "bug-gnulib" mailing list to fix build problem2007-11-26T00:52:32Ztrontron@pkgsrc.org2007-11-26T00:52:32Zurn:sha1:6b9661cc2be1770843026eaa49b21909074bf207
under Mac OS X Leopard.Override the auto detection of a "thread-safe mkdir -p" (whatever that is)2007-07-19T09:07:43Ztrontron@pkgsrc.org2007-07-19T09:07:43Zurn:sha1:7e3aed184e4179f6a7fe0a920ff295d49f970798
to "${MKDIR}". "configure" will otherwise decide to use "gmkdir -p" if an
older version of the "coreutils" package is already installed. But during
the install stage the old "gmkdir" binary will have been removed by
"pkg_delete" and the installation fails.