Bug#701059: [Pkg-haskell-maintainers] Bug#701059: Bug#701059: haskell-conduit: FTBFS: test failure form doctest adopted

2013-02-22 Thread Hiroyuki Yamamoto

Joachim Breitner wrote:

Am Freitag, den 22.02.2013, 21:09 +0900 schrieb Hiroyuki Yamamoto:

Joachim Breitner wrote:

Am Donnerstag, den 21.02.2013, 13:10 +0900 schrieb Debian ppc64 build
daemon:

Build test of haskell-conduit fails form ver. 0.5.5 which adopted doctest.
http://buildd.debian-ports.org/status/logs.php?pkg=haskell-conduit&arch=ppc64

Unfortunately, because transitions of ghc is not applied to experimental 
repository,
this error is not checked at present except on ppc64 port.
https://buildd.debian.org/status/package.php?p=haskell-conduit&suite=experimental
http://buildd.debian-ports.org/status/package.php?p=haskell-conduit&suite=experimental

So, since it may be a bug peculiar to doctest on ppc64 port, this is reported by 
"Severity:  important".


doctest requires GHCi, which is not supported on all architectures. The
cleanest fix would be if doctest would detect this situation and fail
gracefully: https://github.com/sol/doctest-haskell/issues/46


OK. This bug is under jurisdiction of haskell-doctest.

Although it can be understood that this bug should be solved at haskell-doctest,
if it is taken into consideration that GHCi is supporting architectures only
amd64, i386, hurd-i386, kfreebsd-amd64, kfreebsd-i386, powerpc, sparc, 
powerpcspe,
and not supporting official armel, armhd, ia64, mips, mipsel, s390, s390x,
and unofficial alpha, hppa, m68k, ppc64, sh4, sparc64, x32,
it may be worthy of considering avoiding the test by doctest.


Yes, but it should be avoided centrally, i.e. in doctest itself. No need
to encode the information “doctest needs GHCi” in every packages that
uses doctest.


Since libghc-conduit-dev is build-depended from many other haskell packages,
it blocks building many packages now.
http://buildd.debian-ports.org/status/architecture.php?a=ppc64&suite=experimental

If another wishlist BTS to haskell-conduit about this is needed, shall I post 
it?


no need, as there is no change to conduit required. I’ll just upload the
new doctest as soon as it is released.


OK.
I'll give-back to build haskell-conduit on ppc64 as soon as new haskell-doctest 
built.


But it is surely a problem that GHCi's supporting architectures are very few,
only Intel architectures, 32-bit PowerPC, and 32-bit SPARC.

These days, there is a tendency that haskell packages depending on ghc-ghci 
increase,
it has been really troubled a little.

Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA  91AC 3A10 59C6 5203 04DC


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#701059: [Pkg-haskell-maintainers] Bug#701059: Bug#701059: haskell-conduit: FTBFS: test failure form doctest adopted

2013-02-22 Thread Joachim Breitner
Hi,

Am Freitag, den 22.02.2013, 21:09 +0900 schrieb Hiroyuki Yamamoto:
> Joachim Breitner wrote:
> > Am Donnerstag, den 21.02.2013, 13:10 +0900 schrieb Debian ppc64 build
> > daemon:
> >> Build test of haskell-conduit fails form ver. 0.5.5 which adopted doctest.
> >> http://buildd.debian-ports.org/status/logs.php?pkg=haskell-conduit&arch=ppc64
> >>
> >> Unfortunately, because transitions of ghc is not applied to experimental 
> >> repository,
> >> this error is not checked at present except on ppc64 port.
> >> https://buildd.debian.org/status/package.php?p=haskell-conduit&suite=experimental
> >> http://buildd.debian-ports.org/status/package.php?p=haskell-conduit&suite=experimental
> >>
> >> So, since it may be a bug peculiar to doctest on ppc64 port, this is 
> >> reported by "Severity:  important".
> >
> > doctest requires GHCi, which is not supported on all architectures. The
> > cleanest fix would be if doctest would detect this situation and fail
> > gracefully: https://github.com/sol/doctest-haskell/issues/46
> 
> OK. This bug is under jurisdiction of haskell-doctest.
> 
> Although it can be understood that this bug should be solved at 
> haskell-doctest,
> if it is taken into consideration that GHCi is supporting architectures only
> amd64, i386, hurd-i386, kfreebsd-amd64, kfreebsd-i386, powerpc, sparc, 
> powerpcspe,
> and not supporting official armel, armhd, ia64, mips, mipsel, s390, s390x,
> and unofficial alpha, hppa, m68k, ppc64, sh4, sparc64, x32,
> it may be worthy of considering avoiding the test by doctest.

Yes, but it should be avoided centrally, i.e. in doctest itself. No need
to encode the information “doctest needs GHCi” in every packages that
uses doctest.

> Since libghc-conduit-dev is build-depended from many other haskell packages,
> it blocks building many packages now.
> http://buildd.debian-ports.org/status/architecture.php?a=ppc64&suite=experimental
> 
> If another wishlist BTS to haskell-conduit about this is needed, shall I post 
> it?

no need, as there is no change to conduit required. I’ll just upload the
new doctest as soon as it is released.

Greetings,
Joachim


-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata



signature.asc
Description: This is a digitally signed message part