Acknowledgement sent
to Jean-Pierre De Jesus Diaz <jean@foundation.xyz>:
New bug report received and forwarded. Copy sent to guix-patches@gnu.org.
(Tue, 03 Sep 2024 08:53:02 GMT) (full text, mbox, link).
Jean-Pierre De Jesus Diaz <jean@foundation.xyz> skribis:
> This fixes the compilation of coq-ide, frama-c and why3.
>
> * gnu/packages/ocaml.scm (ocaml-cairo2): Build only cairo2 dune package,
> and remove lablgtk and gtk-2 from inputs.
>
> [...]
> + (list ;; FIXME: lablgtk@2 package does not build, so skip building the
> + ;; cairo-pango and cairo-gtk packages. Once fixed, add lablgtk
> + ;; back to inputs and remove this.
> + #:package "cairo2"))
A fix for lablgtk was pushed yesterday in
0aa66ec0b0bef39591ddae3d8d06ac0fa71f03bb, so ocaml-cairo2 should build
now.
Hello,
Sorry for the noise then, didn't notice a fix was already there.
I'm still a bit of a noob with Debbugs, so is there a way to close the
issue from my side?
On Tue, Sep 3, 2024 at 10:06 AM Guillaume Le Vaillant <glv@posteo.net> wrote:
>
> Jean-Pierre De Jesus Diaz <jean@foundation.xyz> skribis:
>
> > This fixes the compilation of coq-ide, frama-c and why3.
> >
> > * gnu/packages/ocaml.scm (ocaml-cairo2): Build only cairo2 dune package,
> > and remove lablgtk and gtk-2 from inputs.
> >
> > [...]
> > + (list ;; FIXME: lablgtk@2 package does not build, so skip building the
> > + ;; cairo-pango and cairo-gtk packages. Once fixed, add lablgtk
> > + ;; back to inputs and remove this.
> > + #:package "cairo2"))
>
> A fix for lablgtk was pushed yesterday in
> 0aa66ec0b0bef39591ddae3d8d06ac0fa71f03bb, so ocaml-cairo2 should build
> now.
Reply sent
to Guillaume Le Vaillant <glv@posteo.net>:
You have taken responsibility.
(Tue, 03 Sep 2024 11:34:02 GMT) (full text, mbox, link).
Notification sent
to Jean-Pierre De Jesus Diaz <jean@foundation.xyz>:
bug acknowledged by developer.
(Tue, 03 Sep 2024 11:34:02 GMT) (full text, mbox, link).
Jean-Pierre De Jesus Diaz <jean@foundation.xyz> skribis:
> Hello,
>
> Sorry for the noise then, didn't notice a fix was already there.
>
> I'm still a bit of a noob with Debbugs, so is there a way to close the
> issue from my side?
No problem. To close an issue, you can just send an email to
<nnnnnn-done@debbugs.gnu.org> or <nnnnnn-close@debbugs.gnu.org> (where
nnnnnn is the issue number), like I did with this email.
Debbugs is free software and licensed under the terms of the
GNU Public License version 2. The current version can be
obtained from https://bugs.debian.org/debbugs-source/.