Looks like they fixed the LDAP requirement bug in with p1-r3. This was related if you had a ldap as a USE flag. You would see an error similar to this:
!!! ERROR: net-misc/openssh-4.6_p1-r2 failed.
Call stack:
ebuild.sh, line 1648: Called dyn_setup
ebuild.sh, line 714: Called qa_call 'pkg_setup'
ebuild.sh, line 44: Called pkg_setup
openssh-4.6_p1-r2.ebuild, line 64: Called die
!!! booooo
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/net-misc/openssh-4.6_p1-r2/temp/build.log'.
I wanted to see if they addressed the istate bug that I mentioned in the last post, so I did a simple scp, and saw the following in the logs:
Looks like they fixed the LDAP requirement bug in with p1-r3. This was related if you had a ldap as a USE flag. You would see an error similar to this:
!!! ERROR: net-misc/openssh-4.6_p1-r2 failed.
Call stack:
ebuild.sh, line 1648: Called dyn_setup
ebuild.sh, line 714: Called qa_call 'pkg_setup'
ebuild.sh, line 44: Called pkg_setup
openssh-4.6_p1-r2.ebuild, line 64: Called die
!!! booooo
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/net-misc/openssh-4.6_p1-r2/temp/build.log'.
I wanted to see if they addressed the istate bug that I mentioned in the last post, so I did a simple scp, and saw the following in the logs:
Aug 6 08:38:11 comp.com sshd[32425]: Accepted keyboard-interactive/pam for hanji from xxx.xxx.xxx.xxx port 41349 ssh2
Aug 6 08:38:11 comp.com sshd(pam_unix)[32435]: session opened for user hanji by (uid=0)
Aug 6 08:38:12 comp.com sshd[32435]: error: channel 0: chan_read_failed for istate 3
Aug 6 08:38:12 comp.com sshd[32435]: error: channel 0: chan_read_failed for istate 3
Aug 6 08:38:12 comp.com sshd(pam_unix)[32435]: session closed for user hanji
So, no. This isn’t fixed yet. But looking at bugs:
http://bugs.gentoo.org/show_bug.cgi?id=181407
I see that they added a fix from upstream to openssh-4.6_p1-r4. This is not in portage yet (so ACCEPT_KEYWORDS=”x86″ isn’t an option yet, but I’m sure it’ll be in portage soon).