Yes: you can either edit (ie via nano) the previously indicated file so that the “def rpm_build_info(pkg):” section reads as I posted earlier or you could follow the instructions in How to apply a patch to aid in development using the following patch url:
https://github.com/rockstor/rockstor-core/commit/5aea23d8607294da741a23dabcc905edaeedd7d2.patch
if all goes well then you should receive the following reply from the patch command indicated in those instructions:
patching file src/rockstor/system/pkg_mgmt.py
I have just tested this patch on a 3.9.1-16 install here and all was well, although that install didn’t exhibit your issue in the first place.
In either case it may be necessary to restart the rockstor service there after via:
systemctl restart rockstor
for the changes to take effect, as there is a chance that you system will be ‘holding onto’ the previous version of the file if it was active at the time.
That depends on how happy you are taking the risks indicated in the above wiki post. You will always be able to update via ‘yum update’, assuming that the last testing channel update is delivered that way; which is the plan I believe. But it may be of more use overall to know if this patch works in your setting; just in case others run into the same thing. See how you feel after reading the indicated wiki and take it from there. If it fails you can always restore the backup version of the file the instructions talk you though making.
Hope that helps.