| Summary: | sys-apps/portage-2.2.7 - portage.tests.dbapi.test_fakedbapi.TestFakedbapi fails: portage.exception.PermissionDenied: /etc/portage/make.conf | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Toralf Förster <toralf> |
| Component: | Unclassified | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | prefix |
| Priority: | Normal | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 484436 | ||
| Attachments: |
sys-apps:portage-2.2.7:20131130-095326.log.gz
First patch including debug output |
||
|
Description
Toralf Förster
2013-11-30 10:10:15 UTC
Created attachment 364474 [details, diff]
First patch including debug output
@prefix: Please take a look at the patch.
The change in LocationsManager.py seems pretty obvious and fixes the reported test failure. But then tests/emerge/test_simple.py starts to fail. It complains that the directory EPREFIX is to in some test cases, does not exist. I added code to create it and to create make.profile.
Now the test fails with: emerge: there are no ebuilds to satisfy "dev-libs/A" for /tmp/tmpxQzKMD/cross_prefix/.
@prefix: I don't know how the EPREFIX stuff is intended to work. Could you give me some pointers? Should it see the ebuilds from the "host" system or not? Do you agree with other changes I made so far?
(In reply to Sebastian Luther (few) from comment #1) > Created attachment 364474 [details, diff] [details, diff] > First patch including debug output > > @prefix: Please take a look at the patch. > > The change in LocationsManager.py seems pretty obvious and fixes the > reported test failure. But then tests/emerge/test_simple.py starts to fail. > It complains that the directory EPREFIX is to in some test cases, does not > exist. I added code to create it and to create make.profile. > > Now the test fails with: emerge: there are no ebuilds to satisfy > "dev-libs/A" for /tmp/tmpxQzKMD/cross_prefix/. > > @prefix: I don't know how the EPREFIX stuff is intended to work. Could you > give me some pointers? Should it see the ebuilds from the "host" system or > not? Do you agree with other changes I made so far? user_config_dir = os.path.join(os.sep, eprefix, USER_CONFIG_PATH) looks strange to me, because eprefix should start with /? The locationamanager change, I thought only Prefix branch used the portage.const.EPREFIX hack, so what branch is this patch for? (In reply to Fabian Groffen from comment #2) > The locationamanager change, I thought only Prefix branch used the > portage.const.EPREFIX hack, so what branch is this patch for? It's for master. (In reply to Sebastian Luther (few) from comment #3) > (In reply to Fabian Groffen from comment #2) > > The locationamanager change, I thought only Prefix branch used the > > portage.const.EPREFIX hack, so what branch is this patch for? > > It's for master. The debug stuff should be removed from the patch - debug = False + debug = True and all the commented out code to make it easier to see what's what. I have a patch in this branch: https://github.com/zmedico/portage/commits/bug_492932 I've posted it for review here: http://thread.gmane.org/gmane.linux.gentoo.portage.devel/5026 This is in the master branch now: https://github.com/gentoo/portage/commit/a9aea5f9a055e6a38acfbaa1b6190d0c627cb299 Released in portage-2.2.16. |