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

Re: Fix: cabal-debian 4.33-4 cannot detect GHC built-in packages correctly



Hi,

I tried cabal-debian-4.35.6 in my Debian sid environment with simply
builded by cabal.
And I did not find my issue in its result like following:

-----

    time-locale-compat-0.1.1.3 %
../cabal-debian-4.35.6/dist/build/cabal-debian/cabal-debian
    time-locale-compat-0.1.1.3 % head -14 debian/control
    Source: haskell-time-locale-compat
    Maintainer: Debian Haskell Group
<pkg-haskell-maintainers@lists.alioth.debian.org>
    Priority: extra
    Section: haskell
    Build-Depends: debhelper (>= 10),
     haskell-devscripts-minimal | haskell-devscripts (>= 0.8),
     cdbs,
     ghc,
     ghc-prof,
     libghc-old-locale-dev,
     libghc-old-locale-prof,
    Build-Depends-Indep: ghc-doc,
     libghc-old-locale-doc,
    Standards-Version: 3.9.6
-----

Anyway, I think it is important that fixed cabal-debian package is
uploaded for Debian stretch.

Thanks.

On Wed, Jan 18, 2017 at 4:31 AM, David Fox <ddssff@gmail.com> wrote:
>
>
> On Wed, Jan 11, 2017 at 6:20 PM, Kei Hibino <ex8k.hibino@gmail.com> wrote:
>>
>> Hi,
>>
>> I reported and fixed the problem of cabal-debian around detecting GHC
>> built-ins.
>>
>> cabal-debian searches `package.conf.d' from output of `dpkg -L ghc',
>> for example under `/var/lib/ghc/package.conf.d/',
>> and matches filenames like `base-4.9.0.0.conf'.
>> Under ghc-7.10, checksum suffix exists like
>> `base-4.8.2.0-0d6d1084fbc041e1cded9228e80e264d.conf',
>> but under ghc-8 it does not.
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850920
>>
>>
>> https://lists.alioth.debian.org/pipermail/pkg-haskell-commits/2017-January/043666.html
>>
>> https://lists.alioth.debian.org/pipermail/pkg-haskell-commits/2017-January/043667.html
>>
>> Please review this fix, and upload.
>>
>> Regards
>>
>
> Fortunately or unfortunately, I made extensive changes to this code in
> November:
>
> https://github.com/ddssff/cabal-debian/commit/480f4f099657a20eb46a45c0ca5f492038773e5b
>
> Could you test the latest version of cabal-debian and see if it resolves
> your issue?  Thanks!


Reply to: