update_excuses zope (also related to Bug #122443)
* zope (2.3.3-1 to 2.4.2-0.2)
* Maintainer: Gregor Hoffleit
* 36 days old (needed 10 days)
* Valid candidate
auric:~> madison zope
zope | 2.1.6-10 | stable | source, alpha, arm, i386, m68k, powerpc, sparc
zope | 2.3.3-1 | testing | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
zope | 2.3.3-1 | unstable | hurd-i386, sh
zope | 2.4.2-0.2 | unstable | source, alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
Well zope has a critical bug (#122443) but I wonder about the time after
the 10 days zope was in unstable without critical bugs and compiled for
all architectures. Why did it not went into testing earlier?
On the other hand we have to care for the critical bug of course. Any
opinion from the maintainer? The current version was done via NMU
but anyway I think it is important to get Zope 2.4.2 into testing
because we want to get rid of the old Python stuff and zope-2.3.3
depends from Python 1.5.
Anybody out there who is able to reproduce the bug?
All went fine for me at 4 different machines now. Today also
done on Sparc architecture - all went fine and is running OK
If there is nobody who can reproduce the problem and the reporter of
the bug can not give any further information (perhaps a disk crash
scrambled postinst file or something else) we should close this bug
with "can not reproduce". If it occures also on other machines we
have to care about this quickly.