I also have this bug. Downgrading 'reportbug' doesn't cure it -- I've
tried these versions, all of them are currently prone to the bug:
> cd /var/cache/apt/archives/
> alfie [VT] /var/cache/apt/archives>ls reportbug* -go
> -rw-r--r-- 1 125288 May 10 18:47 reportbug_3.12_all.deb
> -rw-r--r-- 1 125832 Jun 14 16:02 reportbug_3.13_all.deb
> -rw-r--r-- 1 125918 Jun 16 17:47 reportbug_3.14_all.deb
> -rw-r--r-- 1 125964 Jun 19 23:47 reportbug_3.15_all.deb
...all of these used to work fine. This bug can't be more than a week
old, though the newest package above is almost two months old.
Running 'reportbug reportbug' in a failed attempt to read this very bug,
looks like:
> % reportbug reportbug
> { ... etc... }
> 126 bug reports found:
>
> Important bugs - outstanding
> 1) #183573: reportbug: Requires python1.5 for installation
> 2) #279168: reportbug: Fails to send report, no error message
> 3) #302103: reportbug: Silent termination with no error when
> required http_proxy not specified
> 4) #304474: reportbug: Verifying package integrity fails with
> elinks check
> 5) #310856: reportbug: the handling of the smtphost is not really
> convenient
> 6) #322720: Can not retrieve bugs from the BTS anymore
> 7) #322739: querybts fails to retrieve bug reports
> (1-7/126) Is the bug you found listed above [y|N|m|r|q|s|f|?]? 6
> Retrieving report #322720 from Debian bug tracking system...
> No report available: #322720
Conclusion: like Anthony DeRobertis said, something in the BTS
server was changed to be incompatible with our trusty 'reportbug'
clients. Probably not news to the maintainer, but some BTS reader
might be saved a futile downgrade attempt by reading this.
HTH...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
