Hello, I tried a no-change rebuild without this patch, and also a build of
pyexiv2 0.3.2-9 from Debian, and none of them had this issue
"python -c 'import pyexiv2'"
works with and without this patch. For this reason, I'm going to sync
pyexiv2 from Debian, since this was the only remaining delta.
I suspect this was some sort of python regression that has been fixed in
the meanwhile?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050918
Title:
Segmentation fault when exiting python after impo
** Changed in: pyexiv2
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050918
Title:
Segmentation fault when exiting python after importing pyex
** Branch linked: lp:ubuntu/pyexiv2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050918
Title:
Segmentation fault when exiting python after importing pyexiv2
To manage notifications about this bu
This bug was fixed in the package pyexiv2 - 0.3.2-5ubuntu1
---
pyexiv2 (0.3.2-5ubuntu1) quantal; urgency=low
* Fix build failure (Olivier Tilloy). LP: #1050918.
-- Matthias KloseWed, 26 Sep 2012 16:05:33 +0200
** Changed in: pyexiv2 (Ubuntu)
Status: Fix Committed => Fix
** Changed in: pyexiv2 (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050918
Title:
Segmentation fault when exiting python after importing pyexiv2
The attachment "version-tuple.patch" of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag 'patch'
I just subscribed Micah and Martin-Éric who helped with packaging issues in the
past.
Guys, could we have the patch that fixes this bug pushed to Quantal? For
convenience I’m attaching it here (it’s the contents of revision 376 of
lp:pyexiv2).
Thanks!
** Patch added: "version-tuple.patch"
h
Thanks. The problem is now fixed. When can we expect an updated
package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050918
Title:
Segmentation fault when exiting python after importing pyexiv2
Fixed in the trunk at revision 376.
** Changed in: pyexiv2
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050918
Title:
Segmentation fault when exiting p
** Branch linked: lp:pyexiv2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050918
Title:
Segmentation fault when exiting python after importing pyexiv2
To manage notifications about this bug go to
For some reason, instantiating the exiv2_version tuple outside of the
boost module declaration causes the segfault, whereas it previously
worked. This is easily fixed by moving the instantiation inside the
BOOST_PYTHON_MODULE block.
** Changed in: pyexiv2
Status: Confirmed => In Progress
*
I can also reproduce with the tip of the trunk on Quantal.
** Also affects: pyexiv2
Importance: Undecided
Status: New
** Changed in: pyexiv2
Importance: Undecided => High
** Changed in: pyexiv2
Status: New => Confirmed
** Changed in: pyexiv2
Assignee: (unassigned) => Ol
13 matches
Mail list logo
