On Saturday, August 03, 2013 09:32:09 AM Matthias Klose wrote: > Am 03.08.2013 02:36, schrieb Daniel Schepler: > > Package: python3.2 > > Version: 3.2.4-1 > > Severity: important > > > > Currently, if I rebuild pygobject in an amd64 chroot (with pbuilder > > login), > > then install the resulting packages in that same chroot and pbuilder > > session, then python2.7 and python3.3 are able to "import gi" but > > python3.2 gives the error: > > > > root@frobozz:/tmp# python3.2 -c 'import gi' > > > > Traceback (most recent call last): > > File "<string>", line 1, in <module> > > File "/usr/lib/python3/dist-packages/gi/__init__.py", line 27, in > > <module> > > > > from ._gi import _API, Repository > > > > ImportError: No module named _gi > > > > This is despite the fact that the rebuild python3-gi package does have a > > file > > /usr/lib/python3/dist-packages/gi/_gi.cpython-32mu-x86_64-linux-gnu.so. > > And in fact, if I run strace on the python3.2 command above, it shows > > /usr/lib/python3/dist-packages/gi/_gi.cpython-32mu.so as one of the file > > locations it tries to open, but not the multiarched version. > > > > This, in turn, causes python-distutils-extra to FTBFS against rebuilt > > python3- gi. > > 3.2 never had the multiarch lookup for extensions enabled. I think I enabled > it once and found some other effects on packaging because of the changed > file names. It looks like the new pybuild implementation renames these for > 3.2 as well. Now that we did stop supporting 3.2, I don't want to change > that again, and it's probably better to fix dh-python that it even does the > right thing for backports. > > Matthias
Ah, I see... If I'd just waited one more day to investigate #717512, I wouldn't have seen this happen. You can close / tag wontfix / do whatever you want with this; and I'm off to close #717512 as no longer being an issue. -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
