Hello,
Since my last message, I have tried to reproduce this in several ways,
e.g. an sbuild chroot in both qemu-user-static and on actual hardware
(Raspberry Pi 2), and also a direct build on an armhf VM. It always
builds successfully. Since then, there has been a new upstream release
of
On 2024-03-22 10:35:06 -0400, Ben Westover wrote:
> Sebastian,
>
> I can't seem to reproduce this on an armhf chroot, VM, or actual hardware
> (all unstable). When were you last able to reproduce this? It's possible
> (since unstable has changed rapidly in recent days) that the problem was
>
Sebastian,
I can't seem to reproduce this on an armhf chroot, VM, or actual
hardware (all unstable). When were you last able to reproduce this? It's
possible (since unstable has changed rapidly in recent days) that the
problem was something external that fixed itself between then and now.
Hi Ben
On 2024-03-20 22:54:58 -0400, Ben Westover wrote:
> Hello,
>
> The package builds fine on my armhf VM as well as a Raspberry Pi 2 running
> armhf Debian bare metal. Maybe some transitioning library caused this issue?
> If xmrig gets binNMU'd, it will probably build successfully. I would
Hello,
The package builds fine on my armhf VM as well as a Raspberry Pi 2
running armhf Debian bare metal. Maybe some transitioning library caused
this issue? If xmrig gets binNMU'd, it will probably build successfully.
I would do it, but I'm not a Debian Developer. Could you do it?
Thanks,
Source: xmrig
Version: 6.21.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=xmrig=armhf=6.21.1%2Bdfsg-1%2Bb1=1710494247=0
cd
6 matches
Mail list logo
