On Tue, Dec 21, 2021 at 6:47 AM Demi Marie Obenour
<demiobenour@xxxxxxxxx> wrote:
>
> On 12/20/21 8:09 AM, Panu Matilainen wrote:
> > Having to disable debug packages practically always indicates a bug in
> > the package - either packaging, upstream or both.
> >
> > Typical causes for "error: Empty %files file
> > <...>/debugsourcefiles.list" are missing debug info in the build (eg -g
> > flag of gcc) and building outside the designated build directory.
> > Unfortunately diagnosing these from rpm isn't easy.
> >
> > "%global debug_package %{nil}" is always a workaround and never a fix.
> >
> > - Panu -
>
> Is the only exception when the debuginfo for a huge package consumes too
> much memory or disk space?
If memory or disk space are the constraints that prevent debug
packages, it would probably be better to reduce debuginfo level during
compilation process instead of ignoring it at the RPM level.
Fabio
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure
