Hello, I maintain the packages for the navigation SW OpenCPN and I use a sandbox in my home for testing new releases and fixing build an integration issues. When my test are completed (users do not like to discover bugs when at sea) I copy the project on the publication repo Application:Geo:OpenCPN with osc copypac. - https://build.opensuse.org/package/show/Application:Geo:OpenCPN/OpenCPN-4.x-... - https://build.opensuse.org/project/show/home:dominig:opencpn-sandbox Knowing that as today both packages are at the same release 4.6.1, I do not understand why the release shown in https://software.opensuse.org for home:dominig:opencpn-sandbox claims to be at release 4.6.1 while the one from Application:Geo:OpenCPN indicates release 4.6.0. This is annoying as it can lead user to take my sandbox version as source and get in trouble when I will integrate the new release. The actual packages are are the same in both repos (4.6.1) https://build.opensuse.org/package/binaries/Application:Geo:OpenCPN/OpenCPN-... The published packages are at the correct release in both repo, only the release indication for 'one click install' is incorrect. Questions: - where does come the version indication in https://software.opensuse.org ? - is there a way to publish packages without getting them listed in https://software.opensuse.org ? I would love such feature to restrict visibility of my sandbox to my beta tester only. I only know the flag publish or nor publish which is too violent for my use case. A flag in project meta to remove publication from https://software.opensuse.org would be very handy. Thanks. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org