The build tags for this don't allow it to be placed in the build root and I cannot set this build into a build override or create an update for it.
When do you need this? (YYYY/MM/DD) 2019/04/15
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact? Wine builds require it. Cannot push an updated wine.
Well, I fixed an issue related to this this morning already, so I thought it was fixed, when did you hit this issue?
Can you problem a build that doesn't see it in the buildroot?
What does it say when you try and add a override or update?
I hit this issue today. Here is what I get from koji (not from mock) when I tried to build a wine update for f30 or f31:
https://koji.fedoraproject.org/koji/taskinfo?taskID=34176476 https://kojipkgs.fedoraproject.org//work/tasks/6669/34176669/root.log: DEBUG util.py:554: BUILDSTDERR: Error: DEBUG util.py:554: BUILDSTDERR: Problem: package autotrace-0.31.1-54.fc30.x86_64 requires libMagickCore-6.Q16.so.6()(64bit), but none of the providers can be installed DEBUG util.py:554: BUILDSTDERR: - package fontforge-20170731-12.fc30.x86_64 requires autotrace, but none of the providers can be installed DEBUG util.py:554: BUILDSTDERR: - package ImageMagick-libs-1:6.9.10.28-1.fc30.x86_64 requires libgs.so.9()(64bit), but none of the providers can be installed DEBUG util.py:554: BUILDSTDERR: - conflicting requests DEBUG util.py:554: BUILDSTDERR: - nothing provides urw-base35-fonts needed by libgs-9.26-4.fc30.x86_64
I fixed f31 by issuing a new build of urw-base35-fonts because there was no f31 build yet and the f30 build is in this bad tag state. I guess I could fix this for f30 too by a release bump and rebuild, but something odd happened here because my last wine build two weeks back was normal. Did someone remove urw-base35-fonts from the f30/f31 tags?
When I try to issue an override I get this from bodhi: "Nvr : Invalid build"
Ah, I see what happened. The old builds were all untagged when it blocked it.
I've tagged the last build back in, so it should be ok in a few minutes... please test.
Thanks. That fixed it.
Metadata Update from @mooninite: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)