First, thanks for the continued help. Is there any documentation on the maintenance concept? My first instinct was to create a subproject, and stuff the main package + supporting package which required a specific version in there. However, while that does keep a specific version around, it doesn't address the issue of a "roll-back" scenario - that means we'd basically have to re-build the old version we wanted to push out any time we needed to roll-back. Or, as you suggested, copying the package container. Both seem a bit messy. This issue is bigger then this though - one *must* continue forward with revision movements of repos generated by OBS. For instance, for the appliance, I modified the vhost config, but forgot to back up the original. No problem, I'll reinstall the version from the repo. Problem is, the next version was released; the version I have is no longer there. What I have is only repeatable from the actual raw image I have. For something "supported" this seems like a very foreign concept. It's as if OS updates were all being put in the "base" repository. Not even Debian does that. ;) -Matt On 10/22/12 3:02 AM, Adrian Schröter wrote:

Am Samstag, 20. Oktober 2012, 00:27:59 schrieb Matthew Drobnak:

...

I've noticed that when a new version of a package is built, the old one is removed from the repo. Is there a way to keep X old versions (or all) old versions? You either need to copy your package container for that, eg:

osc copypac $project $package $project $package.rev$number

or use something like our maintenance concept for that.

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org