Re: [gentoo-user] python-updater: updating cracklib forever...
On 06-Mar-14 20:59, Daniel Frey wrote: 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... I wonder if python-updater can even tell the package is built without the python USE flag. It sounds to me like it can't, and it notices that modules are missing, so it adds it to the rebuild list. Easy way to find out is emerge cracklib with the python USE flag enabled. If python-updater gives an all-clear after that, maybe it's a bug? I did try it. When I recompiled "cracklib" with "python" flag, python-updater was satisfied. But when I removed that flag, as soon as "emerge --update --newuse" recompiled cracklib it was all back again... It looks so that python-updater insists on having python-support in cracklib. If it does not find any ABI it thinks recompilation could "fix" it (without checking actuall cracklib use-flags): * check: PYTHON_ABIS [Previous Python ABIs: , new Python ABIs: 2.7] You see? Previous ABIs none, so it wants to compile cracklib to include python ABIs 2.7. But with "-python" USE flag it will never be there, no matter how many times cracklib will be recompilled. Seems to me like bug in python-updater. It should recompile cracklib only if it was compiled with *some* ABIs, but older than the new one. But not if cracklib was compiled with no python-ABIs at all... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] python-updater: updating cracklib forever...
On 03/06/2014 10:40 AM, Jarry wrote: > > 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 > I wonder if python-updater can even tell the package is built without the python USE flag. It sounds to me like it can't, and it notices that modules are missing, so it adds it to the rebuild list. Easy way to find out is emerge cracklib with the python USE flag enabled. If python-updater gives an all-clear after that, maybe it's a bug? Just a thought... Dan
Re: [gentoo-user] python-updater: updating cracklib forever...
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- -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.
Re: [gentoo-user] python-updater: updating cracklib forever...
http://bugs.gentoo.org/503648 for stabilization of 2.9.1 which has been migrated to the new python eclasses, should solve many of the python related cracklib problems
Re: [gentoo-user] python-updater: updating cracklib forever...
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. -- Regards Peter
