[arch-general] [arch-dev-public] Python rebuild on its way to [testing]

Allan McRae allan at archlinux.org
Mon Oct 4 19:26:02 EDT 2010

On 05/10/10 09:02, Ng Oon-Ee wrote:
> On Mon, 2010-10-04 at 20:14 +0200, Pierre Schmitz wrote:
>> On Mon, 04 Oct 2010 23:01:03 +0800, Ng Oon-Ee<ngoonee at gmail.com>
>> wrote:
>>> Just a question on this topic - does the new [staging] mean that
>>> [testing] should always be complete (ie. not having any
>>> unupdated-for-lib-bump packages)?
>> Yes, that was the whole idea; to not break or freeze testing
>> intentionally.
> Thanks =). Now that the python rebuild is complete, how do I find out
> (besides parsing pacman -Qi python) which of my AUR (-Qm) packages are
> affected? Just realized jack_control from jack-audio-connection-kit-mp
> doesn't work, neither does python_waf.

Any package that links to libpython2.6.so, or has files pointing at 
/usr/bin/python or /usr/bin/env python needs fixed.

something like  (untested...)

for pkg in ....; do
   readelf -d $(pacman -Qql $pkg) 2>/dev/null | grep libpython2.6
   grep "usr/bin/python" $(pacman -Qql $pkg) | grep -v python2
   grep "usr/bin/env python" $(pacman -Qql $pkg) | grep -v python2


More information about the arch-general mailing list