[opensuse-packaging] Python 2.7 coming to Factory
Fellow developers and users, just a heads-up: moments ago I have submitted a new Python version 2.7. This version contains many new and interesting features, and only a small chance of breaking existing code: no backwards-incompatible changes, and no big changes worth mentioning. For more details see [1]. There is one thing notable for people who write or maintain software that embeds Python: the new function PySys_SetArgvEx [2] does the job originally done by PySys_SetArgv, but closes a nasty security problem with the latter [3][4]. Most software should be fixed by now, but please review your packages anyway. have fun m. [1] http://docs.python.org/dev/whatsnew/2.7.html#porting-to-python-2-7 [2] http://docs.python.org/dev/c-api/init.html#PySys_SetArgvEx - the link points to python 3 docs, but applies to 2.7 as well [3] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983 [4] http://www.openwall.com/lists/oss-security/2009/01/26/2 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
2010/8/27 Jan Matejek
just a heads-up: moments ago I have submitted a new Python version 2.7. This version contains many new and interesting features, and only a small chance of breaking existing code: no backwards-incompatible changes, and no big changes worth mentioning. For more details see [1].
Yes! I am glad to see this. -- Jon -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Freitag 27 August 2010 schrieb Jan Matejek:
Fellow developers and users,
just a heads-up: moments ago I have submitted a new Python version 2.7. This version contains many new and interesting features, and only a small chance of breaking existing code: no backwards-incompatible changes, and no big changes worth mentioning. For more details see [1].
There is one thing notable for people who write or maintain software that embeds Python: the new function PySys_SetArgvEx [2] does the job originally done by PySys_SetArgv, but closes a nasty security problem with the latter [3][4]. Most software should be fixed by now, but please review your packages anyway.
There are quite many packages that break because of this - many of them are from devel:languages:python - I assumed you had checked that ;( Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Dne 6.9.2010 11:27, Stephan Kulow napsal(a):
Am Freitag 27 August 2010 schrieb Jan Matejek:
Fellow developers and users,
just a heads-up: moments ago I have submitted a new Python version 2.7. This version contains many new and interesting features, and only a small chance of breaking existing code: no backwards-incompatible changes, and no big changes worth mentioning. For more details see [1].
There is one thing notable for people who write or maintain software that embeds Python: the new function PySys_SetArgvEx [2] does the job originally done by PySys_SetArgv, but closes a nasty security problem with the latter [3][4]. Most software should be fixed by now, but please review your packages anyway.
There are quite many packages that break because of this - many of them are from devel:languages:python - I assumed you had checked that ;(
right now everything is rebuilding, so i can't see the statuses :( AFAICT, many packages broke because of setuptools, i'll be forwarding a new version momentarily m.
Greetings, Stephan
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Montag 06 September 2010 schrieb Jan Matejek:
Dne 6.9.2010 11:27, Stephan Kulow napsal(a):
Am Freitag 27 August 2010 schrieb Jan Matejek:
Fellow developers and users,
just a heads-up: moments ago I have submitted a new Python version 2.7. This version contains many new and interesting features, and only a small chance of breaking existing code: no backwards-incompatible changes, and no big changes worth mentioning. For more details see [1].
There is one thing notable for people who write or maintain software that embeds Python: the new function PySys_SetArgvEx [2] does the job originally done by PySys_SetArgv, but closes a nasty security problem with the latter [3][4]. Most software should be fixed by now, but please review your packages anyway.
There are quite many packages that break because of this - many of them are from devel:languages:python - I assumed you had checked that ;(
right now everything is rebuilding, so i can't see the statuses :( AFAICT, many packages broke because of setuptools, i'll be forwarding a new version momentarily
Don't let the blocked fool you, you can check the last build result: https://build.opensuse.org/stage/project/monitor?commit=Filter%3A&failed=1&pkgname=&repo_bleeding_edge_python_Factory=1&arch_i586=1&arch_x86_64=1&lastbuild=1&project=devel%3Alanguages%3Apython&defaults=0 Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Dne 6.9.2010 14:43, Stephan Kulow napsal(a):
There are quite many packages that break because of this - many of them are from devel:languages:python - I assumed you had checked that ;(
right now everything is rebuilding, so i can't see the statuses :( AFAICT, many packages broke because of setuptools, i'll be forwarding a new version momentarily
Don't let the blocked fool you, you can check the last build result:
i see; in that case, i'd like to point out that most of those packages were failing before the update as well: https://build.opensuse.org/stage/project/monitor?commit=Filter%3A&succeeded=1&failed=1&pkgname=&repo_bleeding_edge_python_Factory=1&repo_openSUSE_11_3=1&repo_openSUSE_Factory=1&arch_x86_64=1&lastbuild=1&project=devel%3Alanguages%3Apython&defaults=0 many of those are simple filelist problems, there are some deeper issues and i'm looking into that, but those only affect about five packages from d:l:py. i am not aware of anything that would be "newly" broken in base Factory distribution. if there really is something, please let me know m.
Greetings, Stephan
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Monday 06 September 2010, Jan Matejek wrote:
many of those are simple filelist problems, there are some deeper issues and i'm looking into that, but those only affect about five packages from d:l:py. i am not aware of anything that would be "newly" broken in base Factory distribution. if there really is something, please let me know
One thing that broke (and that breaks on every python update) was rpmlint, which is used for building every package (it is part of the supportpackages). Hnece I would love to see a more advanced notice of such updates in the future to be able to fix the packages in time. (here I ran into the additional issue that I was on FTO when this happened..). Greetings, Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, 27 Aug 2010 19:30:34 +0200
Jan Matejek
Fellow developers and users,
just a heads-up: moments ago I have submitted a new Python version 2.7. This version contains many new and interesting features, and only a small chance of breaking existing code: no backwards-incompatible changes, and no big changes worth mentioning. For more details see [1].
Unfortunately, since the switch to python 2.7, virt-manager (the build-fixed-but-not-yet-forwarded one from the Virtualization repo) just segfaults and this is clearly beyond what I am able to fix. -- Stefan Seyfried "Any ideas, John?" "Well, surrounding them's out." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Monday 20 September 2010 schrieb Dirk Müller:
On Monday 06 September 2010, Jan Matejek wrote:
many of those are simple filelist problems, there are some deeper issues and i'm looking into that, but those only affect about five packages from d:l:py. i am not aware of anything that would be "newly" broken in base Factory distribution. if there really is something, please let me know
One thing that broke (and that breaks on every python update) was rpmlint, which is used for building every package (it is part of the supportpackages). Hnece I would love to see a more advanced notice of such updates in the future to be able to fix the packages in time.
How much time do you need? it was way over a week before annoucement and hit. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Dne 20.9.2010 23:28, Stefan Seyfried napsal(a):
Unfortunately, since the switch to python 2.7, virt-manager (the build-fixed-but-not-yet-forwarded one from the Virtualization repo) just segfaults and this is clearly beyond what I am able to fix.
it works for me with cleanly built python-gtk. and now apparently with python-gtk from Factory too. perhaps there was some kind of miscompilation m. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Tuesday 21 September 2010, Stephan Kulow wrote:
How much time do you need? it was way over a week before annoucement and hit.
it usually doesn't take me more than a day to adopt a new version, but as I said,I was on FTO. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (5)
-
Dirk Müller -
Jan Matejek -
Jon Nelson -
Stefan Seyfried -
Stephan Kulow