[Reportbug-maint] Bug#491219: Bug#491219: [PATCH] python-debianbts takes precedance over /usr/share/reportbug/reportbuglib/debianbts.py
matrixhasu at gmail.com
Thu Jul 17 18:15:48 UTC 2008
On Thu, Jul 17, 2008 at 19:28, Alban Browaeys <prahal at yahoo.com> wrote:
> Package: reportbug
> Version: 3.42
> Severity: important
> Tags: patch
> Hi. I am new to python and the debian policy regarding how to handle
> them though I found a workaround to get debreaper working again.
> It was failing
> Traceback (most recent call last):
> File "/usr/share/debreaper/debreaper", line 70, in <module>
> report = generate_report (status, status, status, status, path, gdbout)
> File "/usr/share/debreaper/bug_iface.py", line 27, in generate_report
> return reportbug.generate_blank_report (package, pkgversion, 'important', None, depinfo, '', path, body="*** Please describe what you were doing when the application crashed ***\n\n"+gdbout)
> File "/usr/share/reportbug/reportbuglib/reportbug.py", line 721, in generate_blank_report
> if debianbts.SYSTEMS[system].has_key('namefmt'):
> AttributeError: 'module' object has no attribute 'SYSTEMS'
> due to python-debianbts (dependency of reportbug-ng) tyaking precedance in the import search path in /usr/share/reportbug/reportbuglib/reportbug.py
> This patch works around it by adding /usr/share/reportbug/reportbuglib first in the import search path.
Thanks for the report! BTW, I'm not inclined to do this change: stuff
under /usr/share/$pkg is private one, so you can use it at your own
danger. I didn't look too much into the debreaper code, but you can
add a similar line than
"sys.path.insert(0,"/usr/share/reportbug/reportbuglib")" into the
debreaper code and obtain your result.
Additionally, maybe moving debreaper code to python-debianbts /
python-btsutils would be a nice move.
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
More information about the Reportbug-maint