On Tue, Jan 17, 2012 at 6:47 AM, Sandro Tosi <[email protected]> wrote: > Hello Samuel, > > On Tue, Jan 17, 2012 at 00:15, Samuel Bronson <[email protected]> wrote: >> Package: apt-listchanges >> Version: 2.85.8 >> Severity: normal >> >> This is what I'm seeing: >> ,---- >> | naesten@hydrogen:~% apt-listchanges bzip2 >> | Traceback (most recent call last): >> | File "/usr/bin/apt-listchanges", line 28, in <module> >> | import apt_pkg >> | ImportError: No module named apt_pkg >> `---- > ... >> ii python 2.7.2-7 interactive high-level >> object-orie >> ii python-apt 0.7.97.1 Python interface to libapt-pkg > > I suspect you're using a too old python-apt. You upgraded python to > 2.7, but it's likely that the version of python-apt (which is no > longer in testing and you should upgrade the system before reporting a > bug) is supporting only 2.6 and 2.5 (check with python2.x -c "import > apt_pkg" with x in 5, 6, 7). Try upgrading python-apt and see if this > fixes your problem.
Yeah, it did fix the problem, which would seem to confirm my suspicion that apt-listchanges should depend on a recent-enough version of python-apt. Though I guess this is probably actually a problem with the old python-apt's packaging? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
