’corrode’ fails because ’ghc-language-c’ wrong version

  • Done
  • quality assurance status badge
Details
One participant
  • zimoun
Owner
unassigned
Submitted by
zimoun
Severity
normal
Z
Z
zimoun wrote on 9 Oct 2020 03:25
(address . bug-guix@gnu.org)
86ft6o8a2k.fsf@gmail.com
Dear,

Using Guix a0d4aa2, the package ’corrode’ fails to build because:

Toggle snippet (5 lines)
Configuring corrode-0.1.0.0...
Setup.hs: Encountered missing dependencies:
language-c >=0.4 && <0.6

and the package ’ghc-language-c’ had been updated to 0.8.1 by the commit
19b29882878a6558e5f16d587265eb3a0c0cdec6 (Jan. 2017). So the package is
probably broken since 3 years.

Four fixes are possible:

1. add the package ’ghc-language-c@0.5.0’ introduced by
2d2388e243d31f00b31b36b8ada76876b6fdacf2.
2. turn the package as “private” or at least deprecated.
3. move it to guix-past.
4. remove it. (Note that upstream is stalling; last commit 4 years
ago.)


I am in favor of option #4. Or maybe someone wants to fix?


WDYT?

All the best,
simon
Z
Z
zimoun wrote on 21 Oct 2021 14:19
(address . 43874-done@debbugs.gnu.org)
86ilxqefjf.fsf@gmail.com
Hi,

On Fri, 09 Oct 2020 at 03:25, zimoun <zimon.toutoune@gmail.com> wrote:

Toggle quote (22 lines)
> Using Guix a0d4aa2, the package ’corrode’ fails to build because:
>
> Configuring corrode-0.1.0.0...
> Setup.hs: Encountered missing dependencies:
> language-c >=0.4 && <0.6
>
> and the package ’ghc-language-c’ had been updated to 0.8.1 by the commit
> 19b29882878a6558e5f16d587265eb3a0c0cdec6 (Jan. 2017). So the package is
> probably broken since 3 years.
>
> Four fixes are possible:
>
> 1. add the package ’ghc-language-c@0.5.0’ introduced by
> 2d2388e243d31f00b31b36b8ada76876b6fdacf2.
> 2. turn the package as “private” or at least deprecated.
> 3. move it to guix-past.
> 4. remove it. (Note that upstream is stalling; last commit 4 years
> ago.)
>
>
> I am in favor of option #4. Or maybe someone wants to fix?

This option #4 is done by b97f549b14402421fcfb360ddd4cff7de93b9af0. So,
closing!

All the best,
simon
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 43874@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 43874
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch