Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@matttbe
Copy link
Contributor

@matttbe matttbe commented Nov 6, 2025

Compared to the GNU Coreutils timeout usage menu and man page, some parts were missing here:

  • What the <duration> and <command> arguments stand for.

  • Which signal is being sent by default.

  • What the different exit status are.

All the new descriptions are coming from the GNU Coreutils project, except the one for <command> which is a new one.

French translations are also provided. (I am a French native speaker.)

Compared to the GNU Coreutils timeout usage menu and man page, some
parts were missing here:

 - What the <duration> and <command> arguments stand for.

 - Which signal is being sent by default.

 - What the different exit status are.

All the new descriptions are coming from the GNU Coreutils project,
except the one for <command> which is a new one.

French translations are also provided. (I am a French native speaker.)

Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
@matttbe
Copy link
Contributor Author

matttbe commented Nov 6, 2025

I don't think the two failing tests are due to my modifications:

Run limactl start --plain --name=default --cpus=4 --disk=40 --memory=8 --network=lima:user-v2 template://fedora
time="2025-11-06T12:35:38Z" level=warning msg="Template locator \"template://fedora\" should be written \"template:fedora\" since Lima v2.0"
time="2025-11-06T12:35:38Z" level=fatal msg="template \"_images/fedora-43.yaml\" not found"

It looks like there is an attempt to fix them in PR #9159.

@AkihiroSuda
Copy link

Could you try closing and reopening the PR to retrigger the CI?
The regression should have been fixed in https://github.com/lima-vm/lima/releases/tag/v2.0.1

@matttbe matttbe closed this Nov 6, 2025
@matttbe matttbe reopened this Nov 6, 2025
@cakebaker cakebaker merged commit 0058316 into uutils:main Nov 6, 2025
239 of 241 checks passed
@cakebaker
Copy link
Contributor

Thanks for your PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants