RE: Is debbugs.gnu.org broken?

[Drew Adams]

> >> > Go to http://debbugs.gnu.org/, type 20 into field "Browse 
> >> > the N newest bugs:", then click `Find'.  It finds no bugs.
> >> > That used to work.
> >> 
> >> Works fine here with your recipe above.
> >> http://debbugs.gnu.org/cgi/pkgreport.cgi?newest=20;package=emacs
> >
> > Thanks for checking.
> >
> > But that is not following my recipe.  I didn't used to need 
> > to enter the package (`emacs').  I just did what I wrote: went to 
> > http://debbugs.gnu.org/, typed 20 into field "Browse the N newest
> > bugs:", and clicked `Find'.
> 
> Trust me, I just did what you wrote.

OK.

> I get this:
> http://debbugs.gnu.org/cgi/pkgreport.cgi?newest=20
> 
> The URL I gave was not related to the recipe I followed but 
> I thought you would enjoy it too.

Trying that URL I get the same result: all bugs in package emacs.  Even though
the browser title bar says this: "bugs in 20 newest reports -- GNU bug report
logs"

Clearly we are not seeing the same thing for the same URL.  I even deleted my
browser cache and history, and even closed the browser completely.  I've
attached a screenshot of what I see.

> > Also, when I use your URL or I enter 20 as before but I 
> > also enter "emacs" as the package, I do not get the 20 latest bugs.
> 
> What do you get with this one?
> http://debbugs.gnu.org/cgi/pkgreport.cgi?newest=10;package=emacs

Same thing, except the title bar says "10" instead of "20".

> I definitely get the 10 last Emacs "reports" -- i.e. bugs or updates 
> to a bug.

Sounds like perhaps the problem depends on the browser.

> Perhaps something weird with Internet Explorer.  Joooooking :)

No joke.  My guess is you are right.  My blind guess so far is that the site
changed something that IE7, at least, does not digest well.

Ah, but unfortunately Google Chrome has the same problem (for me) - at least the
version I have, which is "Version 22.0.1229.79 m".

throw-emacs-recent-bugs-IE7.png
Description: PNG image