Your message dated Fri, 17 Nov 2006 04:35:19 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393273: enchant can now be requequed
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: enchant
Severity: serious
Version: 1.3.0-1
Hi,
libhunspell-dev is (and never was, so it's not RC) not available on ARM
because it fails the testsuite:
$ rmadison libhunspell-dev
libhunspell-dev | 1.1.4-3 | testing | alpha, amd64, i386, ia64,
m68k, mips, mipsel, powerpc, s390, sparc
libhunspell-dev | 1.1.4-3 | unstable | alpha, amd64, hurd-i386,
i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
libhunspell-dev | 1.1.4-3+b1 | testing | hppa
libhunspell-dev | 1.1.4-3+b1 | unstable | hppa
Therefore, it FTBFSes on arm:
http://buildd.debian.org/fetch.cgi?pkg=enchant;ver=1.3.0-2;arch=arm;stamp=1160935593
Upstream known but either forgot it or didn't fix it yet.
I guess I should talk to him again...
Regards,
Rene
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-powerpc
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Fri, Nov 17, 2006 at 02:13:43PM +0200, Riku Voipio wrote:
> unblock 393273 with 396528
> thanks
> Blocking bug has been fixed, thanks to Sesse. After enchant
> has been requequed, this RC bug can be closed. Food for thought:
Then I would say this bug can be closed now, because enchant will be
requeued automatically as soon as hunspell/arm enters the archive, and it's
already been built.
> 1) Shouldn't blocking bugs be atleast same severity as the bug they block?
Not inherently, no. A blocking bug may only be blocking because a
maintainer *chooses* to make it so.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
