| Summary: | net-misc/openssh-4.9_p1-r1 fails on absent "USE=ldap" feature in this version. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Xavian-Anderson Macpherson <Shingoshi> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | boltomli |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
openssh-4.9_p1-r1.build.log
portage.info_2008.04.02.21:47:39 |
||
|
Description
Xavian-Anderson Macpherson
2008-04-03 06:49:59 UTC
Created attachment 148176 [details]
openssh-4.9_p1-r1.build.log
openssh-4.9_p1-r1.build.log
Created attachment 148177 [details]
portage.info_2008.04.02.21:47:39
portage.info_2008.04.02.21:47:39
Please read the error message before you file a bug. * Sorry, but this version does not yet support features * that you requested: ldap * Please mask openssh-4.9_p1-r1 for now and check back later: * # echo '=net-misc/openssh-4.9_p1-r1' >> /etc/portage/package.mask (In reply to comment #3) > Please read the error message before you file a bug. > > * Sorry, but this version does not yet support features > * that you requested: ldap > * Please mask openssh-4.9_p1-r1 for now and check back later: > * # echo '=net-misc/openssh-4.9_p1-r1' >> /etc/portage/package.mask > I'm just wondering why the package would even allow the flag to be present to influence the build, when I've seen other packages with different USE flags for different versions. In those packages, the USE flag set for one version, but absent in another, won't prevent or influence the build of the package(s) without that flag. That is what I see as the bug here. Not that I didn't set the proper flag, but that it shouldn't have influence the build at all. Shingoshi I'd say to assure users of ldap enabled openssh actually notice the issue, instead silently getting it without ldap support installed, which is much more problematic on a production box, than a failing build. (In reply to comment #5) > I'd say to assure users of ldap enabled openssh actually notice the issue, > instead silently getting it without ldap support installed, which is much more > problematic on a production box, than a failing build. > Ok. I'll take your word for it. Have a nice weekend! Shingoshi Any idea when this will be available again? (In reply to comment #6) > Any idea when this will be available again? No. Have a look at the Changelog, check resolved openssh bug reports and if you don't find relevant information, contact the maintainer about it. |