[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#789365: transition: ghc-7.8

On 24/06/15 16:12, Joachim Breitner wrote:
> Hi,
> Am Dienstag, den 23.06.2015, 15:05 +0200 schrieb Joachim Breitner:
>> * leksah ought to be removed from testing:
>>    https://bugs.debian.org/789521
> ✓
>>  * Then I’m waiting for these binNMUs to be built
>>    https://buildd.debian.org/status/package.php?p=haskell-happstack-server+haskell-reflection+haskell-xml-conduit&suite=sid&a=mips,mipsel
> ✓
>>  * And then the youngest upload (haskell-mono-traversable) needs to
>>    age (3 more days):
>>    https://packages.qa.debian.org/h/haskell-mono-traversable.html
> There was a problem with the gitit package, fixed by a swift upload of
> Clint right now. So the counter is back to 5, unless someone in the
> release team gets impatient and age hints haskell-mono-traversable and
> gitit.
> https://release.debian.org/transitions/html/haskell.html seems to
> contain only gitit (still waiting for the mips build) and false
> positives.

This may need a binNMU:

haskell-trifecta (1.4.3-1 to
    Maintainer: Debian Haskell Group
    9 days old (needed 5 days)
    libghc-trifecta-dev/ppc64el unsatisfiable Depends: libghc-charset-dev-
    libghc-trifecta-dev/ppc64el unsatisfiable Depends: libghc-comonad-dev-4.2.5-c2e64
    libghc-trifecta-dev/ppc64el unsatisfiable Depends: libghc-lens-dev-
    libghc-trifecta-dev/ppc64el unsatisfiable Depends: libghc-reducers-dev-
    libghc-trifecta-dev/ppc64el unsatisfiable Depends: libghc-semigroups-dev-0.15.3-77447
    libghc-trifecta-prof/ppc64el unsatisfiable Depends: libghc-charset-prof-
    libghc-trifecta-prof/ppc64el unsatisfiable Depends: libghc-comonad-prof-4.2.5-c2e64
    libghc-trifecta-prof/ppc64el unsatisfiable Depends: libghc-lens-prof-
    libghc-trifecta-prof/ppc64el unsatisfiable Depends: libghc-reducers-prof-
    libghc-trifecta-prof/ppc64el unsatisfiable Depends: libghc-semigroups-prof-0.15.3-77447

I have also added a few more age-days. Mostly missing gitit at this point.


Reply to: