Description of the issue (screenshots if relevant):
New user here, coming from ROSA Linux and old member of MIB group from Italy. For ROSA in the last few years I acted as maintainer of the packages in the Sound group, working with the ROSA’s ABF, and now I would like to do something for OMV…
So, to see if all is working on my setup, I started preparing a package for a program not yet included in OMV (dmidiplayer, a rewrite for Qt5/6 of the venerable kmid2 program) and managed to build and locally install the resulting rpm.
Now I would like to try to create and build the package with the OMV’s ABF, but I did not manage to do it successfully: in the browser, after filling the form for a new package (abf.openmandriva.org/projects/new) from the ABF starting page
How may I solve this issue and start building stuff on OMV’s ABF?
Relevant informations (hardware involved, software version, logs or output…):
Account nickname: gvm (enabled a couple of weeks ago by Rugyada).
Browser used: firefox 136.0.4 (firefox-136.0.4-1.znver1) with NoScript 12.1.1 (the whole domain openmandriva.org is marked as “trusted” so NoScript should not be the culprit).
Nope.
Using Chromium with the same data as in Firefox and clicking “Save” only makes the page hanging forever with the button saying “working…”.
The culprit seems to be the optional srpm loading: if I don’t specify a srpm, the project is actually created both on firefox and chromium… but is obviously empty.
Has someone any clue about what is going wrong when telling ABF to load a srpm?
Next I will have to figure how to populate the new project with the files from the srpm…
While you are technically correct, the correct logical path would be to supply the source and spec files to have ABF generate the srpm because the contents of a srpm from another distro may lead to a non-working build.
You plug it into a GitHub repo and modify it from there. If you are not in our Cooker chat, you may want to join that. You will also want to test any packages on a Cooker install, be it a chroot, VM, or physical install.
Sorry I was not clearer about this…
The srpm I was trying to use was not the original one from ROSA: I made it (and then built it) locally on a Rome install; the relevant specfile was changed to work with the dependencies provided by OMV and to pass the rpmlint tests.
So what you fear should not happen… I would like to try with ABF exactly to verify this.
Please make sure you are building in Cooker. Our process is to test in Cooker before a UM to ROME. Otherwise, you may have issues building in Cooker that could be avoided.
I think a better use of everyone’s time would be to make a request in the Cooker chat to have the srpm upload feature removed. What you are attempting to try is already mitigated by the thing you called a “bug” and I would agree that is not a graceful way to handle it.
