[SOLVED] openssh fails

[klees]

While updating my system openssh failed to compile. Below is the log:

Code: Select all

 * Sorry, but this version does not yet support features
 * that you requested:   ldap
 * Please mask openssh-4.6_p1-r2 for now and check back later:
 *  # echo '=net-misc/openssh-4.6_p1-r2' >> /etc/portage/package.mask

!!! 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'.

Any ideas?

[jonnevers]

Any ideas?

sure, the two obvious ideas!
do what it suggests:

Code: Select all

echo '=net-misc/openssh-4.6_p1-r2' >> /etc/portage/package.mask

or try not using the 'ldap' USE flag

Code: Select all

echo "net-misc/openssh -ldap" >> /etc/portage/package.use
emerge -av openssh

[termite]

Unless you have some need for ldap (if you don't know you do, you probably don't), I'd recommend the second approach, as it allows upgrades.

[klees]

Not using ldap worked. Sorry for my noobness.

[swingkyd]

you would think that one living in the stable tree would not get such errors. is this not a bug?

[mark_alec]

you would think that one living in the stable tree would not get such errors. is this not a bug?

It isn't - http://bugs.gentoo.org/show_bug.cgi?id=170545

[baldeante]

Hello,

I have the same problem and solved as posted here but i do not have ldap flag set.

Des anyone knows why does openssh complains ???

[Dominique_71]

Same here, I don't have any ldap use flag.

[baldeante]

Hello,

I noticed something else when i emerge openssh with "-pv" the ldap flag isn't there, so if i don't have it on my use and it doesn't aper with "-pv" from where does it came

I guess some mystery's exist just to drive us nuts ... and to make us loose the time we don't have ....

[flysideways]

Choosing the Right Profile

First, a small definition is in place.

A profile is a building block for any Gentoo system. Not only does it specify default values for CHOST, CFLAGS and other important variables, it also locks the system to a certain range of package versions. This is all maintained by the Gentoo developers.

Previously, such a profile was untouched by the users. However, there may be certain situations in which you may decide a profile change is necessary.

You can see what profile you are currently using with the following command:

Code Listing 7: Verifying system profile

# ls -FGg /etc/make.profile

You don't have ldap set in make.conf but the developers set it for you if you are using a default profile. It's not a bug, it's a "feature". emerge --info should show that ldap is in fact set globally. Just get rid of it with net-misc/openssh -ldap in your /etc/portage/package.use file.

[JakeTri]

Look like someone set this package as stable but never tested with default desktop profile!

I think the right "fix" for this is to ... either keep this in the ~x86 or mask it for the 2007.0 desktop profile.

Thanks,
Jake

[flysideways]

*openssh-4.6_p1-r3 (06 Aug 2007)

06 Aug 2007; Mike Frysinger <vapier@gentoo.org> +openssh-4.6_p1-r3.ebuild:
Add updated ldap patch #187594.

And now it's fixed.

[baldeante]

Choosing the Right Profile

First, a small definition is in place.

A profile is a building block for any Gentoo system. Not only does it specify default values for CHOST, CFLAGS and other important variables, it also locks the system to a certain range of package versions. This is all maintained by the Gentoo developers.

Previously, such a profile was untouched by the users. However, there may be certain situations in which you may decide a profile change is necessary.

You can see what profile you are currently using with the following command:

Code Listing 7: Verifying system profile

# ls -FGg /etc/make.profile

You don't have ldap set in make.conf but the developers set it for you if you are using a default profile. It's not a bug, it's a "feature". emerge --info should show that ldap is in fact set globally. Just get rid of it with net-misc/openssh -ldap in your /etc/portage/package.use file.

You are right emerge --info shows ldap flag there i never remember to check that

And as flysideways says is now solved today i did emerge --sinc && emerge world -uD --newuse and the package when fine