hikari 2.3.3 build failure

  • Done
  • quality assurance status badge
Details
4 participants
  • bdju
  • Josselin Poiret
  • Ludovic Courtès
  • Simon Tournier
Owner
unassigned
Submitted by
bdju
Severity
normal
B
J
J
Josselin Poiret wrote on 10 May 2023 21:23
877ctgdm93.fsf@jpoiret.xyz
Hi,

"bdju" via Bug reports for GNU Guix <bug-guix@gnu.org> writes:

Toggle quote (4 lines)
> guix (GNU Guix) e0c35d1578c10a8fe27c8372f3a8bb5dd88b01b8
> guix system
> hikari build log attached

I tried to look into it before the core-updates merge, but it seems that
hikari is not maintained anymore, so I don't expect it to work with
newer wlroots.

Best,
--
Josselin Poiret
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEOSSM2EHGPMM23K8vUF5AuRYXGooFAmRb7xgQHGRldkBqcG9p
cmV0Lnh5egAKCRBQXkC5FhcaimxBC/0dDUIsbsa5FHzpJWrdHjnAtcG9/AwJlp2d
e7vdPH4SeYvP7fD1jKatv6SubZqTs0Iqj3/gGEyb+IY3zn5PhdoGmFdCHTNr3mNA
ypM5G/GGfshYVBfXsiQvGJt9hrJpn62dsdl5SSjtgk4zjEQOoUhwxHwF1dS859lL
zftTZ2A7UXTk6L/NqbIh/JYWXXS5z1eJ1zt9BIFPA6d0yYDMrYGcDadV5ff/8kFP
OB8Q0vfBKA/iEocx1+JIMiULeJDDSask24GpAim4fu+9NoCtKc9qDCt/yDOhRyUF
OPdi1B/K2kWw2d4o9IUgV2a501zI4EGIJE19t7LacKtCxbfqKYbmBqOUHUiz2pIh
Ki4SxLUxhp4r03nYFfsY7uNZtfsfGhiyDZajYqOtYw5aaznkNvfki+soVRveh+G6
lrmskGszFzmxKUTm+rsmDyzNWdpxofMnTG5XrmUrz3Zg3J7+WlKvGL2sH+v6clZq
Dxq6WNGvnPgipq8fyx18iyuzOFxvAak=
=iN47
-----END PGP SIGNATURE-----

S
S
Simon Tournier wrote on 11 May 2023 14:45
87sfc33uky.fsf@gmail.com
Hi,

On mer., 10 mai 2023 at 21:23, Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:

Toggle quote (4 lines)
> I tried to look into it before the core-updates merge, but it seems that
> hikari is not maintained anymore, so I don't expect it to work with
> newer wlroots.

In that case, do we plan to remove this package hikari?

Cheers,
simon
L
L
Ludovic Courtès wrote on 21 Mar 2024 15:15
control message for bug #63426
(address . control@debbugs.gnu.org)
87le6bvfg0.fsf@gnu.org
close 63426
quit
?
Your comment

This issue is archived.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 63426
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