Bug 32825

Summary: cannot rebuild mesa 23.3.3 from Mageia source rpm (works from Git)
Product: Mageia Reporter: Jan Smout <smout.jan>
Component: RPM PackagesAssignee: Giuseppe Ghibò <ghibomgx>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Normal CC: fri, ghibomgx
Version: 9   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: mesa-23.3.3-1.mga9.src.rpm CVE:
Status comment:

Description Jan Smout 2024-02-09 11:30:01 CET
mesa-23.3.3-1.mga9.src.rpm compiles, but then stops at

RPM build errors:
    Empty %files file /home/jan/rpmbuild/BUILD/mesa-23.3.3/debugsourcefiles.list

This is very annoying because I wanted to investigate a SIGSEGV in _glapi_add_dispatch which only occurs in the mageia rpm package, but not when I recompile 23.3.3 from git (with the same build options)


Steps to Reproduce:

1. rpm -ivh mesa-23.3.3-1.mga9.src.rpm
2. rpmbuild -ba SPECS/mesa.spec
Comment 1 Morgan Leijström 2024-02-09 12:43:32 CET
CC packager

CC: (none) => fri, ghibomgx

Comment 2 katnatek 2024-02-09 19:59:09 CET
Can you test the oackages in https://bugs.mageia.org/show_bug.cgi?id=32826 ?
Comment 3 Lewis Smith 2024-02-09 21:00:17 CET
Thank you both for your comments.

Notwithstanding, assigning this to ghibo; expecting a response fro Jan to:
> Can you test the oackages in https://bugs.mageia.org/show_bug.cgi?id=32826

Summary: cannot rebuild mesa 23.3.3 from source rpm => cannot rebuild mesa 23.3.3 from Mageia source rpm (works from Git)
Assignee: bugsquad => ghibomgx

Comment 4 Giuseppe Ghibò 2024-02-09 21:04:29 CET
The main problem could be your system which might include unneeded packages that might interfere on building. To avoid interference, try to build using the packages strictly required for building, e.g. using mock or a minimal chroot.
Comment 5 Jan Smout 2024-02-11 00:04:02 CET
So I followed https://wiki.mageia.org/en/Using_Mock

and successfully built mesa 23.3.3-1 and 23.3.5-1 with:

mock --root mageia-9-x86_64 --rebuild <package.src.rpm> --resultdir <dir>

So indeed something in my build system that interferes. Which begs the question: how are mass rebuilds managed in Mageia? Do you regenerate all rpm's using mock or something similar?

Thank you.
Comment 6 Giuseppe Ghibò 2024-02-11 14:20:58 CET
To get which exact packages might interfere you should compare the logs between the two different builds.

Official build system uses iurt, which is similar to mock but has a different setup. Global massive rebuilds are handled using some script in puppet (which interfaces to iurt).

So I think this bug is resolved and can be closed.
Comment 7 Giuseppe Ghibò 2024-02-11 15:32:24 CET
Furthermore as alternative to rpmbuild for a local build you might try to use 'bm' which allows better interaction with mgarepo (see https://wiki.mageia.org/en/Mgarepo, https://wiki.mageia.org/en/Becoming_a_Mageia_Packager). Of course it's not a replacement for iurt or mock.
Comment 8 Jan Smout 2024-02-11 23:40:28 CET
Thanks Giuseppe for the interesting links. I used to download src.rpm by hand. Will certainly try bm next time.

From log file I could detect only 3 differences: xcb-keysyms-devel, polly-devel and cmake. But after removing those the issue persists.

Maybe a fresh install would bring relief. Anyway, bug can be closed for me.