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

Issue 812528 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
akes...@chromium.org
vapier@chromium.org
█ jrbarnette@chromium.org
hidehiko@chromium.org
nya@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Packages depending on chromeos-ssh-testkeys are always rebuilt from source

Project Member Reported by nya@chromium.org, Feb 15 2018 
On building a test image, build_package forces to rebuild chromeos-ssh-testkeys package for SSH key uniqueness.

However this only affects two packages (chromeos-ssh-testkeys and debugd) so it's not a big loss.

Solution: Trigger rebuild of chromeos-ssh-testkeys only when USE=generated_ssh_key is enabled.

Comment 1 by nya@chromium.org, Feb 16 2018

Cc: jrbarnette@chromium.org
jrbarnette@ pointed out build-time dependency from debugd to chromeos-ssh-testkeys is strange, and I agree. While debugd actually references /usr/share/chromeos-ssh-config/keys, it should be a runtime dependency.

In fact, I tried:

$ emerge-cave --unmerge chromeos-ssh-testkeys
$ emerge-cave --nodeps debugd

and the build passed, so I believe we can update the dependency to avoid rebuild.

Comment 2 by vapier@chromium.org, Feb 16 2018 

it isn't uncommon for us to add deps to both DEPEND & RDEPEND w/out thinking about it.  in this case, the keys dep is only RDEPEND (you can look at the helpers to see how the files on the disk are used).
►

Sign in to add a comment