As you are probably aware, the Fedora packaging guidelines state that Fortran modules must be installed in %{_fmoddir}, which currently evaluates to %{_libdir}/gfortran/modules. However, the modules are inherently dependent on the version of gfortran used to generate them, and we are currently missing this dependency information. Also, the placement of the modules is not in touch with the gfortran version. I have been previously alerted by the gcc maintainers that %{_libdir}/gfortran/modules is the wrong place to put the modules, they should go to the finclude directory instead. For this reason I am hereby requesting that you add rpm macros to the gfortran package, which change %{_fmoddir} to the correct directory used internally by gfortran itself. (At the same time the definition needs to be removed from /usr/lib/rpm/redhat/macros provided by the redhat-rpm-config package.) Also, it would be nice to solve the dependency question. As long as the dependencies are not automatically picked up by RPM, I ask that you add another RPM macro which gives the module compatibility version of gfortran, e.g. %_gfortran_module_ver 4.8.1%{?_isa} that can be Required by packages shipping fortran modules.
*** Bug 513985 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
See bug #1192617 for rpm part of problem.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Issue still exists on rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.