Description of problem: fedpkg build fails with "packag e msgpack not in list for tag epel8-playground-pending" I have no idea about this error. How reproducible: Steps to Reproduce: 1. fedpkg clone msgpack 2. fedpkg switch-branch epel8 3. fedpkg build Actual results: $ fedpkg build Building msgpack-3.1.0-3.el8 for epel8-candidate Created task: 39091525 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=39091525 Building msgpack-3.1.0-3.el8 for epel8-playground-candidate Created task: 39091527 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=39091527 Watching tasks (this may be safely interrupted)... 39091525 build (epel8-candidate, /rpms/msgpack.git:aec8d8bb2318e6180c2dc5c1d4bc0ff3bdb28f3b): open (buildvm-13.phx2.fedoraproject.org) 39091526 buildSRPMFromSCM (/rpms/msgpack.git:aec8d8bb2318e6180c2dc5c1d4bc0ff3bdb28f3b): free 39091527 build (epel8-playground-candidate, /rpms/msgpack.git:aec8d8bb2318e6180c2dc5c1d4bc0ff3bdb28f3b): free 39091527 build (epel8-playground-candidate, /rpms/msgpack.git:aec8d8bb2318e6180c2dc5c1d4bc0ff3bdb28f3b): free -> FAILED: BuildError: packag e msgpack not in list for tag epel8-playground-pending 1 free 1 open 0 done 1 failed 39091528 buildSRPMFromSCM (/rpms/msgpack.git:aec8d8bb2318e6180c2dc5c1d4bc0ff3bdb28f3b): closed 39091526 buildSRPMFromSCM (/rpms/msgpack.git:aec8d8bb2318e6180c2dc5c1d4bc0ff3bdb28f3b): free -> closed 0 free 1 open 2 done 1 failed 39091525 build (epel8-candidate, /rpms/msgpack.git:aec8d8bb2318e6180c2dc5c1d4bc0ff3bdb28f3b): open (buildvm-13.phx2.fedoraproject.org) -> F AILED: BuildError: package msgpack not in list for tag epel8-testing-candidate 0 free 0 open 2 done 2 failed 39091525 build (epel8-candidate, /rpms/msgpack.git:aec8d8bb2318e6180c2dc5c1d4bc0ff3bdb28f3b) failed 39091527 build (epel8-playground-candidate, /rpms/msgpack.git:aec8d8bb2318e6180c2dc5c1d4bc0ff3bdb28f3b) failed Expected results: fedpkg build succeeds. Additional info:
Why is this RFE? Could you please talk to the relevant people in #fedora-admin on IRC?
OK. Could you close this bug? It seems that I can't close.