Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 627124 - app-crypt/mit-krb5 depends on libressl if pkinit is enabled
Summary: app-crypt/mit-krb5 depends on libressl if pkinit is enabled
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-05 19:50 UTC by hexum
Modified: 2017-08-07 18:07 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge info (info.gz,3.37 KB, application/gzip)
2017-08-05 19:50 UTC, hexum
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hexum 2017-08-05 19:50:48 UTC
Created attachment 488038 [details]
emerge info

I have got strange error.

* Error: circular dependencies:

(dev-libs/openssl-1.0.2l:0/0::gentoo, ebuild scheduled for merge) depends on
 (app-crypt/mit-krb5-1.15.1:0/0::gentoo, ebuild scheduled for merge) (buildtime)
  (dev-libs/openssl-1.0.2l:0/0::gentoo, ebuild scheduled for merge) (buildtime)

It might be possible to break this cycle
by applying any of the following changes:
- app-crypt/mit-krb5-1.15.1 (Change USE: +libressl)
- app-crypt/mit-krb5-1.15.1 (Change USE: -pkinit)
- dev-libs/openssl-1.0.2l (Change USE: -kerberos)

Why can't mit-krb5[pkinit] be build with openssl?
Comment 1 hexum 2017-08-06 00:56:58 UTC
Now I'm trying to rebuild system without kerberos and then turn it on back.
Will see if it can help. It can be a common circular dependency error.
My system was not updated for a long time. In this case I can't update system partially: some new packages depends on new icu, but already installed rely on an old one. It's a hell of incompatibilities of old tree packages with dependencies of an updated tree. Do not know how to prevent such cases.
Comment 2 hexum 2017-08-07 18:07:27 UTC
The problem was only observable due to my system state.
After system update (I had to disable kerberos temporary) the problem is not reproducible anymore.