© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
[SRU]
[Impact]
Frequency of the bug is rare, or under certain cases as described in this bug. In Oneiric, anything using egenix-mx-base for mx.DateTime is vulnerable to this occurrence.
[Development Fix]
This bug was filed to the upstream source, and was fixed with the release of 3.2.1 to Debian, which was subsequently synced into Precise during the last sync.
[Stable Fix]
After reviewing the differences in the code between Debian Sid / Precise and the versions in Oneiric, there were additional code changes to the upstream version. Finding the exact specific place in the code to patch this is time consuming, and after consulting with Evan Broder, it would be more prudent to update to 3.2.1 that is in Precise (which is confirmed to build and work without changes in Oneiric)
[Test Case]
A test case to reproduce the errors in this bug in 3.2.0 are here (the result is "Segmentation Fault" in 3.2.0 or earlier):
$ python -c "from mx.DateTime import Date; Date(2011,1,1) == None"
According to the bug poster, who tested my original "backported" version which I used to test the building within Oneiric, the version of 3.2.1 does *not* have this bug, and operates as is expected, not producing the segfault
[Regression Potential]
Severity of regressions is minimal, as the changes to the upstream version are minor between 3.2.0 and 3.2.1 as it was a microrelease update.