Bug#515173: marked as done (rmadison: handle pg.InternalError gracefully)
Your message dated Mon, 16 Feb 2009 23:33:56 +0100
with message-id <4999E9D4.9050306@debian.org>
and subject line Re: Bug#515173: rmadison: handle pg.InternalError gracefully
has caused the Debian Bug report #515173,
regarding rmadison: handle pg.InternalError gracefully
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
515173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515173
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Hello,
as per [1], there are some minutes each day were the projectb database
ceases to exist on merkel, producing a traceback on rmadison. It would
be nice if this could be caught, and a message akin to "Database down
for daily maintenance, please try again in a few minutes" would be
printed.
Maybe you have to introduce a python wrapper in order to catch the
exception, I don't know (or just match the output for /FATAL:
*database.*does not exist/?).
Thanks for considering,
[1]: http://lists.debian.org/debian-release/2009/02/msg00401.html
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
The pure and simple truth is rarely pure and never simple.
-- Oscar Wilde
--- End Message ---
--- Begin Message ---
Adeodato Simó wrote:
> Package: qa.debian.org
>
> Hello,
Hi dato
> as per [1], there are some minutes each day were the projectb database
> ceases to exist on merkel, producing a traceback on rmadison. It would
> be nice if this could be caught, and a message akin to "Database down
> for daily maintenance, please try again in a few minutes" would be
> printed.
>
> Maybe you have to introduce a python wrapper in order to catch the
> exception, I don't know (or just match the output for /FATAL:
> *database.*does not exist/?).
I don't think we're up to using python in a perl script yet :-)
I have done the plain matching as that was easiest. Feel free to reopen
the bug or ping me personally if it doesn't do as expected.
Cheers
Luk
--- End Message ---
Reply to: