The 'blender' package blender-4.0.2-1.fc39.x86_64 was installed and the man page was attempted to be read: $ man blender Manual page blender(1) byte 0/0 (END) (press h for help or q to quit) but the man page was empty. The package was checked and it was apparent the package man page is empty: $ rpm -qlv blender | grep /man/ -rw-r--r-- 1 root root 20 Dec 9 19:00 /usr/share/man/man1/blender.1.gz The -qlv shows the man page is 20 bytes which is the size of an 0 byte file that's been gzipped. Directly checking by ungzipping to stdout also showed it's empty: $ gzip -dc /usr/share/man/man1/blender.1.gz | wc -c 0 Reproducible: Always Steps to Reproduce: 1. Install blender rpm package for 4.0.2-1.fc39 2. run "man blender" Actual Results: Man page for blender has no contents Expected Results: Packages should not include empty man pages or 'blender' man page should have the usual type of content expected in man pages like instructions on usage and so on. Either do not include the blender.1.gz file at all if there's no such manual file or include related Blender content in the file.
Looking at the build result, it appears the built traced back without failing ''' Traceback (most recent call last): File "/builddir/build/BUILD/blender-4.0.2/doc/manpage/blender.1.py", line 227, in <module> main() File "/builddir/build/BUILD/blender-4.0.2/doc/manpage/blender.1.py", line 221, in main man_page_from_blender_help(fh, blender_bin, verbose) File "/builddir/build/BUILD/blender-4.0.2/doc/manpage/blender.1.py", line 103, in man_page_from_blender_help blender_info = blender_extract_info(blender_bin) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/builddir/build/BUILD/blender-4.0.2/doc/manpage/blender.1.py", line 45, in blender_extract_info blender_help = subprocess.run( ^^^^^^^^^^^^^^^ File "/usr/lib64/python3.12/subprocess.py", line 548, in run with Popen(*popenargs, **kwargs) as process: ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.12/subprocess.py", line 1026, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib64/python3.12/subprocess.py", line 1950, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/blender' '''
FEDORA-2024-9b34e45efc (blender-4.1.1-3.fc41, luxcorerender-2.7-0.18.beta1.fc41, and 5 more) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-9b34e45efc
FEDORA-2024-9b34e45efc (blender-4.1.1-3.fc41, luxcorerender-2.7-0.18.beta1.fc41, and 5 more) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-bd77f9e670 (blender-4.0.2-3.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-bd77f9e670
FEDORA-2024-bd77f9e670 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-bd77f9e670` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-bd77f9e670 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-bd77f9e670 (blender-4.0.2-3.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.