https://bugzilla.redhat.com/show_bug.cgi?id=1558683
--- Comment #15 from Alfredo Moralejo amoralej@redhat.com --- (In reply to Sandhya Dasu from comment #14)
A change to run UTs without dependency on the presence of an actual UCS domain has just been merged.
What are the proposed next steps?
- We build an RPM with the latest release + the commit id of the UT fix?
- Proceed with the current RPM and then update the RPM when a new ucsmsdk
release with this fix is release?
The best option would be go get a new release as soon as possible and build it. If it's not possible, we can build latest release without tests and add them when a new tag is created.
I have a related question. Is the .spec file being used to generate your own RPM or is the RPM already build by us being used to add to Fedora?
I'm not sure i understand the question, but the process to add a package to fedora is to get a new repository for the spec files in https://src.fedoraproject.org/ (once this package review is approved), then upload the spec file using "fedpkg push" and build it in https://koji.fedoraproject.org using fedpkg build command. The process is described in :
https://fedoraproject.org/wiki/New_package_process_for_existing_contributors
Let me know if this is clear or you need further help.
Thanks, Sandhya
package-review@lists.fedoraproject.org