On Saturday, April 19 2025, I wrote:

> On Saturday, April 19 2025, Chris Hofstaedtler wrote:
>
>> On Sat, Apr 19, 2025 at 01:27:21PM +0200, Chris Hofstaedtler wrote:
>>> On Sat, Apr 19, 2025 at 12:45:08AM -0400, Sergio Durigan Junior wrote:
>>> > On Monday, April 07 2025, Graham Inggs wrote:
>>> > > The recent upload of patchelf 0.18.0-1.2 FTBFS on mips64el [1].  I've
>>> > > copied what I hope is the relevant part of the log below.
>>> > 
>>> > Thanks, Graham.
>>> > 
>>> > I tried reproducing the issue but apparently it's gone.  I've given back
>>> > the build, hopefully it will succeed this time.  I'll check back
>>> > tomorrow.
>>> 
>>> Didn't help:
>>> https://buildd.debian.org/status/logs.php?pkg=patchelf&ver=0.18.0-1.2&arch=mips64el
>>> https://buildd.debian.org/status/fetch.php?pkg=patchelf&arch=mips64el&ver=0.18.0-1.2&stamp=1745055768&raw=0
>>
>> One of the commits added in -1.2 is:
>>
>> $ head fix-replace-add-needed-armhf.patch
>> From 1c443aa1c7b8c8bcafde796f2e41e4abce3793e1 Mon Sep 17 00:00:00 2001
>> From: matoro <mat...@users.noreply.github.com>
>> Date: Sat, 4 Nov 2023 20:01:22 -0400
>> Subject: [PATCH] Fix page size on Alpha
>>
>> Upstream meanwhile reverted it:
>> https://github.com/NixOS/patchelf/pull/541/commits/a9d3f085ffdc1730c722998ef95a632e2f76dc8f
>
> I'll backport and upload this to unstable.  I believe it makes sense to
> do it regardless.
>
>> Unfortunately, reproducing the build failure does not seem possible 
>> on eberlin.d.o.
>
> That's what I was trying yesterday, and I noticed that it's not possible
> to reproduce the problem on eberlin.  It's tough to debug this without
> reproducing the problem.
>
> If the backport above doesn't solve the FTBFS, I'm inclined to ignore
> the result on mips64el.

It didn't work, the FTBFS still happens.

I'll keep debugging it.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

Attachment: signature.asc
Description: PGP signature

Reply via email to