This information is probably missing:
/usr/lib/rpm/sepdebugcrcfix: Updated 4 CRC32s, 0 CRC32s did match.
12830 blocks
+ '[' '%{buildarch}' = noarch ']'
+ QA_CHECK_RPATHS=1
+ case "${QA_CHECK_RPATHS:-}" in
+ /usr/lib/rpm/check-rpaths
*******************************************************************************
*
* WARNING: 'check-rpaths' detected a broken RPATH and will cause 'rpmbuild'
* to fail. To ignore these errors, you can set the '$QA_RPATHS'
* environment variable which is a bitmask allowing the values
* below. The current value of QA_RPATHS is 0x0000.
*
* 0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
* issue but are introducing redundant searchpaths without
* providing a benefit. They can also cause errors in multilib
* environments.
* 0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
* nor relative filenames and can therefore be a SECURITY risk
* 0x0004 ... insecure RPATHs; these are relative RPATHs which are a
* SECURITY risk
* 0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
* RPATHs; this is just a minor issue but usually unwanted
* 0x0010 ... the RPATH is empty; there is no reason for such RPATHs
* and they cause unneeded work while loading libraries
* 0x0020 ... an RPATH references '..' of an absolute path; this will break
* the functionality when the path before '..' is a symlink
*
*
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
* $ QA_RPATHS=$(( 0x0001|0x0010 )) rpmbuild my-package.src.rpm
* - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
* $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
*
*******************************************************************************
ERROR 0001: file '/usr/bin/gsl-histogram' contains a standard rpath
'/usr/lib64' in [/usr/lib64]
ERROR 0001: file '/usr/bin/gsl-randist' contains a standard rpath
'/usr/lib64' in [/usr/lib64]
error: Bad exit status from /var/tmp/rpm-tmp.rVEtxu (%install)
> Sent: Saturday, June 19, 2021 at 11:35 PM
> From: "Patrick Dupre" <pdu...@gmx.com>
> To: users@lists.fedoraproject.org
> Cc: users@lists.fedoraproject.org
> Subject: Re: fedpkg
>
> This what I have done.
>
> extrated the gsl.spec from gsl-2.7.tgz
> edited it to set the version (2.7)
> run rpmbuild -bb gsl.spec
> It started to work, but finally stop with
> * Examples:
> * - to ignore standard and empty RPATHs, execute 'rpmbuild' like
> * $ QA_RPATHS=$(( 0x0001|0x0010 )) rpmbuild my-package.src.rpm
> * - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
> * $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
> *
> *******************************************************************************
> ERROR 0001: file '/usr/bin/gsl-histogram' contains a standard rpath
> '/usr/lib64' in [/usr/lib64]
> ERROR 0001: file '/usr/bin/gsl-randist' contains a standard rpath
> '/usr/lib64' in [/usr/lib64]
> error: Bad exit status from /var/tmp/rpm-tmp.rVEtxu (%install)
>
>
> RPM build errors:
> Bad exit status from /var/tmp/rpm-tmp.rVEtxu (%install)
>
>
> > >
> > > https://www.gnu.org/software/gsl/gsl-latest.tgz (gsl-2.7)
> > >
> > >
> > >> I thought that fedpkg works with a clone of the git repo for a fedora
> > >> package.
> > >> Is that what you are doing?
> >
> > That isn't going to work. You need the extra files from the repo to use
> > fedpkg. A possibly easier method would be to get the current source
> > file (dnf download --source gsl), install it as your user, edit things
> > as necessary and use rpmbuild to create a new rpm.
> > _______________________________________________
> > users mailing list -- users@lists.fedoraproject.org
> > To unsubscribe send an email to users-le...@lists.fedoraproject.org
> > 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/users@lists.fedoraproject.org
> > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
> >
> _______________________________________________
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> 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/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
