Your message dated Sun, 21 May 2006 19:13:48 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Bug#327242: [bugzilla #327242] still reproducible?
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: bugzilla
Version: 2.18.3-1
When I try to test bugzilla with piuparts, it seems to go into an
eternal loop in the bugzilla.config script: it doesn't finish in the
fifteen or so minutes gave it (on a fast machine), and it uses a lot of
CPU. Piuparts sets DEBIAN_FRONTEND to "noninteractive", but I don't know
if that is relevant. I'd be happy to do any debugging you need. The
piuparts command line was (not including irrelevant --ignore options):
/home/liw/piuparts.bzr/piuparts.py -b etch.tar.gz -d etch -m
http://liw.iki.fi/debian -avl bugzilla.log bugzilla
It could, of course, be a bug in piuparts, and if so feel free to scream
at me.
--- End Message ---
--- Begin Message ---
to, 2006-04-27 kello 09:39 +0200, Alexis Sukrieh kirjoitti:
> tags 327242 + moreinfo
> thanks
>
> I wonder if that bug is still reproducible with the last version in sid:
> 2.20.1-2 (the postinst script got changed a lot).
Sorry for the delay. The neverending postinst bug no longer happens.
There are other problems, but I'm too far away from my machines on a
crappy Internet connection and can't be sure I have tested that
correctly. I'll get back to you about that once I'm back home in a
couple of weeks.
--
i++; /* TODO: make this pre-increment - more efficient */
--- End Message ---
