| Summary: | problems emerging mesa-6.5.1-r1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Boyan Ivanov <tindor> |
| Component: | New packages | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Log file of the emerge process
output of emerge --debug =mesa-6.5.1-r1 the environment file the environment file after the setup and before the unpacking phase the output after adding "set -x" |
||
|
Description
Boyan Ivanov
2006-09-28 18:14:36 UTC
Created attachment 98350 [details]
Log file of the emerge process
Looks like this is another bug where portage isn't preserving variables across phases. CONFIG is set in pkg_setup() and used in src_unpack(). I'm unable to reproduce this problem. Please attach the output of `emerge --debug =mesa-6.5.1-r1`. Created attachment 98392 [details]
output of emerge --debug =mesa-6.5.1-r1
You're log shows CONFIG=linux-dri-x86 being properly set on line 290. Then it's disappeared from the environment when line 1147 is reached. Do you have any idea what might be different about your environment? Perhaps you have something in /etc/portage/bashrc? In order to troubleshoot this, you can run the following commands separately: FEATURES=noauto ebuild /usr/portage/media-libs/mesa/mesa-6.5.1-r1.ebuild setup FEATURES=noauto ebuild /usr/portage/media-libs/mesa/mesa-6.5.1-r1.ebuild unpack Check /var/tmp/portage/mesa-6.5.1-r1/temp/environment after the setup phase to see if CONFIG is still in the environment. It seems to be there, but I'll attach this file also, so you can check it. Created attachment 98412 [details]
the environment file
There's no file /etc/portage/bashrc and I haven't changed anything in the environment manually. (In reply to comment #6) > It seems to be there, but I'll attach this file also, so you can check it. Well, I don't see a CONFIG variable defined in that file. Which phase is that from? If it's just after setup then it means that something removed it before the end of the setup phase. We need to isolate exacly where and when this is happening. Well, the missing CONFIG variable has beeen omitted after the unpack phase, as I see it after the setup phase : Tindor ~ # FEATURES=noauto ebuild /usr/portage/media-libs/mesa/mesa-6.5.1-r1.ebuild setup QA Notice: USE Flag 'amd64-fbsd' not in IUSE for media-libs/mesa-6.5.1-r1 QA Notice: USE Flag 'kernel_FreeBSD' not in IUSE for media-libs/mesa-6.5.1-r1 Tindor ~ # cat /var/tmp/portage/mesa-6.5.1-r1/temp/environment | grep CONFIG CONFIG=linux-dri-x86 this is at the beginning of the file in the variable section. But I'll attach this file also, just in case. Created attachment 98418 [details]
the environment file after the setup and before the unpacking phase
Please add 'set -x' on the second line of /usr/lib/portage/bin/ebuild.sh, just below '#!/bin/bash'. Then run `emerge =mesa-6.5.1-r1`. Hopefully we'll be able to trace what's going wrong with the output from that. Created attachment 98433 [details]
the output after adding "set -x"
I don't see anything in your log change the CONFIG variable after it is initially set. The sourcing and saving of the environment in /var/tmp/portage/mesa-6.5.1-r1/temp/environment seems to be normal as well. Sorry, I can't explain that behavior. But could you propose a walkthrough? When bash tracing is enabled (set -x), it's supposed to show everything that happens during the `source /var/tmp/portage/mesa-6.5.1-r1/temp/environment` command. We're not seeing the CONFIG variable show up again in those source commands, so something's wrong there. It seems like your /var/tmp/portage/mesa-6.5.1-r1/temp/environment is always empty for some reason. Well, it worked after I added CONFIG=linux-dri-x86 to the command line in that manner : CONFIG=linux-dri-x86 emerge -va mesa |
