tself" but wc is
saying that it is, no?
Sorry if this has already been done to death. My search of the archives
failed to find a previous discussion but perhaps I missed them.
Thanks
--
Nick
Asunción 12:04 PYST ► 37°C ◆ nubes ◆ 3Km/h NE ◆ 52% HR
El 2024-03-11 14:33 PYST, Pádraig Brady escribió:
> On 10/03/2024 15:16, Nick wrote:
> > Markus Kuhn's FAQ says "A combining character is not a full
> > character by itself" but wc is saying that it is, no?
> It's a fair point. Libre Office for example wil
* init.cfg (gcc_shared_): -ldl has to be positioned after the object
files that may rely upon it. (Fixes tests/cp/nfs-removal-race.sh.)
---
init.cfg | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init.cfg b/init.cfg
index 725ee12..3e74e87 100644
--- a/init.cfg
+++ b/init.cfg
Here's the FAIL output. (Note that despite the name,
/usr/local/share/compiler-nfs is not nfs-mounted, but is an
xattr-capable ext4 filesystem which I pointed the testsuite at after
getting a similar failure on tmpfs.)
This is with kernel 3.16.3 and libattr current as of commit
55f39ef1ddec924d746
On 2 Oct 2014, Pádraig Brady stated:
> On 10/02/2014 03:26 PM, Nick Alcock wrote:
>> - $CC -Wall -shared --std=gnu99 -fPIC -ldl -O2 $* "$in" -o "$out"
>> + $CC -Wall -shared --std=gnu99 -fPIC -O2 $* "$in" -o "$out" -ldl
>
> I cou
On 2 Oct 2014, Pádraig Brady stated:
> On 10/02/2014 04:59 PM, Nick Alcock wrote:
>> Here's the FAIL output. (Note that despite the name,
>> /usr/local/share/compiler-nfs is not nfs-mounted, but is an
>> xattr-capable ext4 filesystem which I pointed the testsuite at
On 3 Oct 2014, Nick Alcock uttered the following:
> I'll be digging into libattr next. Looks like it's not doing what it was
> asked to do... and coreutils's testsuite was the first thing to spot it.
> You can tell I don't use xattrs much :)
Confirmed, this is a tr
Mike's build-system-revamping commit 9ce21bd of January this year
accidentally dropped a crucial -include of "libattr.h". This silently
undefined the HAVE_F*ATTR macros, causing attr_copy_{fd,file}.c to think
that xattrs are not supported and to compile the functions in those
files into a 'return 0
responding update to the ENXIO description:
... or the whence argument is SEEK_DATA and the offset falls beyond
the last byte not within a hole.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
This test requires an unwritable input and an unreadable output,
so will fail if the testsuite is being run as root, and should
not be run in this case.
---
tests/misc/sort-exit-early | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/misc/sort-exit-early b/tests/misc/sort-exit-early
inde
On 30 Aug 2012, Jim Meyering uttered the following:
> A word of caution:
>
> There have been exploitable flaws (albeit rare) in these tests over
> the years, and if you had regularly run all of them as root on a shared
> system, it might have been easy to exploit. The root-only tests are
> more c
Similarly to the fix to tests/rmdir/ignore.sh in c0e5f8c59,
tee should not be expected to fail when run with read-only outputs
when run as root.
* tests/rmdir/ignore.sh: Add uid_is_privileged_ guard around test for
read-only outputs.
---
tests/misc/tee.sh | 8 +---
1 file changed, 5 insertion
On 21 Mar 2023, Pádraig Brady stated:
> I'll update release procedure to do a test run as root
> (which is unusual / ill-advised TBH).
Oh! I do it routinely because at one point coreutils maintainers were
asking for people to do it more often -- and because if there is
anything whose component too
13 matches
Mail list logo
