Bug#322739: Bug#322825: Possibility of working around this bug in stable

2005-08-21 Thread Don Armstrong
On Fri, 19 Aug 2005, Don Armstrong wrote:
> I'm now redirecting reportbug 3.15, 3.8 and versions younger than 3 to
> the previous version of bugreport.cgi. [Or rather, will be as soon as
> apache on spohr gets reloaded.]

It has now been reloaded and appears to be working properly; newer
versions will have to be fixed as the redirect rules do not currently
apply to them.


Don Armstrong

-- 
Do not handicap your children by making their lives easy.
 -- Robert Heinlein _Time Enough For Love_ p251

http://www.donarmstrong.com  http://rzlab.ucr.edu


signature.asc
Description: Digital signature


Bug#322739: Bug#322825: Possibility of working around this bug in stable

2005-08-19 Thread Don Armstrong
tag 322825 pending
thanks

On Thu, 18 Aug 2005, Don Armstrong wrote:
> 2) the user agent that querybts sends so I can redirect it to older
>versions if that's what needs to be done.

I'm now redirecting reportbug 3.15, 3.8 and versions younger than 3 to
the previous version of bugreport.cgi. [Or rather, will be as soon as
apache on spohr gets reloaded.]

Considering the information that querybts is getting from
bugreport.cgi, I'd strongly suggest just using
bugreport.cgi?bug=XXX&msg=2 and doing minimal parsing (or just using
the mailbox).


Don Armstrong

-- 
If a nation values anything more than freedom, it will lose its
freedom; and the irony of it is that if it is comfort or money it
values more, it will lose that, too.
 -- W. Somerset Maugham

http://www.donarmstrong.com  http://rzlab.ucr.edu


signature.asc
Description: Digital signature


Bug#322739: Bug#322825: Possibility of working around this bug in stable

2005-08-19 Thread Jutta Wrage

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Am 19.08.2005 um 20:11 schrieb Justin Pryzby:



"GET http://bugs.debian.org/cgi-bin/bugreport.cgi?
bug=322825&archive=no HTTP/1.0" 404 285 "-" "Python-urllib/1.15"
"GET http://bugs.debian.org/db/32/322825.html HTTP/1.0" 404 281 "-"
"Python-urllib/1.15"


Sorry, forgot to add, that the second set of requests is from woody,  
which is widely used on server machines still.



  GET /db/29/298740.html


Ah, so that non existing URL might be the reason, that querybts fails.

greegins

Jutta

- -- 
http://www.witch.westfalen.de

http://witch.muensterland.org

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iEYEARECAAYFAkMGM3UACgkQOgZ5N97kHkc37ACgi56D6Ntz1zRnZh6e/vIbosL7
OZMAoJshGqkRi/gWhesIkKay0z1rOwPZ
=gU+k
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#322739: Bug#322825: Possibility of working around this bug in stable

2005-08-19 Thread Jutta Wrage

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Am 19.08.2005 um 07:59 schrieb Don Armstrong:

1) exactly what is breaking the parser (to see if it can be easily  
fixed)

2) the user agent that querybts sends so I can redirect it to older
   versions if that's what needs to be done.


1) can be answered by someone, who can dive through reportbug's  
python code.


2) That can be read from the log entries on the apache. If I use my  
apache as "proxy" I see the following requests:


"GET http://bugs.debian.org/cgi-bin/bugreport.cgi? 
bug=322825&archive=no&mbox=no HTTP/1.0" 404 285 "-" "reportbug/3.8 
(Debian)"
"GET http://bugs.debian.org/db/32/322825.html HTTP/1.0" 404 281 "-"  
"reportbug/3.8 (Debian)"


"GET http://bugs.debian.org/cgi-bin/bugreport.cgi? 
bug=322825&archive=no HTTP/1.0" 404 285 "-" "Python-urllib/1.15"
"GET http://bugs.debian.org/db/32/322825.html HTTP/1.0" 404 281 "-"  
"Python-urllib/1.15"


Where I do not know, if the second request is only made because the  
first one does not give a usable result.



greetings

Jutta




- -- 
http://www.witch.westfalen.de

http://witch.muensterland.org

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iEYEARECAAYFAkMGFRkACgkQOgZ5N97kHkcM6gCgvvcQDuJwWOVrxE2iOkrdfUSb
3jwAn1FaGFoSNQpcz20r44dbzav+SKvt
=GjxE
-END PGP SIGNATURE-


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]