chown -v: `+ID` spec echoed verbatim on a broken symlink
Maintainers usually reply within 1 day
@sunsss123soldier is already working on this.
Since Nov 16, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 80/100
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
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
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uutils/coreutils
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
U - shred
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
dircolors: --csh doesn't escape `!`Possibly taken @majidninja claimed this 2 days ago. Opengood first issue oss-scanner U - dircolors
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
uutils/coreutils#16496 · 1 comment ·
Maintainers usually reply within 1 day
-
dircolors: directory operand exits 2 with a custom message, GNU prints 'read error: Is a directory' and exits 1Possibly taken @emirmrkaljevic claimed this 3 days ago. OpenU - dircolors
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
test_hostid.rs lacks test cases with frozen ip addr e.g. unshare -ru sh -c "hostname 127.0.0.1 && hostid"Possibly taken @costajohnt claimed this 3 days ago. OpenU - hostid
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
All issues in uutils/coreutils
Similar issues
-
ai_p2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ClickHouse/ClickHouse#132519 ·
Maintainers usually reply within 1 day
-
Pattern-clip compiler tests miss the clip cap, sort order, muted output and count/emit agreementOpenarea: engine type: test
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
YuriiMurha/grooviq#224 ·
Maintainers usually reply within 1 day
-
state:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
zed-industries/zed#67109 · 1 comment ·
Maintainers usually reply within 1 day
-
bug priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
storytold/photocraft#15500 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day