On Tue, Nov 26, 2024 at 12:14:08PM +0100, Florian Weimer wrote: > * Richard W. M. Jones: > > > This is a weird one: > > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=125988419 > > > > + /usr/bin/find-debuginfo -j48 --strict-build-id -m -i --build-id-seed 1.55.2-1.fc42 --unique-debug-suffix -1.55.2-1.fc42.x86_64 --unique-debug-src-base libguestfs-1.55.2-1.fc42.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /builddir/build/BUILD/libguestfs-1.55.2-build/libguestfs-1.55.2 > > find-debuginfo: starting > > Extracting debug info from 13 files > > objcopy: unable to copy file '/builddir/build/BUILD/libguestfs-1.55.2-build/BUILDROOT/usr/lib64/perl5/vendor_perl/auto/Sys/Guestfs/Guestfs.so'; reason: Permission denied > > *** ERROR:: GDB exited with exit status 1 during index generation > > > > The same thing happens on each architecture, for the same file. > > This suggests that gdb-add-index is trying to overwrite that file in > place it should never do that. Our long-standing assumption is that a > broken gdb-add-index is very unlikely to produce corrupted production > binaries, but if overwrites in place, that seems a bit overly > optimistic. See: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/EDJURPPJA7CZMXAMGNKQWYNWWFKEEQTS/ It runs effectively the command 'objcopy Guestfs.so Guestfs.so', thus updating the file in place. The objcopy manual doesn't say whether or not it's allowed for 'infile' and 'outfile' to be the same. It does say that you can omit 'outfile': infile outfile The input and output files, respectively. If you do not specify outfile, objcopy creates a temporary file and destructively renames the result with the name of infile. But anyway, whether or not it's right, that's what it tries to do. It fails because the upstream build system sets the file to 0555, so it's not writable. Previously, rpm(?) ignored errors from find-debuginfo, so the debuginfo was silently not generated. However that changed recently so now errors cause the build to fail, hence why we're seeing these reports now. The fix / workaround (in %install) was to make the file writable. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- _______________________________________________ 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
