Summary: | sys-apps/portage: on failures for some packages, portage displays messages referring to non-existing files/directories. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Chris Slycord <cslycord> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | tomwij |
Priority: | Normal | Keywords: | InVCS |
Version: | 2.2 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 445274 |
Description
Chris Slycord
2012-11-10 02:23:39 UTC
> * There is NOT at least 2 gigabytes RAM
> *
> * Space constrains set in the ebuild were not met!
> * The build will most probably fail, you should enhance the space
> * as per failed tests.
Did you read this? Have you tried fixing that?
1) Of course I read it. 2) no, I haven't fixed it as it is part of a bug reported elsewhere (imo, the error isn't valid). 3) whether I did our didn't read it doesn't change the fact that portage gives error messages referring to non-existent files. Okay, just checking the obvious, relisted bug and assigned to maintainers. > 2) no, I haven't fixed it as it is part of a bug reported elsewhere (imo, the error isn't valid). Which bug is this? It might be the cause of this problem. This information might or might not help the maintainer. > 3) whether I did our didn't read it doesn't change the fact that portage gives error messages referring to non-existent files. If it ran out of space, it can't create the folder; so it does play a role. > I have sys-apps/portage-2.2.0_alpha142 installed and received the following. Why are you on a masked portage? It is alpha for a reason. Nothing ran out of space. Pypy checks for 2 gb of ram. Gentoo, for whatever reason only recognizes 2000 mb of my ram and so it complains, but I still have memory space available both in ram, swap, and disk space. This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=d80c5799a59a0420301f215add4c75b7d5e14d73 This is fixed in 2.1.11.32 and 2.2.0_alpha143. |