This looks very much like bug 211553, in which case it is a bug in wxwidgets2.6 not in bitpim. This could be solver in two ways:
- patching wxwidgets2.6 so that we install upstream wx.pth instead of the generated file, or - changing bitpim dependencies to wxwidgets2.6
Anyway, can you confirm that by installing python-wxgtk2.8 your problem disappears?
This looks very much like bug 211553, in which case it is a bug in wxwidgets2.6 not in bitpim.
This could be solver in two ways:
- patching wxwidgets2.6 so that we install upstream wx.pth instead of the generated file, or
- changing bitpim dependencies to wxwidgets2.6
Anyway, can you confirm that by installing python-wxgtk2.8 your problem disappears?