On Mon, Nov 18, 2013 at 11:13:33AM +, Mark Brown wrote:
> On Sun, Nov 17, 2013 at 02:36:48PM -0500, James McCoy wrote:
>
> > Well, we're basically just running
>
> > wget -q -O - http://bugs.debian.org/release-critical/other/all.html
>
> > and then parsing the output. Could you run that (
On Sun, Nov 17, 2013 at 12:50:21PM +, Mark Brown wrote:
> On Sun, Nov 17, 2013 at 07:44:03AM -0500, James McCoy wrote:
>
> > Not sure what's different on your end. Are you familiar enough with
> > Perl to step through the debugger and see where things are going wrong?
>
> No, I don't really
On Sun, Nov 17, 2013 at 07:44:03AM -0500, James McCoy wrote:
> Not sure what's different on your end. Are you familiar enough with
> Perl to step through the debugger and see where things are going wrong?
No, I don't really understand perl at all. I *suspect* as I'm on a slow
network with some
Control: tag -1 moreinfo
Control: severity -1 normal
On Sun, Nov 17, 2013 at 09:41:28AM +, Mark Brown wrote:
> When I run rc-alert on my system which I know has some packages with RC
> bugs it does not report anything.
$ rc-alert | grep ^Bug | wc -l
185
> The same applies if one of the RC
>
Package: devscripts
Version: 2.13.4
Severity: important
When I run rc-alert on my system which I know has some packages with RC
bugs it does not report anything. The same applies if one of the RC
buggy packages is explicitly selected on the command line. For example,
"rc-alert clc-intercal" does
5 matches
Mail list logo
