Open Build Service (OBS), currently only keeps the latest package it builds in the repository. Is there a server-wide configuration I can set to keep the latest 3 packages?

I am trying to get Open Build Service to accept this PKGBUILD: ~~~ # Maintainer: Ole Tange pkgname=parallel pkgver=20200622 pkgrel=2 pkgdesc='Build and execute shell command lines from standard input in parallel' arch=('any') url='https://www.gnu.org/software/parallel/ ' license=('GPL3') depends=('perl' 'procps') source=(https://ftp.gnu.org/gnu/$pkgname/$pkgname-$pkgver.tar.bz2{,.sig}) sha256sums=('41ce2f31b7850ad86b88dc756faf78a70e4ae92f45fa6603b7d108148ebe6513' 'SKIP') validpgpkeys=('CDA01A4208C4F74506107E7BD1AB451688888888') prepare() { cd parallel-$pkgver } build() { cd parallel-$pkgver ./configure --prefix=/usr make } package() { cd parallel-$pkgver make DESTDIR="$pkgdir/" install } ~~~ But it complains: nothing provides perl, binutils, procps, gcc, ... I imagine I need a line that says: Please provide me with basic build dependencies. You can see it "live" at: https://build.opensuse.org/package/show/home:tange/parallel What do I need to change to make OBS build the package?

I have a RPM that I'm currently building with FPM, fpm --verbose \ -s dir \ -t rpm \ --directories /opt/myprod --name myprod --rpm-summary "My Prod" --version $(git describe --abbrev=0 --tags) --rpm-sign --rpm-digest sha512 ./myprod=/opt/ This essentially creates an rpm **from a directory** that does **exactly** what I want. It works perfectly. But, my company has their own signing key that can not be shared on an [Open Build Service (OBS)](https://openbuildservice.org/) server. I don't *need* to use FPM at all if OBS can do everything. What I do need is some *understanding* of how I go from the directory ./myprod to an RPM which installs it under /opt/myprod. I'm new to RPM packaging. I assume I could take this directory and .tar.gz it and submit it to to OBS to be packaged and signed. I assume I need to somehow specify this with a spec file? What is the most simple way to accomplish this. Ideally, I wouldn't have to manually generate a spec file. Is any of this provided by OBS?