bug#61530: sha256sum check single file in a mutiple sha sum text file

tag 61530 notabug close 61530 stop On 2/15/23 14:28, Andreas Löw wrote: Hello, I want to check a single file for correct sha256. All the files of my directory are included in a sha256 text file named allsha256. The sha256sum always checks all files included in the allsha256 fil

bug#61386: [PATCH] cp,mv,install: Disable sparse copy on macOS

> On 2023-02-15, at 9:48 PM, Paul Eggert wrote: > > On 2023-02-15 07:26, George Valkov wrote: >> I tested your patch: both overwrite existing and clone to new produce a >> working copy. Here are the test results: >> https://httpstorm.com/share/.openwrt/test/2023-02-06_coreutils-9.1/test-04-cf8

bug#61386: [PATCH] cp,mv,install: Disable sparse copy on macOS

> On 2023-02-15, at 9:26 PM, Paul Eggert wrote: > > On 2023-02-15 06:05, George Valkov wrote: >> gcc d.c && ./a.out >> src 3 dst 4 >> c 14053376 p 20344832 h 20344832 d 6291456 >> total bytes copied 14053376 / 27551296 > > Thanks, this is due to a known incompatibility in macOS lseek that c

bug#61386: [PATCH] cp,mv,install: Disable sparse copy on macOS

On 2023-02-15 07:26, George Valkov wrote: I tested your patch: both overwrite existing and clone to new produce a working copy. Here are the test results: https://httpstorm.com/share/.openwrt/test/2023-02-06_coreutils-9.1/test-04-cf80f988eeb97cc3f8c65ae58e735d36f865277b-clone.txt I see some te

bug#61386: [PATCH] cp,mv,install: Disable sparse copy on macOS

On 2023-02-15 06:05, George Valkov wrote: gcc d.c && ./a.out src 3 dst 4 c 14053376 p 20344832 h 20344832 d 6291456 total bytes copied 14053376 / 27551296 Thanks, this is due to a known incompatibility in macOS lseek that coreutils is supposed to work around. See

bug#61537: [Bug-coreutils] 'cp -au' re-copies (removes and relinks) hard links that are up to date

Hello. I have been forced recently to update my coreutils 8.11 (because 'touch' in 8.11 didn't understand the dates with a 'T' separator passed to it by the configure of another GNU package I was installing) and have found that 'cp -au' now re-copies (removes and relinks) hard links that are u

bug#61386: [PATCH] cp,mv,install: Disable sparse copy on macOS

> On 2023-02-15, at 12:56 PM, Paul Eggert wrote: > > The disabling SEEK_HOLE on Apple is OK if a release is imminent. Otherwise > I'd like to get to the bottom of it first. This can be done by having George > use dtrace or (if that's not possible) adding debugging printfs. Hi Paul! Sure, sen

bug#61530: sha256sum check single file in a mutiple sha sum text file

Hello, I want to check a single file for correct sha256. All the files of my directory are included in a sha256 text file named allsha256. The sha256sum always checks all files included in the allsha256 file, even if I write: sha256sum myfile -c allsha256 It reports a warni

bug#61386: [PATCH] cp,mv,install: Disable sparse copy on macOS

> On 2023-02-14, at 2:12 PM, Pádraig Brady wrote: > > On 14/02/2023 06:12, Paul Eggert wrote: >> On 2023-02-13 09:16, George Valkov wrote: >>> 1. We apply my original patch to disable sparse-copy on macOS. Otherwise >>> since fclonefileat is not used whenever we overwrite a file, corruption >>

bug#61386: [PATCH] cp,mv,install: Disable sparse copy on macOS

Attached is an updated proposal for the fclonefileat patch. CVE-2021-30995 confirmed my suspicion that coreutils 9.1 and the current bleeding-edge coreutils on Savannah both have an exploitable security bug on macOS. Although I hope this patch fixes the bug, it could use more pairs of eyes, gi

bug#61386: [PATCH] cp,mv,install: Disable sparse copy on macOS

On 14/02/2023 19:02, Paul Eggert wrote: On 2023-02-14 04:12, Pádraig Brady wrote: I suspect it's a similar issue to the one that openzfs had: https://github.com/openzfs/zfs/issues/11900 Yes, quite likely. Given how closed / uncommunicative Apple are in general and specifically for this alr

bug#61528: date doesn't parse negative years

Hello, I noticed that date doesn't accept negative years, such as in the date: -0001-01-02 (i.e. 2nd Jan 2 BC). It's also somewhat puzzling that even through date will convert a timestamp in that year to an output string, it won't parse that string as valid (i.e. the last 2 lines below). d