Opened 20 months ago

Closed 13 months ago

Last modified 13 months ago

#65773 closed defect (fixed)

exa @0.10.1_3+doc+git – Failure to build revision 3, is this a libgit2 issue or something else?

Reported by: Gandoon (Erik Hedlund) Owned by: harens (Haren S)
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: Cc: chadcatlett (Chad Catlett), mascguy (Christopher Nielsen), cooljeanius (Eric Gallager)
Port: exa

Description (last modified by Gandoon (Erik Hedlund))

exa @0.10.1_3+doc+git and @0.10.1_3+doc-git fails to build on MacOS 10.15.7 (19H2026). Despite first suspecting this to be an issue with libgit2, which has been an obvious issue for a while now (see also recently closed #65733) – I have had to remain at libgit2 @1.3.0_1+threadsafe due to libgit2 @1.5.0_0+threadsafe breaking the installed exa, calling for a rebuild which ultimately fails.

Thus, I tested to build revision 3 with the new libgit2 (@1.5.0_0), the old (@1.3.0_1), and with the -git modifier, but either of these also resulted in a failed builds of revision 3. I enclose log files for the failed builds of the +git variant with with libgit2 @1.3.0_1+threadsafe and libgit2 @1.5.0_1+threadsafe active respectively. Finally, I also enclose the log for the failed -git variant build of revision 3, tried in an attempt to confirm that it was indeed libgit2 that broke the builds. But, as this also failed, there might be something else going on here that I can't really put my finger on at this point.

Attachments (4)

exa_main-0.10.1_2+doc+git.log (120.5 KB) - added by Gandoon (Erik Hedlund) 20 months ago.
exa_main-upgrade_to_0.10.1_3+doc+git.log (120.5 KB) - added by Gandoon (Erik Hedlund) 20 months ago.
exa_main-upgrade_to_0.10.1_3+doc-git.log (129.3 KB) - added by Gandoon (Erik Hedlund) 20 months ago.
exa_mavericks_main.log (112.5 KB) - added by tehcog (tehcog) 20 months ago.
main.log

Download all attachments as: .zip

Change History (17)

Changed 20 months ago by Gandoon (Erik Hedlund)

Changed 20 months ago by Gandoon (Erik Hedlund)

Changed 20 months ago by Gandoon (Erik Hedlund)

comment:1 Changed 20 months ago by Gandoon (Erik Hedlund)

Please disregard the apparent erroneous revision number of the first log file, it is also a revision 3 build, I missed that number when uploading it.

comment:2 Changed 20 months ago by Gandoon (Erik Hedlund)

Description: modified (diff)

comment:3 Changed 20 months ago by Gandoon (Erik Hedlund)

Description: modified (diff)

comment:4 Changed 20 months ago by jmroot (Joshua Root)

Cc: chadcatlett added
Owner: set to harens
Status: newassigned

comment:5 Changed 20 months ago by mascguy (Christopher Nielsen)

Cc: mascguy added

Changed 20 months ago by tehcog (tehcog)

Attachment: exa_mavericks_main.log added

main.log

comment:6 Changed 20 months ago by tehcog (tehcog)

Fails on mavericks as well. Please see attached log file.

comment:7 Changed 20 months ago by mascguy (Christopher Nielsen)

Yes, this port is failing to build across-the-board, apart from ARM:

https://ports.macports.org/port/exa/details/

comment:8 Changed 20 months ago by Knapoc

It fails due to an issue with rust https://github.com/ogham/exa/issues/1068

comment:9 Changed 20 months ago by ryandesign (Ryan Carsten Schmidt)

That issue says:

This is fixed with rust 1.62.0

So this will be fixed when #65417 is fixed.

comment:10 Changed 19 months ago by cooljeanius (Eric Gallager)

Cc: cooljeanius added

comment:11 Changed 13 months ago by Gandoon (Erik Hedlund)

Just a heads-up. I expect that this ticket can be closed since Rust now is at @1.68.0_0 and exa built as expected since somewhere around @1.66.

comment:12 Changed 13 months ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed

Thanks for letting us know. I forced builds of exa on the buildbot to make the binaries available.

comment:13 in reply to:  12 Changed 13 months ago by Gandoon (Erik Hedlund)

Replying to ryandesign:

Thanks for letting us know. I forced builds of exa on the buildbot to make the binaries available.

Great, cheers :)

Note: See TracTickets for help on using tickets.