I have an orphaned build in one of my project repositories (builds present, build ID gone)
How can I clean this up without deleting my whole project?
Thanks, Richard
On 11/02/2014 07:10 PM, Richard Shaw wrote:
I have an orphaned build in one of my project repositories (builds present, build ID gone)
How can I clean this up without deleting my whole project?
Thanks, Richard
This should not happen. Can you please share more details? Name of project, name of package, version.
Mirek
On Mon, Nov 3, 2014 at 4:59 AM, Miroslav Suchy msuchy@redhat.com wrote:
On 11/02/2014 07:10 PM, Richard Shaw wrote:
I have an orphaned build in one of my project repositories (builds present, build ID gone)
How can I clean this up without deleting my whole project?
This should not happen.
Can you please share more details? Name of project, name of package, version.
If you look here:
http://copr-be.cloud.fedoraproject.org/results/hobbes1069/WSJT/fedora-20-x86...
The hamlib3 build is not listed in my builds.It's the same on several of my chroots.
Thanks, Richard
On 11/03/2014 02:46 PM, Richard Shaw wrote:
If you look here:
http://copr-be.cloud.fedoraproject.org/results/hobbes1069/WSJT/fedora-20-x86...
The hamlib3 build is not listed in my builds.It's the same on several of my chroots.
Ok. To answer your original question. No you can not do that (unless you delete whole project). I can delete it manually.
But before I do that, I would really like to find out how this happened. This really puzzle me. I thought that it may happen by creating projects with two chroots, build package, edit chroot to use only one chroot and then delete package. So I tried it, and it correctly delete both packages. Do you have idea what you did, before this issue occurred?
On Tue, Nov 4, 2014 at 4:06 AM, Miroslav Suchý msuchy@redhat.com wrote:
On 11/03/2014 02:46 PM, Richard Shaw wrote:
If you look here:
http://copr-be.cloud.fedoraproject.org/results/ hobbes1069/WSJT/fedora-20-x86_64/
The hamlib3 build is not listed in my builds.It's the same on several of my chroots.
Ok. To answer your original question. No you can not do that (unless you delete whole project). I can delete it manually.
But before I do that, I would really like to find out how this happened. This really puzzle me. I thought that it may happen by creating projects with two chroots, build package, edit chroot to use only one chroot and then delete package. So I tried it, and it correctly delete both packages. Do you have idea what you did, before this issue occurred?
Unfortunately no, I don't remember the exact steps I took at this point. I know those builds are older so perhaps it's something that's been fixed in newer versions of COPR?
Of course it would be best if this never happened but I wonder if the API could be extended to use copr-cli to fix things like this without having to ask for admin help?
Thanks, Richard
copr-devel@lists.fedorahosted.org