Thank you so much for taking care of this and diving that deep into the issue Mamoru! <3
This is what I love Open Source Communities and in particular the Fedora Community for.
I wouldn't have managed to get that worked out beneath my usual work and childcare.
Regards <3
Dominic
On Thu, Aug 14, 2025 at 9:16 AM Mamoru TASAKA <mtasaka@xxxxxxxxxxxxxxxxx> wrote:
Mamoru TASAKA wrote on 2025/08/13 23:41:
> Dan Horák wrote on 2025/08/13 19:29:
>> On Wed, 13 Aug 2025 12:14:16 +0200
>> Dominic Hopf via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>>> Greetings,
>>>
>>> I'm currently trying to take care of
>>> https://bugzilla.redhat.com/show_bug.cgi?id=2385207 but get stuck in
>>> understanding what happened here as the package itself got its last update
>>> on 2024-10-28. Since then there only were (Mass)? Rebuilds for the package.
>>>
>>> Basic error message is, that check-rpaths found some rpath in the code:
>>>
>>> ERROR 0001: file '/usr/bin/ncmpcpp' contains a standard runpath
>>> '/usr/lib' in [/usr/lib]
>>>
>>> (Compare to
>>> https://bugzilla-attachments.redhat.com/attachment.cgi?id=2100887)
>>>
>>> As this started happening just with a Mass Rebuild in July without any
>>> other changes to the package I wonder if something changed with handling
>>> rpaths in the last year?
>>
>> a change in the toolchain might cause the issue
>>> Otherwise I appreciate any hint which leads me to solve this issue.
>>
>> the guidelines have a section about RPATH
>> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_beware_of_rpath
>>
>>
>> Dan
>
> With the hint from koschei results:
> https://koschei.fedoraproject.org/package/ncmpcpp
>
> what I've confirmed for now is that downgrading
>
> bash-5.3.0-2.fc43 -> bash-5.2.37-3.fc43
>
> makes the above rpath complaint disappear, and
> it seems that these two bash's generate a slightly different
> config.log or src/Makefile.
> Especially the result of "BOOST_LDPATH" is different:
> which I guess is causing this issue.
So actually this is due to bash 5.3 behavior change, which now
treats "cd" with null string as error as specified by POSIX.1-2024,
which results in included boost.m4 behavior change.
I've put some comments on https://bugzilla.redhat.com/show_bug.cgi?id=2385207
Regards,
Mamoru
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
