Bug 1900134

Summary: Please release and build fedpkg for epel-playground changes
Product: [Fedora] Fedora Reporter: Michel Lind <michel>
Component: fedpkgAssignee: Ondřej Nosek <onosek>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: urgent    
Version: rawhideCC: cqi, dennis, jkeating, lsedlar, mattias.ellert, onosek, s
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: fedpkg-1.40-1.fc33 fedpkg-1.40-1.fc32 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-07 01:20:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michel Lind 2020-11-20 22:14:07 UTC
Description of problem:
The latest release of fedpkg was made before the EPEL SC made changes to its epel-playground policy -- namely that requesting an epel8 branch no longer automatically requests an epel8-playground branch, and there is no package.cfg by default (that is used to trigger automatic epel8-playground builds).

These changes have been committed to fedpkg master, so it would be great to have a release. Right now the server-side changes mean new epel8 branch requests no longer creates a branch with package.cfg, but an epel8-playground branch is still created (unless the requester cancels the request in time). There's also a warning triggered when package.cfg is missing on any build operations.

Version-Release number of selected component (if applicable):
fedpkg-1.39-1.fc34

Comment 1 Michel Lind 2020-12-04 22:04:49 UTC
Looks like fedpkg 1.40 is built today, thanks! Could you link this bug to the update?

eg https://bodhi.fedoraproject.org/updates/FEDORA-2020-3c9702ca4d

Comment 2 Fedora Update System 2020-12-04 22:09:28 UTC
FEDORA-2020-3c9702ca4d has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3c9702ca4d

Comment 3 Fedora Update System 2020-12-04 23:36:15 UTC
FEDORA-2020-36f82ae84e has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-36f82ae84e

Comment 4 Fedora Update System 2020-12-05 01:59:54 UTC
FEDORA-2020-3c9702ca4d has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3c9702ca4d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3c9702ca4d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2020-12-05 02:08:27 UTC
FEDORA-2020-36f82ae84e has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-36f82ae84e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-36f82ae84e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2020-12-07 01:20:04 UTC
FEDORA-2020-3c9702ca4d has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2020-12-13 02:35:26 UTC
FEDORA-2020-36f82ae84e has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.