On 06-Mar-14 19:25, Peter Humphrey wrote:
On Thursday 06 Mar 2014 18:57:51 Jarry wrote:
today after emerging python-exec (from 2.0.1 to 2.0.1-r1)
I tried python-upadter and found out it wants to update
cracklib. OK, I did, and then tested python-updater again.
An it updated cracklib again! I tried it again, again,
again, still the same: python-updater keeps re-emerging
cracklib...
Is this normal?
I hope so, because I've been finding the same thing for some years now. Usually
I have a couple of other packages to rebuild too, but not so recently.
I just assume that python-updater can't tell whether it needs to update
cracklib, so it plays safe and adds it to the list for remerging.
Seems to me like bug in python-updater. Why does it want to
update cracklib, when it was compiled with "-python" use-flag?
sys-libs/cracklib-2.8.19 USE="nls zlib -build -python -static-libs"
And I found the same with bind on different system:
net-dns/bind-9.9.4_p2 USE="berkdb dlz ipv6 ssl -caps -doc -filter-aaaa
-fixed-rrset -geoip -gost -gssapi -idn -ldap -mysql -odbc -postgres
-python -rpz -rrl -sdb-ldap (-selinux) -static-libs -threads -urandom -xml"
If I understand it correctly, then "-python" means package is
compiled *without* python-support. So a) it should not depend
on python at all and b) recompilation does not change anything...
Jarry
--
_______________________________________________________________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.
