I'm not overly familiar with Go but generally this is the result of a compile-time flag stripping debug symbols from binaries, then when rpmbuild goes to do exactly that there's nothing there for it to grab.
Look for compile-time flags that mention stripping (or not stripping) symbols. On Wed, Jan 17, 2024 at 11:39 AM Alessandro Baggi < [email protected]> wrote: > Hi list, > I'm creating an RPM package for gocryptfs on AlmaLinux 9.3 > I'm using the source with deps (vendoring) because deps are too much. > > During the process rpmbuild returns: > > gocryptfs-debugsource-2.4.0-1.el9.x86_64 > error: Empty %files file > /root/rpmbuild/BUILD/gocryptfs_v2.4.0_src-deps/debugsourcefiles.list > > To avoid this I can add: > > %global debug_package %{nil} > > and the problem is solved also if the build-id links are generated. > > But, here there is a problem. I read that for $arch packages a debug > package will be created and if some error is reported there is something > wrong on the SPEC file. > > Why debugsourcefiles.list is empty? What is causing this? > > Thank you in advance. > > Alessandro. > _______________________________________________ > AlmaLinux Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- Jonathan Wright AlmaLinux Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
