chfn, chsh: print a line on stderr after a successful change
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
Research direction
Start by locating the success paths for chfn and chsh and compare their stderr output with GNU shadow 4.17.4. Reproduce the reported commands (chfn -f N alice and chsh -s /bin/bash alice) and inspect the relevant tests. Done when successful changes no longer print the reported lines to stderr and the tests cover both commands.
Written by the indexing model from the issue text.
Description
GNU chfn and chsh (shadow 4.17.4) print nothing when the change succeeds. shadow-rs prints
chfn: changed user 'alice' information
chsh: shell changed for 'alice'
on stderr after every successful run (chfn -f N alice, chsh -s /bin/bash alice). Scripts and config tools that treat output on stderr as a warning or failure see one on every call.
GNU shadow 4.17.4 (Ubuntu 26.04). shadow-rs main f913109.
- Dominant language
- Rust
- Stars
- 17
- Forks
- 10
- Avg merge
- 18h 30m
- Merged PRs (30d)
- 24
Getting set up
- Ships a 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/shadow
-
groupmod -U: members change in /etc/group but not in /etc/gshadowPossibly taken @jayhemnani9910 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
usermod: -r/--remove is not acceptedPossibly taken @jayhemnani9910 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
pwck: warnings and "no changes" on clean files, nothing after problemsPossibly taken @jayhemnani9910 claimed this 1 day ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 54/100
Maintainers usually reply within 1 day
Similar issues
-
build.yml: macOS arm64 DMG fails, cargo missing on the macos-26 runner imagePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
getopenscreen/openscreen#1423 ·
Maintainers usually reply within 1 day
-
bug good first issue python
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug: remove the "not stable yet" warning from DataReplacement commitsPossibly taken @lance-gatefixer claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
lance-format/lance#10433 ·
Maintainers usually reply within 3 days
-
vorbis: Inverse coupling runs in wrong orderPossibly taken @computerfan claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100