chown -v: `+ID` spec echoed verbatim on a broken symlink

Open Beginner friendly
#16,500 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@sunsss123soldier is already working on this.

Since Nov 16, 2026.

  • #16545 by @sunsss123soldier — open
  • #16611 by @Rajpal14 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
80/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
cli

Research direction

The verbose message is built in traverse in src/uucore/src/lib/features/perms.rs from raw_owner; the parsed owner/group IDs should be printed instead. Read the spec-parsing path that turns +1000 and :+1000 into IDs so you can tell when only a group was given, then reuse those parsed values. Run cargo test --features unix --test tests -- --ignored test_chown::test_chown_verbose_broken_symlink_plus_ids (from #16493) and compare with GNU chown; done when the message shows 1000 and says "group" for the group-only case.

Written by the indexing model from the issue text.

Description

good first issue oss-scanner U - chown

GNU coreutils master prints the parsed IDs in this message, and says "group" when only a group is given.

$ ln -s absent ghost
$ chown -v +1000 ghost     # uutils: ... to +1000     GNU: ... to 1000
$ chown -v :+1000 ghost    # uutils: failed to change ownership of 'ghost' to :+1000
                           # GNU:    failed to change group of 'ghost' to 1000

See traverse in src/uucore/src/lib/features/perms.rs (uses raw_owner).

Test added in #16493: cargo test --features unix --test tests -- --ignored test_chown::test_chown_verbose_broken_symlink_plus_ids

Dominant language
Rust
Stars
24.4k
Forks
2.2k
Avg merge
3d 6h
Merged PRs (30d)
434

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from uutils/coreutils

All issues in uutils/coreutils

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.