python 2.5 bytecode problems

[wrobell]

On Tue, Sep 26, 2006 at 09:25:06PM +0100, wrobell wrote:
> I am planning to build Python 2.5 (final version) on TH builders.

This is done more or over. Dozens of packages are rebuilt and these
are working fine. Still there are packages, which should be rebuilt.

If something is not working for you, i.e. in case of ipython you
could get error

    ImportError: Bad magic number in /usr/share/python2.5/site-packages/IPython/__init__.pyc

then please increase release and send it to builders. If you can't do this,
then let me know, I will do it.

Below two scripts I used for mass upgrade (maybe they will be useful for
somebody):

1. Increase release for specific packages, fails if any spec file contains
   non-integer release
----
#!/bin/sh

grep '^Release:.*[0-9]\+\.[0-9]' $@ && exit 1

for f in $@; do
    rel=$(grep '^Release:' $f | awk -F':' '{print $2}')

    echo -n $f '->' $rel '-> '
    rel=$(($rel + 1))
    echo $rel

    [ $? ] || exit 1

    sed -i "s/^\(Release:\).*\([0-9]\+\)/\1	$rel/" $f
    grep "^\(Release:.\+\)\([0-9]\+\)" $f
done
----

2. Commit specific specs, with message indicating release number
---
#!/bin/sh

for f in $@; do
    rel=$(grep '^Release:' $f | awk -F':' '{print $2}' | sed 's/[^0-9]\+//g')
    cvs ci -m "- rel. $rel to rebuild with python 2.5 (final)" $f
done   
---

[...]

Regards,

    wrobell <wrobell at pld-linux.org>