[opensuse-buildservice] Disabled packages coming back
This is another HUGE thing I've been dealing with. I tried to "un-publish" a package that I built, and the changes do not stick. obs01:/obs/repos/common # rm ./CentOS_5/src/netezza-client-7.0.2-1.1.src.rpm ./CentOS_5/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm ./ScientificLinux_6/src/netezza-client-7.0.2-1.1.src.rpm ./ScientificLinux_6/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm obs01:/obs/repos/common # find -name netezza* obs01:/obs/repos/common # find -name netezza* ./CentOS_5/src/netezza-client-7.0.2-1.1.src.rpm ./CentOS_5/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm ./ScientificLinux_6/src/netezza-client-7.0.2-1.1.src.rpm ./ScientificLinux_6/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm obs01:/obs/repos/common # find -name netezza* ./CentOS_5/src/netezza-client-7.0.2-1.1.src.rpm ./CentOS_5/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm ./ScientificLinux_6/src/netezza-client-7.0.2-1.1.src.rpm ./ScientificLinux_6/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm obs01:/obs/repos/common # find -name netezza* ./CentOS_5/src/netezza-client-7.0.2-1.1.src.rpm ./CentOS_5/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm ./ScientificLinux_6/src/netezza-client-7.0.2-1.1.src.rpm ./ScientificLinux_6/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm obs01:/obs/repos/common # rm ./CentOS_5/src/netezza-client-7.0.2-1.1.src.rpm ./CentOS_5/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm ./ScientificLinux_6/src/netezza-client-7.0.2-1.1.src.rpm ./ScientificLinux_6/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm obs01:/obs/repos/common # find -name netezza* obs01:/obs/repos/common # find -name netezza* ./CentOS_5/src/netezza-client-7.0.2-1.1.src.rpm ./CentOS_5/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm ./ScientificLinux_6/src/netezza-client-7.0.2-1.1.src.rpm ./ScientificLinux_6/x86_64/netezza-client-7.0.2-1.1.x86_64.rpm As you can see, it goes away. Then I deleted a package to regenerate the repo. It comes back. Then I tried disabling build completely. Still there. The only way I think I can make this go away is to change the project. Why is this? The build in the Web UI was 1.3, not 1.1. 1.1 is when I tried unpublishing it in the first place. What's the correct way to remove something from the yum repo, but still leave the sources in the system? -Matt N�����r��y隊Z)z{.���Wlz��qﮞ˛���m�)z{.��+�:�{Zr�az�'z��j)h���Ǜ�)]���Ǿ� ޮ�^�ˬz��
Matthew Drobnak <mdrobnak@appnexus.com> writes:
What's the correct way to remove something from the yum repo, but still leave the sources in the system?
osc wipebinaries Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Do I do this osc command then disable publishing in the UI? When I've hit "delete published binaries" before in the UI, it's immediately started a build job. -Matt On Tue, 2013-11-19 at 19:09 +0100, Andreas Schwab wrote:
Matthew Drobnak <mdrobnak@appnexus.com> writes:
What's the correct way to remove something from the yum repo, but still leave the sources in the system?
osc wipebinaries
Andreas.
N�����r��y隊Z)z{.���Wlz��qﮞ˛���m�)z{.��+�:�{Zr�az�'z��j)h���Ǜ�)]���Ǿ� ޮ�^�ˬz��
participants (2)
-
Andreas Schwab
-
Matthew Drobnak