Daniel Leidert wrote: > The reportbug module was shipped with reportbug 3.48, which was > installed on your system at the time you wrote this report. Today it's > shipped by python-reportbug but pulled in as dependency of reportbug. > However, this looks more like a problem with reportbug 3.48 than a bug > in debreaper. > > So I'm wondering if a) this report can be closed or b) a versioned > dependency on reportbug is necessary?
I could imagine that reportbug shipped its Python modules in a private modules directory, which was the right thing to do at that time. So you'd have to specify that modules directory in your sys.path. Now the proper thing would be a dependency onpython-reportbug I guess. -- Bernd Zeimetz Debian GNU/Linux Developer GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org