#9642 Cannot submit F34 build to test repo... build does not exist...
Closed: Invalid 3 years ago by gbcox. Opened 3 years ago by gbcox.

It appears the build completed successfully, but when I try to "fedpkg update" to get this submitted to the f34 repo, receive the message build does not exist...

Output of commands below. Thanks!

fedpkg build
Building yubikey-manager-4.0.0a1-2.gitd3802d4.fc34 for f34-candidate
Created task: 61722068
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=61722068
Watching tasks (this may be safely interrupted)...
61722068 build (f34-candidate, /rpms/yubikey-manager.git:7d9c9fdfd45a0231b664ad6d19344d4e0aec3e1a): free
61722068 build (f34-candidate, /rpms/yubikey-manager.git:7d9c9fdfd45a0231b664ad6d19344d4e0aec3e1a): free -> open (buildvm-ppc64le-31.iad2.fedoraproject.org)
61722069 buildSRPMFromSCM (/rpms/yubikey-manager.git:7d9c9fdfd45a0231b664ad6d19344d4e0aec3e1a): open (buildvm-ppc64le-31.iad2.fedoraproject.org)
61722076 buildArch (yubikey-manager-4.0.0a1-2.20210210gitd3802d4.fc34.src.rpm, noarch): open (buildvm-ppc64le-36.iad2.fedoraproject.org)
61722069 buildSRPMFromSCM (/rpms/yubikey-manager.git:7d9c9fdfd45a0231b664ad6d19344d4e0aec3e1a): open (buildvm-ppc64le-31.iad2.fedoraproject.org) -> closed
0 free 2 open 1 done 0 failed
61722068 build (f34-candidate, /rpms/yubikey-manager.git:7d9c9fdfd45a0231b664ad6d19344d4e0aec3e1a): open (buildvm-ppc64le-31.iad2.fedoraproject.org) -> closed
0 free 1 open 2 done 0 failed
61722077 tagBuild (noarch): closed
61722076 buildArch (yubikey-manager-4.0.0a1-2.20210210gitd3802d4.fc34.src.rpm, noarch): open (buildvm-ppc64le-36.iad2.fedoraproject.org) -> closed
0 free 0 open 4 done 0 failed

61722068 build (f34-candidate, /rpms/yubikey-manager.git:7d9c9fdfd45a0231b664ad6d19344d4e0aec3e1a) completed successfully
[gbcox@charon yubikey-manager]$ fedpkg update
Could not execute update: Could not generate update request: Build does not exist: yubikey-manager-4.0.0a1-2.gitd3802d4.fc34
You may not specify an empty list of builds.
ACL validation mechanism was unable to determine ACLs.


Metadata Update from @gbcox:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata