| 1 |
On 28-01-2013 12:29:02 -0800, Zac Medico wrote: |
| 2 |
> On 01/28/2013 12:20 PM, Fabian Groffen wrote: |
| 3 |
> > On 28-01-2013 11:41:53 -0800, Zac Medico wrote: |
| 4 |
> >>> interestingly enough, this problem occurs exactly at the moment that |
| 5 |
> >>> PipeLogger._start() is invoked and self.stdout_fd is None |
| 6 |
> >> |
| 7 |
> >> You could try removing these FD_CLOEXEC lines from PipeLogger, which are |
| 8 |
> >> relatively new, to see if that helps: |
| 9 |
> > |
| 10 |
> > Thanks, I've removed that piece, looked like it worked, but eventually |
| 11 |
> > it broke down the same way. |
| 12 |
> |
| 13 |
> You might try adding Darwin to the _disable_openpty list in |
| 14 |
> pym/portage/util/_pty.py, to see if the pty device is what's triggering it. |
| 15 |
|
| 16 |
Doesn't make any difference. I've logged the issue as |
| 17 |
https://bugs.gentoo.org/show_bug.cgi?id=456296 |
| 18 |
|
| 19 |
Thanks |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
Fabian Groffen |
| 24 |
Gentoo on a different level |
Archives