5485 – Cache wierdness in portage-2.0.17

Bug 5485 - Cache wierdness in portage-2.0.17

Summary: Cache wierdness in portage-2.0.17

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	6187
	Show dependency tree

Reported:	2002-07-23 19:53 UTC by Mark Guertin
Modified:	2011-10-30 22:18 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 Mark Guertin 2002-07-23 19:53:14 UTC

With portage-2.0.17 I was having problems pulling the proper version of
scrollkeeper, it was not finding 0.3.10-r1 even though was keyworded and not
masked (there was an error in the current cvs version of the scrollkeeper build,
2 sets of unmatched KEYWORDS).  I fixed this error, and did rm -rf
/var/cache/edb/dep/* , still no luck seeing the new build.

I commeneted line in package.mask with gnome-base/scrollkeeper, and I could then
see the newest build.  Commenting this line in packages.mask again and it still
let me see newest build.  Cache wierdness?

Comment 1 Daniel Robbins (RETIRED) gentoo-dev

2002-07-24 01:14:59 UTC

OK, this is due to a logic error in the xcache code.  I'm removing the xcache
for now and will revisit it later.  Should be totally fixed in portage 2.0.18.