Skip to content

ci: install adduser explicitly in package-arch test step#4017

Closed
grandixximo wants to merge 1 commit into
LinuxCNC:masterfrom
grandixximo:ci-install-adduser
Closed

ci: install adduser explicitly in package-arch test step#4017
grandixximo wants to merge 1 commit into
LinuxCNC:masterfrom
grandixximo:ci-install-adduser

Conversation

@grandixximo
Copy link
Copy Markdown
Contributor

Summary

The package-arch Test debian packages step calls eatmydata adduser ... testrunner to set up a non-root user for runtests, but never installs the adduser package. It used to work because adduser was pulled transitively via Recommends of the installed .deb files; sid no longer pulls it, so builds fail with:

E: eatmydata: unable to find 'adduser' in PATH
##[error]Process completed with exit code 1.

Surfaced today on PR #3999 (all six package-arch jobs across bookworm/trixie/sid x amd64/arm64 failed). Same failure mode reproduces on rerun, so this is not transient.

Fix

Add adduser to the existing apt-get install sudo line so the testrunner setup does not depend on a fragile Recommends chain.

Test plan

The test step runs 'eatmydata adduser ... testrunner' but never
installs adduser. It was pulled transitively via Recommends on the
installed .deb files; sid no longer pulls it, so builds fail with
'eatmydata: unable to find adduser in PATH'. Add it to the existing
sudo install so testrunner setup does not depend on Recommends.
@BsAtHome
Copy link
Copy Markdown
Contributor

This conflicts with #3984, which is the one that should go in.

You'll have to rebase when I do...

@grandixximo grandixximo deleted the ci-install-adduser branch May 11, 2026 13:16
@BsAtHome
Copy link
Copy Markdown
Contributor

If you could be so kind, I think you need to re-apply this but to 2.9 branch. There the CI is not going to be upgraded and it fails with the same error.

@grandixximo
Copy link
Copy Markdown
Contributor Author

I was about to text you about it, just realized I need this on 2.9 for #4015

@grandixximo
Copy link
Copy Markdown
Contributor Author

@BsAtHome I did it as #4018 but it fails cause of GitHub now...

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.

2 participants