go-ipfs 0.4.22 fails to build

  • Done
  • quality assurance status badge
Details
3 participants
  • Danny Milosavljevic
  • Jack Hill
  • Michael Gorlick
Owner
unassigned
Submitted by
Michael Gorlick
Severity
normal
Merged with
M
M
Michael Gorlick wrote on 14 Feb 2020 19:16
(address . bug-guix@gnu.org)
CAFLY-sLEM6PrtQmEuh_cY1pRxof7M+DkkJjDaFaU1rhZqJABoQ@mail.gmail.com
guix install go-ipfs
ends with:
building /gnu/store/4a9v3a2f4x2xi82vw9v4rxq8kb5x4y3p-go-ipfs-0.4.22.drv...
| 'build' phasebuilder for
`/gnu/store/4a9v3a2f4x2xi82vw9v4rxq8kb5x4y3p-go-ipfs-0.4.22.drv' failed
with exit code 1
build of /gnu/store/4a9v3a2f4x2xi82vw9v4rxq8kb5x4y3p-go-ipfs-0.4.22.drv
failed
View build log at
'/var/log/guix/drvs/4a/9v3a2f4x2xi82vw9v4rxq8kb5x4y3p-go-ipfs-0.4.22.drv.bz2'.
cannot build derivation
`/gnu/store/q7p2i2wc0w25br0mfwi1wf79690gdxp7-profile.drv': 1 dependencies
couldn't be built
guix install: error: build of
`/gnu/store/q7p2i2wc0w25br0mfwi1wf79690gdxp7-profile.drv' failed
Attachment: file
D
D
Danny Milosavljevic wrote on 14 Feb 2020 19:31
(name . Michael Gorlick)(address . michael.m.gorlick@gmail.com)
20200214193155.660b09ae@scratchpost.org
Hi,

what does the build log /var/log/guix/drvs/4a/9v3a2f4x2xi82vw9v4rxq8kb5x4y3p-go-ipfs-0.4.22.drv.bz2 say?
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl5G558ACgkQ5xo1VCww
uqVlagf+Izy4a4V3cq324mRGUaI0WuQ3YFkXseRrIetpW0wixphfdT3SUEGKimPo
ruWVs3io7D2YVcUkznnTfwuBIP2g/BjyIfwRSnnOLvXLClHif0vnErwxdcVbR4aR
JamXxtMDCQqhn3PEj+9AHVbTsPZtmoTb/wnvbRdZfpqjptRGrJJIZoLsw9Bdr29A
TyPDIKkHgHDgideWlfjEXAmlZ/2ChAeSlIVqonISRvqe2DFBoOoUAh1N/8xZwiW8
CPSZS8dAaUUG8RNqHtYHGsB42vZMbYBGhy9wV9/lqsAd/7k1cLLHI+/YBRLTGPIl
evDBO14Nu94Z4nLWCG0ch3XUFHH6VA==
=mJk9
-----END PGP SIGNATURE-----


J
J
J
Jack Hill wrote on 14 Feb 2020 20:25
(no subject)
(address . control@debbugs.gnu.org)
alpine.DEB.2.20.2002141425080.11123@marsh.hcoop.net
reassign 39605 guix
merge 39605 39603
?
Your comment

This issue is archived.

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

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