Please do not post in response to this email. Flames are neither
useful not appropriate. USEFUL information should be posted into
the bug to follow.
If a response is required please visit the following bug:
http://bugs.gentoo.org/show_bug.cgi?id=68443
Affected Platform: AMD64
Affected Requirement: FEATURES=sandbox
Initial Problem: Removal of sandbox library and binary.
Compounding Problems: Deletion of package files during update.
Most users will not be affected by this. Initial installs
may fail, and those having specifically enabled Sandbox on
AMD64 will be affected.
To determine if your machines are affected run emerge info
and view the FEATURES setting. If sandbox is listed, please
do the following: (It does no harm to do this anyway)
All AMD64 users are advised to do the following:
(Again, regardless of how recently this was done)
emerge sync
FEATURES=-sandbox emerge portage
The potential for portage to misbehave when interacting with
sandbox exists for 2.0.51_rc10 and 2.0.51 for anyone sync'ing
PRIOR to Thu Oct 21 18:14:09 UTC 2004.
Portage-2.0.51-r1 does not have this problem.
An oversight on my part, followed by coincidence, left sandbox
uninstalled on AMD64 with the original portage-2.0.51 ebuilds.
If sandbox is not enabled, this will go unnoticed. It appears
that due to profiles and other tree-affects, that sandbox is
disabled on most boxes but the full extent of that default
is not yet known.
UPDATE PORTAGE __AGAIN__ after sync'ing now. The potential
exists for portage to remove installed files without replacing
them with updated files when doing updates. MERGE PORTAGE FIRST
or disable sandbox.
--NJ
useful not appropriate. USEFUL information should be posted into
the bug to follow.
If a response is required please visit the following bug:
http://bugs.gentoo.org/show_bug.cgi?id=68443
Affected Platform: AMD64
Affected Requirement: FEATURES=sandbox
Initial Problem: Removal of sandbox library and binary.
Compounding Problems: Deletion of package files during update.
Most users will not be affected by this. Initial installs
may fail, and those having specifically enabled Sandbox on
AMD64 will be affected.
To determine if your machines are affected run emerge info
and view the FEATURES setting. If sandbox is listed, please
do the following: (It does no harm to do this anyway)
All AMD64 users are advised to do the following:
(Again, regardless of how recently this was done)
emerge sync
FEATURES=-sandbox emerge portage
The potential for portage to misbehave when interacting with
sandbox exists for 2.0.51_rc10 and 2.0.51 for anyone sync'ing
PRIOR to Thu Oct 21 18:14:09 UTC 2004.
Portage-2.0.51-r1 does not have this problem.
An oversight on my part, followed by coincidence, left sandbox
uninstalled on AMD64 with the original portage-2.0.51 ebuilds.
If sandbox is not enabled, this will go unnoticed. It appears
that due to profiles and other tree-affects, that sandbox is
disabled on most boxes but the full extent of that default
is not yet known.
UPDATE PORTAGE __AGAIN__ after sync'ing now. The potential
exists for portage to remove installed files without replacing
them with updated files when doing updates. MERGE PORTAGE FIRST
or disable sandbox.
--NJ