Hello, if I understand well your need is to add an RPM which is not built by OBS in an OBS managed repository. With your method you will need to recreate your repo metadata every time that your OBS trigger a rebuild. I add a similar need in the past ad this is how I proceeded. I had to add packages in an OBS Repos which could not be to be compiled by the OBS (DSP code), my trick has been to add a package in the OBS which has an empty %build macro in the package spec file. In my case. My goal was to provide binary blobs for DSP firmware and the trick was only to have a %install macro which copied the blob in the right place. If you need only a source rpm as said in your mail, you can also have an empty %build macro. Dominig ar Foll MeeGo TV Open Source Technology Centre Intel SSG Le 11/08/2011 09:57, Wu, Yanping a écrit :
I tried to add extra package(rpms) into my OBS project repo(E.g /srv/obs/repos/project/i586), When I run createrepo in OBS server, the repodata will change correctly, and I can use the repo to install this extra package.
But when there is check-in to the project, and it begins to rebuild. The repo will republished. I found OBS automatically delete my extra package in i586 directory. And the repodata doesn’t include it any more. How can I solve this issue?
Hope for your help.
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org