Bug 60561

Summary:	When not in PORTDIR repoman updates the wrong metadata.dtd file
Product:	Portage Development	Reporter:	Lisa Seelye (RETIRED) <lisa>
Component:	Repoman	Assignee:	Portage team <dev-portage>
Status:	RESOLVED INVALID
Severity:	minor
Priority:	High
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Lisa Seelye (RETIRED) gentoo-dev

2004-08-16 08:37:13 UTC

root@lisa /home/gentoo/portage-tree/sys-devel/distcc # repoman

We're not in PORTDIR... setting to: /home/gentoo/portage-tree

RepoMan scours the neighborhood...

*** the local copy of metadata.dtd needs to be refetched, doing that now

>>> Downloading http://www.gentoo.org/dtd/metadata.dtd
--11:27:50--  http://www.gentoo.org/dtd/metadata.dtd
           => `/usr/portage/distfiles/metadata.dtd'
Resolving www.gentoo.org... 198.63.211.235, 203.112.31.164
Connecting to www.gentoo.org[198.63.211.235]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2,713 [application/xml-dtd]

100%[====================================>] 2,713         --.--K/s             

11:27:55 (4.01 MB/s) - `/usr/portage/distfiles/metadata.dtd' saved [2713/2713]

See the snafu?


lisa@lisa ~ $ qpkg -I -v portage
sys-apps/portage-2.0.51_pre17 *
app-portage/gentoolkit-dev-0.2.0_pre3 *
app-portage/gentoolkit-0.2.0_pre8 *

Comment 1 Marius Mauch (RETIRED) gentoo-dev

2004-08-16 08:44:40 UTC

Not really, where is the problem ?

Comment 2 Lisa Seelye (RETIRED) gentoo-dev

2004-08-16 09:15:56 UTC

Shouldn't repoman update the .dtd in the overlay instead of the real portdir?

Comment 3 Brian Harring (RETIRED) gentoo-dev

2004-08-16 10:20:27 UTC

Actually, it fetches metadata.dtd to DISTDIR, then transfers it to portage.CACHE_PATH; /var/cache/edb/metadata.dtd being it's normal location- it's not tree specific at this point, since we don't bundle it w/ any trees :)