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

Issue 807777 link

Starred by 2 users
Status: Verified
Owner:
vapier@chromium.org
Closed: Feb 2018
Cc:
llozano@chromium.org
█ ravisadineni@chromium.org
abhishekbh@chromium.org
█ jkop@chromium.org
vapier@chromium.org
newcomer@chromium.org
█ rahulchaudhry@chromium.org
manojgupta@chromium.org
cmt...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

wireshark fails to build in SDK builder

Project Member Reported by manojgupta@chromium.org, Jan 31 2018 
https://uberchromegw.corp.google.com/i/chromiumos/builders/chromiumos-sdk/builds/8483

wireshark-1.10.5-r4: >>> Installing (1 of 1) net-analyzer/wireshark-1.10.5-r4::chromiumos
wireshark-1.10.5-r4: chown: invalid group: '0:wireshark'
wireshark-1.10.5-r4:  * ERROR: net-analyzer/wireshark-1.10.5-r4::chromiumos failed (postinst phase):
wireshark-1.10.5-r4:  *   (no error message)

Suspect that it started after portage upgrade:
https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/815597

I am not sure what is the right fix here so assigning to vapier@.

Comment 1 by manojgupta@chromium.org, Feb 1 2018

Cc: abhishekbh@chromium.org newcomer@chromium.org ravisadineni@chromium.org jkop@chromium.org
Components: OS>Packages
Labels: -Build-Toolchain
Suspect that bsdiff fail is also because of portage upgrade. I did the following experiment:

In a newly synced chroot that still had portage 2.12:
$ sudo emerge bsdiff -> works.
$ sudo emerge portage -> upgrade portage to 2.28
$ sudo emerge bsdiff -> fails.

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

the wireshark ebuild has always been broken it looks like.  no one noticed because in previous portage versions, failures in pkg_postinst were ignored.  the ebuild references the "wireshark" group but never actually creates it.

Comment 3 by manojgupta@chromium.org, Feb 1 2018 

Thanks Mike, any idea about bsdiff?

Comment 4 by vapier@chromium.org, Feb 1 2018 

bsdiff is failing because, while platform2 has already been fixed, it's a blacklisted ebuild pointing to an old platform2 w/out the fix.
  https://chromium-review.googlesource.com/815616

Comment 5 by jkop@chromium.org, Feb 1 2018 

Why is it blacklisted? Can this be fixed manually?

Comment 6 by akes...@chromium.org, Feb 1 2018

Labels: -Pri-1 Pri-0
CQ breaking on this repeatedly.

https://luci-milo.appspot.com/buildbot/chromeos/master-paladin/17633

Comment 7 by vapier@chromium.org, Feb 1 2018

Labels: -Pri-0 Pri-1
Status: Fixed (was: Untriaged)
the fix has already landed at this point and bots cycled green

Comment 8 by manojgupta@chromium.org, Feb 3 2018

Status: Verified (was: Fixed)
►

Sign in to add a comment