| Summary: | builds fail when ${T} suddenly disappears (obviously) | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | genbug |
| Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED CANTFIX | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
not a wine problem ... portage should be creating the temp directory in question rather than posting random snippets from your config files, use the standard `emerge --info` also post the full build log from doing `emerge wine` as an attachment The "snippets" were not random, they were precisely and deliberately chosen to explain why the paths were non std since this was the crux of the issue. I'd already cleared out portage_tmpdir but noticed a part of the tree remaining. It turned out to be a broken node in the fs. Having fixed the fs wine seems to be building OK, so I _assume_ that there was an error when portage tried to create the temp dir. Maybe some error trapping should be added to portage for such basics so they get picked up rather than being ignored and having to be guessed from the fallout. The script should stop if it can't make the directory. Changing title to reflect this is not an ebuild issue and dropping to normal. thx. (In reply to comment #0) > >>> Unpacked to /usr/portage/tmp/portage/app-emulation/wine-9999/work/wine-9999 > * Applying wine-gentoo-no-ssp.patch ... > /usr/portage/tmp/portage/app-emulation/wine-9999/temp/environment: line 1195: > /u > sr/portage/tmp/portage/app-emulation/wine-9999/temp/wine-gentoo-no-ssp.patch-593 > 0.out: No such file or directory > > Quite correct, there is no directory "temp" The "temp" directory had to exist because that's where the "environment" file was clearly located. If it suddenly disappeared then then you've got something wrong locally that probably has nothing to do with portage. Actually, should have marked this CANTFIX. If directories suddenly disappear then there's nothing we can do. We can check to make sure it's there, but it might be gone the next moment after we've check. your deliberate selection of a reduced set of information is about the same as a random selection. users often times omit useful/important information that is automatically provided by `emerge --info`. so instead of us wasting time on every bug report asking you to post `emerge --info`, you should be posting it first. OK , I think this can be closed. It appears to have been a local issue with an fs error as I noted. I have been able to build wine-9999 twice now , so I think it's reasonable to regard this as a glitch locally. Thanks for picking it up. |
wine-9999 successfully gets the git tree then attempts one epatch (wine-gentoo-no-ssp.patch) this completely misses the installed code and exits the ebuild. Reproducible: Always Steps to Reproduce: 1. unmask wine-9999 in package.keywords 2. emerge wine 3. Actual Results: Indexing 362855 objects... remote: Total 362855 (delta 302587), reused 362855 (delta 302587) 100% (362855/362855) done Resolving 302587 deltas... 100% (302587/302587) done * local clone: /usr/portage/new/distfiles/git-src/wine * committish: master >>> Unpacked to /usr/portage/tmp/portage/app-emulation/wine-9999/work/wine-9999 * Applying wine-gentoo-no-ssp.patch ... /usr/portage/tmp/portage/app-emulation/wine-9999/temp/environment: line 1195: /u sr/portage/tmp/portage/app-emulation/wine-9999/temp/wine-gentoo-no-ssp.patch-593 0.out: No such file or directory Quite correct, there is no directory "temp" bash-3.2#ls /usr/portage/tmp/portage/app-emulation/wine-9999/ work please note non std portage dirs. (though this does not seem to be the cause of the error at first sight) bash-3.2#grep -i "portdir" /etc/make.conf PORTDIR=/usr/portage/new PORTAGE_TMPDIR=${PORTDIR}/../tmp DISTDIR=${PORTDIR}/distfiles gcc version 4.2.2