Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 648062 - sys-apps/portage: portageq repositories_configuration <eroot> does not override PORTAGE_CONFIGROOT
Summary: sys-apps/portage: portageq repositories_configuration <eroot> does not overri...
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Tools (show other bugs)
Hardware: All All
: Normal normal (vote)
Assignee: Portage team
Keywords: InVCS
Depends on:
Blocks: 651804
  Show dependency tree
Reported: 2018-02-18 23:19 UTC by Zac Medico
Modified: 2020-12-27 22:24 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Zac Medico gentoo-dev 2018-02-18 23:19:51 UTC
The `portageq repositories_configuration <eroot>` command is intended to query repository configuration for <eroot>, but it does not override the PORTAGE_CONFIGROOT variable internally, so the <eroot> parameter is essentially ignored.
Comment 1 Zac Medico gentoo-dev 2018-03-23 23:52:19 UTC
Setting PORTAGE_CONFIGROOT works well if the repository location settings refer to existing directories.

However, if the <eroot> parameter refers to a chroot, and the repository location settings valid only for a chrooted process, then RepoConfigLoader's repository location validation gives annoying results. It seems like portageq should probably disable the location validation, and simply allow the configuration to pass through as-is.
Comment 3 Larry the Git Cow gentoo-dev 2018-03-26 17:43:59 UTC
The bug has been referenced in the following commit(s):

commit 382f4be415394886026ccd5dcd08ca96ecda31fa
Author:     Zac Medico <>
AuthorDate: 2018-03-23 16:29:13 +0000
Commit:     Zac Medico <>
CommitDate: 2018-03-26 17:42:50 +0000

    portageq repos_config: fix <eroot> parameter (bug 648062)
    The <eroot> parameter is ineffective for commands that query
    configuration, since the PORTAGE_CONFIGROOT variable controls
    the location of configuration files. Therefore, for portageq
    repos_config, implicitly set PORTAGE_CONFIGROOT equal to the
    value of the <eroot> parameter. Note that this works correctly
    for both prefix and non-prefix systems, because both EROOT and
    PORTAGE_CONFIGROOT are supposed to include the EPREFIX offset.

 bin/portageq | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)}
Comment 4 Zac Medico gentoo-dev 2018-07-02 18:44:15 UTC
Fixed in portage-2.3.40-r1.