40689 – portage 2.0.50: Sandbox violations for xpak.pyo in many emerges

Bug 40689 - portage 2.0.50: Sandbox violations for xpak.pyo in many emerges

Summary: portage 2.0.50: Sandbox violations for xpak.pyo in many emerges

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	Highest critical (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Duplicates (1):	40997 (view as bug list)
Depends on:
Blocks:

Reported:	2004-02-07 01:49 UTC by Klaus Kusche
Modified:	2004-02-10 23:39 UTC (History)
CC List:	1 user (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 Klaus Kusche 2004-02-07 01:49:31 UTC

After emerging portage 2.0.50, at least half of all emerges I try fail with the following sandbox violation:

--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-sys-libs_-_cracklib-2.7-r8-3623.log"

unlink:    /usr/lib/portage/pym/xpak.pyo
open_wr:   /usr/lib/portage/pym/xpak.pyo
--------------------------------------------------------------------------------

Among others, I got this error (always xpak.pyo) for cracklib, libtool, pam, pwdb, ...

The same packages emerge fine with portage 2.0.49-r21

Comment 1 Markus Rothe (RETIRED) gentoo-dev

2004-02-08 11:04:17 UTC

Same problem here while "emerge system" with official 1.4 live cd.

Markus

Comment 2 Nicholas Jones (RETIRED) gentoo-dev

2004-02-09 07:37:19 UTC

Fixed for portage-2.0.50-r1

Comment 3 Aron Griffis (RETIRED) gentoo-dev

2004-02-09 12:18:26 UTC

*** Bug 40997 has been marked as a duplicate of this bug. ***

Comment 4 Nicholas Jones (RETIRED) gentoo-dev

2004-02-10 23:39:33 UTC

comment #2