Bug#774074: dh-make-perl: Recursive option does not check version of existing packages

[Andrew Beverley]

On Sat, 2015-09-26 at 16:32 +0200, gregor herrmann wrote:
> On Sat, 26 Sep 2015 13:43:16 +0000, Damyan Ivanov wrote:
> 
> > Any news on including DPKG::Parse in Debian?
> 
> It's in git and basically ready for upload; if I'm reading my notes
> in d/changelog correctly, I was waiting for Andy to review my changes

Sorry. I think I did, but let me take another look. Stupid question: what
is my git.debian.org username?

> (and file an ITP bug).

I tried a couple of times, but the bug tracker loses my emails, despite
them definitely being delivered to the remote mail server. I did report it
to owner at b.d.o, but didn't hear anything back.

I've just tried again now, and this time I'm getting:

Querying Debian BTS for reports on wnpp (source)...
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2211, in <module>
    main()
  File "/usr/bin/reportbug", line 1081, in main
    return iface.user_interface()
  File "/usr/bin/reportbug", line 1703, in user_interface
    latest_first=self.options.latest_first)
  File "/usr/lib/python2.7/dist-packages/reportbug/ui/text_ui.py", line 517, in handle_bts_query
    source=source, http_proxy=http_proxy, archived=archived)
  File "/usr/lib/python2.7/dist-packages/reportbug/debbugs.py", line 1275, in get_reports
    stats = debianbts.get_status(bugs)
  File "/usr/lib/pymodules/python2.7/debianbts.py", line 179, in get_status
    reply = server.get_status(*nr)
  File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 545, in __call__
    return self.__r_call(*args, **kw)
  File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 567, in __r_call
    self.__hd, self.__ma)
  File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 430, in __call
    timeout = self.timeout)
  File "/usr/lib/python2.7/dist-packages/SOAPpy/Client.py", line 318, in call
    raise HTTPError(code, msg)
SOAPpy.Errors.HTTPError: <HTTPError 500 Internal Server Error>

I had this same problem a while ago, which I reported to the main Debian
users mailing list (not being sure where else to report it), but again
heard nothing back.

Thanks,

Andy