ot attempt to copy the file in this case (since the file is
not newer than itself) and cp would return a true exit status.
--
Ed Avis <[EMAIL PROTECTED]>
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
t programs and the actual list do-not-install-by-default
# programs, modify the former variable to reflect any "do-install" and
--
Ed Avis <[EMAIL PROTECTED]>
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
should not be required when building from a tarball,
>so its absence shouldn't make configure fail.
OK, that's another thing better checked in the bootstrap script.
--
Ed Avis <[EMAIL PROTECTED]>
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
With current coreutils source from git, one test fails on my machine. It is a
Fedora 9 box with a few Windows filesystems mounted. Here is the tests/test-
suite.log.
===
GNU coreutils 7.0.5-42df6-dirty: tests/test-suite.log
=
ne per line and then have something like
if test -e bootstrap.required_progs; then
for p in `cat bootstrap.required_progs`; do
if ! $p --help >/dev/null; then
echo You must install $p
exit 1
fi
done
done
Autodetecting them seems a bit
pyright waiver from my employer so I would need to get
that sorted out. It may be easier for you to just note the list of programs I
mentioned and write the few lines of shell script yourself. However, I will
see if I can get the legal side fixed.
--
Ed Avis <[EMAIL PROTECTED]>
__
want to do that, please update the help text and info
documentation to make it clear that the 'a' format maps high-bit-set
characters onto the same output as ASCII, and so probably isn't what
you want if you are trying to see what characters a byt
ot tell ls to avoid colorization, just to
use the default colour scheme.
--
Ed Avis <[EMAIL PROTECTED]>
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
n7\n8\n9\n0", "1\n2\n3\n4\n5\n6\n7\n8\n9\n0", 0],
+['eof-4', '-V', "1\n2\n3\n4\n5\n6\n7\n8\n9\n0\n", "1\n2\n3\n4\n5\n6\n7\n8\n9\n0\n",
0],
+# This requires the right locale - hope that's okay.
+['eof-5', '-V', "1\n2\n3\n4\n5\n6\n7\n8\n9\n0\n1",
+ "1\n2\n3\n4\n5\n6\n7\n8\n9\n0\n==> truncated ./eof-5.I <==\n", 0],
+['eof-6', '-V', "1\n2\n3\n4\n5\n6\n7\n8\n9\n0\n1\n",
+ "1\n2\n3\n4\n5\n6\n7\n8\n9\n0\n==> truncated ./eof-6.I <==\n", 0],
+# Test -V with --bytes.
+['eof-7', '-V --bytes 3', "12", "12", 0],
+['eof-8', '-V --bytes 3', "123", "123", 0],
+['eof-9', '-V --bytes 3', "1234", "123\n==> truncated ./eof-9.I <==\n", 0],
+['eof-10', '-V --bytes 3', "12345", "123\n==> truncated ./eof-10.I <==\n", 0],
);
sub test_vector
--
Ed Avis <[EMAIL PROTECTED]>
___
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-coreutils
On 10 Aug 2003, Paul Eggert wrote:
>>% (unset TZ; date +%z)
>>+0100
>>% (TZ= date +%z)
>>+
>This is a C library issue, not a coreutils issue, since coreutils
>simply repeats what the C library tells it.
What does POSIX say about date(1) and the TZ variable?
--version
date (coreutils) 5.0
Written by David MacKenzie.
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
--
Ed Avis <[EMAIL PROTEC
g to move any files, and
the simplest way to do that would be to ask mv: if I did run you, what
files would you move?
Of course if --dry-run succeeds it would not be guaranteed that a
following real run of mv or cp would produce the same results, but it
would be good enough.
--
Ed Avi
t would take all measures necessary.
After all, rm -f doesn't care about permissions on files before
removing them, so shouldn't it work equally well with directories?
Even if it does have to chmod u+rx them behind the scenes.
% rm --version | head -1
rm (coreutils)
r a new flag
-F, --really-force
As --force but also change permissions if necessary.
--
Ed Avis <[EMAIL PROTECTED]>
___
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-coreutils
le you own due to e.g., an ACL, attributes a la
>chattr,
I expect that as such things are found they could be added to the -F
code, so it becomes a general 'do everything possible to remove the
file'.
>or being on file system that's mounted read-only.
Hmm, well I wouldn
e to suggest this feature was not that I had
chmodded files to deliberately stop them being removed. It was just a
slightly odd tarball (not generated on a Unix system, I expect) which
created a directory lacking execute permission. Then I tried to use
rm to clean up, and was
They'd have
>to handle failed chdir, opendir, readdir and retry after a chmod.
Well - that's one way to do it, the other way is to chmod every file
before doing anything with it. But that might be slow (I haven't
benchmarked).
--
Ed Avis <[EMAIL PROTECTED]>
___
ore doing anything
with it, and by 'doing anything' I meant either removing it or
preparing to remove it.
--
Ed Avis <[EMAIL PROTECTED]>
___
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-coreutils
;different model of the filesystem than the one that actually exists.
Agreed. But it's too late to change now.
>>FWIW - what prompted me to suggest this feature was not that I had
>>chmodded files to deliberately stop them being removed. It was
>>just a slightly odd tarba
x27;>d') or die "d: $!\n"}};
sub make_j_d ()
{
@@ -85,6 +86,9 @@
{OUT => "\e[0m\e[01;[EMAIL PROTECTED]"},
$slink_d, $unlink_d],
+ # A listing with only plain files should have no color sequences at all.
+ ['no-color', '--color=always d', {OUT => "d\n"}, $creat_d, $unlink_d],
+
# Test for a bug that was introduced in coreutils-4.5.4; fixed in 4.5.5.
# To demonstrate it, the file in question (with executable bit set)
# must not be a command line argument.
--
Ed Avis <[EMAIL PROTECTED]>
___
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-coreutils
-5.2.0-new/ChangeLog 2004-02-22 13:36:13.163611440 +
@@ -1,3 +1,11 @@
+2004-02-22 Ed Avis <[EMAIL PROTECTED]>
+
+ * src/ls.c: ordinary files are written with no ANSI escape
+ sequences, even with --color. The escape sequence to reset the
+ terminal is not output
ct sense. So when I check out of CVS, am I getting a
slightly different code base from what goes into the tarballs?
--
Ed Avis <[EMAIL PROTECTED]>
___
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-coreutils
y `/home/ed/cvs_working/coreutils/po'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/ed/cvs_working/coreutils'
make: *** [all] Error 2
If you want I can send the whole build log, config.log and so on. I
am running Red Hat Linux 9 but with some updated packages including
co
l gettext.
>>But shouldn't the configure script have a 'checking for gettext'
>>stage?
>
>It does, that's why xgettext is not called.
Is it a bug that coreutils would not build after configuring? I
expected that if an important co
No such file or directory
FAIL: date-tests
==
1 of 1 tests failed
Please report to [EMAIL PROTECTED]
==
make[3]: *** [check-TESTS] Error 1
I am not sure what generates that file or why it is missing; it seems
to be Test.pm but ho
ils/po'
>>: --default-domain=coreutils --directory=.. \
>
>You need to install gettext.
OK, I'll try that. But shouldn't the configure script have a
'checking for gettext' stage?
--
Ed Avis <[EMAIL PROTECTED]>
ory not empty').
Note that Emacs command completion (in shell-mode) will complete foo to foo/.
--
Ed Avis
s.
But out of interest,
"If the path argument refers to a path whose final component
is either dot or dot-dot, rmdir() shall fail."
Does POSIX document the error status that should be returned in these cases?
--
Ed Avis
ht not always be the same thing as foo.
How about this: if foo/. has the same inode number as foo then rmdir proceeds.
If not, it prints an error a bit more helpful than 'Invalid argument'.
--
Ed Avis
;t remove . or ..", since the user did
not ask to remove the current directory.)
--
Ed Avis
30 matches
Mail list logo
