Am Dienstag, 3. September 2019, 13:16:06 CEST schrieb Adrian Schröter:
On Dienstag, 3. September 2019, 12:25:51 CEST Hans-Peter Jansen wrote:
but, after waiting for the project to be published, those packages still exist:
sure, publish disable means that now publish operation happens and repo stays untouched.
You look most likely for "osc unpublish" instead.
Thanks Adrian, for the hint. Yes, unpublish does the trick. From the help, I cannot see any distinction between wipebinaries and unpublish, though. It rather looks like an alias: wipebinaries (unpublish): Delete all binary packages of a certain project/package With the optional argument <package> you can specify a certain package otherwise all binary packages in the project will be deleted. usage: osc wipebinaries OPTS # works in checked out project dir osc wipebinaries OPTS PROJECT [PACKAGE] osc unpublish OPTS # works in checked out project dir osc unpublish OPTS PROJECT [PACKAGE] Options: -h, --help show this help message and exit --all Delete all binaries regardless of the package status (previously default) --unresolvable Delete all binaries of packages which have dependency errors --broken Delete all binaries of packages for which the package source is bad --build-failed Delete all binaries of packages for which the build failed --build-disabled Delete all binaries of packages for which the build is disabled -r REPO, --repo=REPO Delete all binary packages for a specific repository -M MULTIBUILD_PACKAGE, --multibuild-package=MULTIBUILD_PACKAGE Delete all binary packages for specified multibuild package -a ARCH, --arch=ARCH Delete all binary packages for a specific architecture Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org