Description of problem: When I manually rebuild the package it fails due to missing command (latexmk). Version-Release number of selected component (if applicable): bind-9.16.15-1.fc34.src.rpm How reproducible: Just use rpmbuild command Steps to Reproduce: 1. Use dnf builddep dnf builddep bind-9.16.15-1.fc34.src.rpm Last metadata expiration check: 2:55:38 ago on Sat May 1 08:15:18 2021. Package autoconf-2.69-36.fc34.noarch is already installed. Package doxygen-1:1.9.1-9.fc34.x86_64 is already installed. Package findutils-1:4.8.0-2.fc34.x86_64 is already installed. Package fstrm-devel-0.6.0-4.fc34.x86_64 is already installed. Package gcc-11.1.1-1.fc34.x86_64 is already installed. Package gnupg2-2.2.27-4.fc34.x86_64 is already installed. Package json-c-devel-0.14-8.fc34.x86_64 is already installed. Package krb5-devel-1.19.1-3.fc34.x86_64 is already installed. Package libcap-devel-2.48-2.fc34.x86_64 is already installed. Package libidn2-devel-2.3.0-5.fc34.x86_64 is already installed. Package libmaxminddb-devel-1.5.2-1.fc34.x86_64 is already installed. Package libpq-devel-13.2-1.fc34.x86_64 is already installed. Package libtool-2.4.6-40.fc34.x86_64 is already installed. Package libuv-devel-1:1.41.0-1.fc34.x86_64 is already installed. Package libxml2-devel-2.9.10-10.fc34.x86_64 is already installed. Package lmdb-devel-0.9.29-1.fc34.x86_64 is already installed. Package make-1:4.3-5.fc34.x86_64 is already installed. Package mariadb-connector-c-devel-3.1.12-1.fc34.x86_64 is already installed. Package openldap-devel-2.4.57-2.fc34.x86_64 is already installed. Package openssl-devel-1:1.1.1k-1.fc34.x86_64 is already installed. Package pkgconf-pkg-config-1.7.3-6.fc34.x86_64 is already installed. Package protobuf-c-devel-1.3.3-7.fc34.x86_64 is already installed. Package python3-devel-3.9.4-1.fc34.x86_64 is already installed. Package python3-ply-3.11-11.fc34.noarch is already installed. Package python3-sphinx-1:3.4.3-2.fc34.noarch is already installed. Package python3-sphinx_rtd_theme-0.5.1-2.fc34.noarch is already installed. Package sed-4.8-7.fc34.x86_64 is already installed. Package selinux-policy-34.3-1.fc34.noarch is already installed. Package sqlite-devel-3.34.1-2.fc34.x86_64 is already installed. Package systemd-248-2.fc34.x86_64 is already installed. Dependencies resolved. Nothing to do. Complete! 2. Rebuild the package rpmbuild --rebuild bind-9.16.15-1.fc34.src.rpm Actual results: Build fails The LaTeX files are in _build/latex. Run 'make' in that directory to run these through (pdf)latex (use `make latexpdf' here to do that automatically). make -C "./_build"/latex make[3]: Entering directory '/home/pawel/rpmbuild/BUILD/bind-9.16.15/build/doc/arm/_build/latex' latexmk -pdf -dvi- -ps- 'Bv9ARM.tex' make[3]: latexmk: No such file or directory make[3]: *** [Makefile:29: Bv9ARM.pdf] Error 127 make[3]: Leaving directory '/home/pawel/rpmbuild/BUILD/bind-9.16.15/build/doc/arm/_build/latex' make[2]: *** [Makefile:447: pdf] Error 2 make[2]: Leaving directory '/home/pawel/rpmbuild/BUILD/bind-9.16.15/build/doc/arm' make[1]: *** [Makefile:105: doc] Error 1 make[1]: Leaving directory '/home/pawel/rpmbuild/BUILD/bind-9.16.15/build/doc' make: *** [Makefile:110: doc] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.d4zP20 (%build) Expected results: Build ends successfully Additional info: If I install missing dependencies (python3-sphinx-latex latexmk texlive-xetex texlive-xindy) build still fails but for other reasons Latexmk: calling xindy( -L english -C utf8 -M sphinx.xdy -o "Bv9ARM.ind" "Bv9ARM.idx" ) /usr/lib64/clisp-2.49.93+/base/lisp.run: initialization file `/usr/bin/xindy.mem' was not created by this version of CLISP runtime Latexmk: Errors, so I did not complete making targets Collected error summary (may duplicate other messages): makeindex Bv9ARM.idx: Command for 'makeindex Bv9ARM.idx' gave return code 256 Refer to 'Bv9ARM.ilg' for details ----------- clisp-2.49.93-18.d9cbf22git.fc34.x86_64
Have you done before build command: dnf builddep bind ? If only documentation building is a problem, it should work fine without rebuilding it: rpmbuild --without DOCPDF --rebuild bind-9.16.15-1.fc34.src.rpm
(In reply to Petr Menšík from comment #1) > Have you done before build command: dnf builddep bind ? Yes, see the first comments > If only documentation building is a problem, it should work fine without > rebuilding it: > > rpmbuild --without DOCPDF --rebuild bind-9.16.15-1.fc34.src.rpm It should work but it doesn't. I can use --without DOC but it's not the same.
Is your problem still valid with more recent versions? Because production builds work just well, I think it should work just well. Have you tried fedpkg for building? Would it change? fedpkg clone --anonymous rpms/bind cd bind git checkout f34 dnf builddep bind.spec fedpkg local Would it have the same problem? I use it myself without issues, it just works.
(In reply to Petr Menšík from comment #3) > Is your problem still valid with more recent versions? No, bind-9.16.18-1.fc34 builds without a problem.
I forgot DOCPDF were disabled. Can you please retry including rpmbuild --with DOCPDF, whether it would build?
(In reply to Petr Menšík from comment #5) > I forgot DOCPDF were disabled. Can you please retry including rpmbuild > --with DOCPDF, whether it would build? With the option "--with DOCPDF"" it also builds without a problem.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.