Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

install -d/-D with -Z or --context relabels directories that already exist

Open
#15,332 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@abendrothj is already working on this.

Since Oct 14, 2026.

  • #15333 by @abendrothj — open

Assessment

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

Research direction

The bug is in the install utility's -Z/--context handling for -d and -D. Compare how it labels parent directories against GNU, which labels only the directories it creates, and check that an existing target is left alone. Pull request 15333 is already open against this issue, so review or build on it rather than starting a parallel fix. Done means that with a context set, only newly created directories get the label, verified with ls -Zd on a SELinux system or a test that checks the labels.

Written by the indexing model from the issue text.

Description

U - install

With -Z or --context, uutils install sets the context not only on the directories it creates but also on every existing parent of the target, up to and including / for an absolute path. GNU install labels only the directories it creates.

On Fedora with SELinux enforcing, as root (relative names keep this inside the current directory):

# mkdir -p /var/www/html/t/p && cd /var/www/html/t && restorecon -R .
# install -d --context=system_u:object_r:tmp_t:s0 p/n/a
# ls -Zd p p/n p/n/a

GNU coreutils 9.12: p keeps httpd_sys_content_t; p/n and p/n/a are tmp_t.

uutils main: all three are tmp_t.

install -d --context=... existing also relabels an existing target directory, which GNU leaves alone.

Dominant language
Rust
Stars
24.3k
Forks
2.1k
Avg merge
2d 1h
Merged PRs (30d)
327

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.