New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 874145 link

Starred by 1 user

Issue metadata

Status: Closed
Owner:
Last visit > 30 days ago
Closed: Aug 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Emerging app-accessibility/brltty fails on EVE

Project Member Reported by vmreyes@google.com, Aug 14

Issue description

While trying to build packages for Eve, my build failed at app-accessibility/brltty.

I have attached the log, which suggests an error with adding a new user during pre-inst.

I do not have changes that would affect this behavior. I have tried to find the eclass that contains the command that is giving me trouble, enewuser, but I cannot find it in portage-stable or chromiumos-overlay. It seems to be in the user.eclass, but I cannot find that file. 
 
brltty.log
272 KB View Download
Cc: vapier@chromium.org
Labels: allpublic
you can try manually deleting the brltty accounts from /build/eve/etc/{group,passwd} and see if emerge works
I checked the contents of /build/eve/etc/{group, passwd} and both are empty. It seems that it may be trying to run the command in reference to the host; the host has brltty in /etc/group. 
brltty accounts shouldn't be in the SDK.  you might have emerged things while testing in such a way that caused them to be created, but that's not normal.

you can hand delete them from the SDK too.
Looks like it was some sort of chroot/environment error. Fixed it after cloning the repo again and creating a new chroot.
Thanks!
Status: Closed (was: Unconfirmed)

Sign in to add a comment