521784 – sys-apps/kmod-18-r1.ebuild: Aug 29 update broke emerge --root

Bug 521784 - sys-apps/kmod-18-r1.ebuild: Aug 29 update broke emerge --root

Summary: sys-apps/kmod-18-r1.ebuild: Aug 29 update broke emerge --root

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	Normal major (vote)
Assignee:	udev maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-08-30 22:52 UTC by kipeta
Modified:	2014-11-13 05:25 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description kipeta 2014-08-30 22:52:27 UTC

If I run emerge --root=/target/root kmod using the latest (Aug 29) kmod-18-r1.ebuild, the files will be installed to /target/root/target/root directory not to /target/root.

Reproducible: Always

Steps to Reproduce:
1. emerge --root=/target/root =sys-apps/kmod-18-r1
2. 
3.
Actual Results:  
...
Some file are installed into wrong directory:
/target/root/target/root/lib64/libkmod.so.2
/target/root/target/root/lib64/libkmod.so.2.2.8
/target/root/target/root/bin/kmod



This happens at least in both amd64 and x86 environment.

I would assume that all versions of kmod ebuild have the same problem because the similar change seemed to be made on all of them

Comment 1 Mike Gilbert gentoo-dev

2014-09-03 15:08:53 UTC

This was probably fixed yesterday.

  02 Sep 2014; Richard Yao <ryao@gentoo.org> kmod-16.ebuild, kmod-17.ebuild,
  kmod-18-r1.ebuild, kmod-18.ebuild, kmod-9999.ebuild:
  src_configure() should use EPREFIX, not EROOT. The previous commit was not
  correct from the perspective of Catalyst. Thanks goes to Arfever for pointing
  it out.