Sorry for the late reply. I just got back to this issue.
> In general this (should) only happen if the binaries are really
> identical (e.g. when one of the packages build requires the other, but
> instead of linking/rebuilding some sources it simply copies a binary
> directly).
>
> The build-id
On Thu, Mar 4, 2021 at 1:15 AM Jerry James wrote:
> Once that is fixed, haxe should build in Rawhide again. Also, Andy,
> I'd like to point out that ocaml-luv is now available in Fedora, so it
> should be possible to update to haxe 4.2.x. Regards,
I've just fixed it by upgrading haxe to 4.2.1.
Hi Jerry,
On Tue, 8 Dec 2020, 07:38 Jerry James, wrote:
> Hi all,
>
> I've BCCed the maintainers of the following packages to see if they
> are okay with this:
> - ocaml-migrate-parsetree (update to 1.8.0)
> - ocaml-sedlex (update to 2.2)
>
I'm fine with this. Thanks for taking care of the upda
Hi list,
Re. https://bugzilla.redhat.com/show_bug.cgi?id=1896901
Since haxe-4.1.3-4 and nekovm-2.3.0-4, both nekovm and haxe packages contains
"/usr/lib/.build-id/b0/aed4ddf2d45372bcc79d5e95d2834f5045c09c".
The nekovm one is a symlink to "/usr/bin/neko". The haxe one to
"/usr/bin/haxelib".
Both
