On Mon, Feb 20, 2023 at 10:19 PM Julian Sikorski <[email protected]> wrote: > > Am 20.02.23 um 19:14 schrieb Orion Poplawski: > > On 2/20/23 10:46, Fabio Valentini wrote: > >> On Mon, Feb 20, 2023 at 6:43 PM Julian Sikorski <[email protected]> > >> wrote: > >>> > >>> Hello, > >>> > >>> FTBFS bug was filed against mame [1]. Unfortunately, the corresponding > >>> build [2] has already been deleted. This is not ideal from maintainer > >>> perspective as it effectively is a bug with no info provided whatsoever. > >>> Not to mention being quite wasteful from the resources perspective as > >>> mame builds take quite a while. > >>> While not much can be done now, can we make sure that the mass rebuild > >>> builds do not get garbage collected, or at least the build logs are > >>> saved somewhere? Thanks. > >> > >> As far as I know, at least some form of truncated build.log used to > >> get attached when FTBFS bugs were filed after a mass rebuild ... maybe > >> this time this wasn't possible, because bugs were reported *weeks* > >> after the mass rebuild? > >> > >> And I agree, having no logs at all for something that takes a long > >> time to build is annoying :( > > > > Well, if your package is tracked by koschei (which I highly recommend), > > you likely could get a current build log from there. > > > Good idea, this allowed me to get further. > I have hit another issue: > > error: Recognition of file > "/builddir/build/BUILDROOT/mame-0.251-3.fc39.x86_64/usr/bin/mame" > failed: mode 100755 , dynamically linked, interpreter > /lib64/ld-linux-x86-64.so.2, > BuildID[sha1]=4cb9f6821033586b869d516b865fa1d8e7b8b5f9, for GNU/Linux > 3.2.0 Note section size too big (137005660 > 134217728) (Invalid argument) > > I am already building with -g1. What can be done about the error above? > Thanks! > > Best regards, > Julian
Hi Julian, This issue is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=2167964 . Regards, Lukas
_______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
