Spec URL: https://download.copr.fedorainfracloud.org/results/mhayden/oci/fedora-rawhide-x86_64/05856594-oci-cli/oci-cli.spec SRPM URL: https://download.copr.fedorainfracloud.org/results/mhayden/oci/fedora-rawhide-x86_64/05856594-oci-cli/oci-cli-3.25.4-1.fc39.src.rpm Description: This is the command line interface for Oracle Cloud Infrastructure. Fedora Account System Username: mhayden
Spec file: https://download.copr.fedorainfracloud.org/results/mhayden/oci/fedora-rawhide-x86_64/05870264-oci-cli/oci-cli.spec SRPM file: https://download.copr.fedorainfracloud.org/results/mhayden/oci/fedora-rawhide-x86_64/05870264-oci-cli/oci-cli-3.26.0-1.fc39.src.rpm Updating to latest version and removing forge macros
Created attachment 1961989 [details] The .spec file difference from Copr build 5856601 to 5870468
Copr build: https://copr.fedorainfracloud.org/coprs/build/5870468 (failed) Build log: https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2190315-oci-cli/fedora-rawhide-x86_64/05870468-oci-cli/builder-live.log.gz Please make sure the package builds successfully at least for Fedora Rawhide. - If the build failed for unrelated reasons (e.g. temporary network unavailability), please ignore it. - If the build failed because of missing BuildRequires, please make sure they are listed in the "Depends On" field --- This comment was created by the fedora-review-service https://github.com/FrostyX/fedora-review-service If you want to trigger a new Copr build, add a comment containing new Spec and SRPM URLs or [fedora-review-service-build] string.
Hmm, the "Depends On" is set in this ticket and the COPR builds worked fine. 🤔 https://copr.fedorainfracloud.org/coprs/mhayden/oci/builds/
(In reply to Major Hayden 🤠 from comment #4) > Hmm, the "Depends On" is set in this ticket and the COPR builds worked fine. > 🤔 https://copr.fedorainfracloud.org/coprs/mhayden/oci/builds/ Looking at your deps, it seems we have a common interest! I have been meaning to open reviews for circuitbreaker and the oci-sdk in order to produce oci-utils. Perhaps we can collaborate? I'd be happy to take this review.
That works for me, Neil!
Upstream is now on 3.27.0: Spec URL: https://download.copr.fedorainfracloud.org/results/mhayden/oci/fedora-rawhide-x86_64/05908069-oci-cli/oci-cli.spec SRPM URL: https://download.copr.fedorainfracloud.org/results/mhayden/oci/fedora-rawhide-x86_64/05908069-oci-cli/oci-cli-3.27.0-1.fc39.src.rpm
Created attachment 1963797 [details] The .spec file difference from Copr build 5870468 to 5908085
Copr build: https://copr.fedorainfracloud.org/coprs/build/5908085 (failed) Build log: https://download.copr.fedorainfracloud.org/results/@fedora-review/fedora-review-2190315-oci-cli/fedora-rawhide-x86_64/05908085-oci-cli/builder-live.log.gz Please make sure the package builds successfully at least for Fedora Rawhide. - If the build failed for unrelated reasons (e.g. temporary network unavailability), please ignore it. - If the build failed because of missing BuildRequires, please make sure they are listed in the "Depends On" field --- This comment was created by the fedora-review-service https://github.com/FrostyX/fedora-review-service If you want to trigger a new Copr build, add a comment containing new Spec and SRPM URLs or [fedora-review-service-build] string.
Package review notes: * Package is named appropriately * Package follows Python packaging guidelines * Package builds and installs * Package licensing is mostly correct, the third-party licensing documents don't apply for this package build and need to be dropped. Note: Your Source0 format is wrong. Please follow the convention here before importing: https://docs.fedoraproject.org/en-US/packaging-guidelines/SourceURL/#_git_tags PACKAGE APPROVED.
The Pagure repository was created at https://src.fedoraproject.org/rpms/oci-cli
FEDORA-2023-b65fcbcd6d has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b65fcbcd6d
FEDORA-2023-b65fcbcd6d has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.