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 *
Not really, where is the problem ?
Shouldn't repoman update the .dtd in the overlay instead of the real portdir?
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 :)