New issue
Advanced search Search tips

Issue 877675 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 876634



Sign in to add a comment

samba: libdir is not being respected

Project Member Reported by vapier@chromium.org, Aug 24

Issue description

samba is installing into /usr/lib64 even on arm boards.  this is incorrect and is in turn breaking other packages (e.g. see  issue 876634 ).

there's two sets of files:
- /usr/lib64/perl5/vendor_perl/5.24.0/Parse/
- /usr/lib64/python2.7/site-packages/samba/

samba shouldn't be building+installing anything perl related.
the python path is also incorrect, but looks entirely unused (it's a single file).  so i guess that should be scrubbed.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 25

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/2e5578dc287121792b0c83b64b42851de47f31d8

commit 2e5578dc287121792b0c83b64b42851de47f31d8
Author: Mike Frysinger <vapier@chromium.org>
Date: Sat Aug 25 15:18:09 2018

samba: hack out python/perl when disabled

The samba build system is using the wrong libdir when installing
perl & python files, and it's installing these files even when we
have them disabled.  They're in turn breaking other python packages
due to the conflicting libdir usage.

Hack the files out of the install until we can figure out why the
build is broken.

BUG= chromium:876634 , chromium:877675
TEST=`emerge-nyan_big samba` doesn't install any perl or python files

Change-Id: I1f2488e96a47edf93a961ec30b1285ff1c161a2b
Reviewed-on: https://chromium-review.googlesource.com/1189002
Reviewed-by: Jason Clinton <jclinton@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>

[rename] https://crrev.com/2e5578dc287121792b0c83b64b42851de47f31d8/net-fs/samba/samba-4.8.0-r8.ebuild
[modify] https://crrev.com/2e5578dc287121792b0c83b64b42851de47f31d8/net-fs/samba/samba-4.8.0.ebuild

Cc: baileyberro@chromium.org
Will take a look at this one shortly for the underlying fix.

Sign in to add a comment