Also
Macro forms of system executables SHOULD NOT be used except when there
is a need to allow the location of those executables to be
configurable. For example, rm should be used in preference to %{__rm},
but %{__python3} is acceptable.
сб, 30 мая 2020 г. в 22:51, <ycollette.nospam@xxxxxxx>:
>
> Yes, you're right :)
>
> Here is a link to a build with the %global debug_package %{nil} :
>
> https://download.copr.fedorainfracloud.org/results/ycollet/linuxmao/fedora-32-x86_64/01415804-jamulus/
>
> ----- Mail original -----
> De: "Björn 'besser82' Esser" <besser82@xxxxxxxxxxxxxxxxx>
> À: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx>
> Envoyé: Samedi 30 Mai 2020 21:44:08
> Objet: Re: Packaging problem
>
> Am Samstag, den 30.05.2020, 21:20 +0200 schrieb
> ycollette.nospam@xxxxxxx:
> > Hello,
> >
> > I've got a problem with a package.
> > I am trying to clean up a spec file before sending it to review and
> > I've got an error:
> >
> > erreur : Empty %files file /home/artelys/rpmbuild/BUILD/jamulus-
> > c6b6e3ab02d7ec1e93edeeb8042a89a561924826/debugsourcefiles.list
> >
> > The code is Qt-5 / c++. It's an application which allows to perform
> > live rehearsale via an internet connection.
> >
> > On the gcc / c++ command line, I can see the -g flags.
> >
> > The build section:
> >
> > %{set_build_flags}
> >
> > %_qt5_qmake Jamulus.pro CONFIG+=opus_shared_lib
> >
> > %make_build VERBOSE=1
> >
> > The install section (the qmake file defines no install rule so I must
> > install everything manually):
> >
> > %__install -m 755 -d %{buildroot}/%{_bindir}/
> > %__install -m 755 Jamulus %{buildroot}%{_bindir}/jamulus
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/applications/
> > %__install -m 644 distributions/jamulus.desktop
> > %{buildroot}%{_datadir}/applications/
> >
> > %__install -m 755 -d %{buildroot}/%{_datadir}/pixmaps/
> > %__install -m 644 distributions/jamulus.png
> > %{buildroot}%{_datadir}/pixmaps/
> >
> > How can I build the debug part of the package ?
> >
> > The only solution I've found is to add:
> >
> > %global debug_package %{nil}
> >
> > At the beginning of the spec file ...
>
>
> Without a scratch build and/or a link to the spec file / srpm its hard
> to help, I guess…
>
> Cheers
> Björn
>
> _______________________________________________
> 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
> _______________________________________________
> 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
_______________________________________________
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
