50310 – emerge -B fails silently on path errors

Bug 50310 - emerge -B fails silently on path errors

Summary: emerge -B fails silently on path errors

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	Bug

Depends on:
Blocks:

Reported:	2004-05-06 20:43 UTC by Joel Hill (RETIRED)
Modified:	2005-08-10 15:56 UTC (History)
CC List:	0 users

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 Joel Hill (RETIRED) gentoo-dev

2004-05-06 20:43:08 UTC

it will complete without errors but the file will be nowhere to be found

Comment 1 Mr. Bones. (RETIRED) gentoo-dev

2004-05-06 23:22:46 UTC

use the summary for the summary and the bug report for filling out the
details of the bug report please.  Makes it easier to read for everyone involved.

Comment 2 Nicholas Jones (RETIRED) gentoo-dev

2004-05-16 03:52:13 UTC

rmdir /usr/portage/packages/All
emerge -B something


succeeds, but doesn't yield a binary.

Comment 3 Zac Medico gentoo-dev

2005-08-10 15:29:40 UTC

Apparently this has been fixed for some time now.  With portage-2.0.51.22-r2 you
can do "PKGDIR=/tmp/foo/bar emerge --buildpkgonly foo" and it creates
/tmp/foo/bar/All automatically.

Hypothetically, if "${PKGDIR}/All" does not exist for some reason, ebuild.sh
will die:

mv "${PF}.tbz2" "${PKGDIR}/All" || die "Failed to move tbz2 to ${PKGDIR}/All"

Comment 4 Alec Warner (RETIRED) archtester

2005-08-10 15:56:04 UTC

if both ${PKGDIR} or ${PKGDIR}/All are missing, they will be recreated prior to 
the binary package being moved there.  Fixed on or before portage-2.0.51.22-r2.