Bug 1879530

Summary: golang-github-marstr-collection-1.1.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: golang-github-marstr-collectionAssignee: Robert-André Mauchin 🐧 <zebob.m>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: go-sig, jchaloup, zebob.m
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: golang-github-marstr-collection-1.1.1-1.fc34 golang-github-marstr-collection-1.1.1-1.fc33 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-21 02:37:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2020-09-16 13:24:00 UTC
Latest upstream release: 1.1.0
Current version/release in rawhide: 1.0.1-6.fc33
URL: https://github.com/marstr/collection

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/18982/

Comment 1 Upstream Release Monitoring 2020-09-16 13:24:04 UTC
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!

Comment 2 Upstream Release Monitoring 2020-09-17 04:18:55 UTC
Latest upstream release: 1.1.1
Current version/release in rawhide: 1.0.1-6.fc33
URL: https://github.com/marstr/collection

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/18982/

Comment 3 Upstream Release Monitoring 2020-09-17 04:18:59 UTC
An unexpected error occurred while creating the scratch build and has been automatically reported. Sorry!

Comment 4 Fedora Update System 2020-12-21 02:37:09 UTC
FEDORA-2020-7ead968ed2 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2020-12-21 02:42:38 UTC
FEDORA-2020-4ed85e8090 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4ed85e8090

Comment 6 Fedora Update System 2020-12-22 02:17:36 UTC
FEDORA-2020-4ed85e8090 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-4ed85e8090`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4ed85e8090

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

Comment 7 Fedora Update System 2020-12-30 01:36:48 UTC
FEDORA-2020-4ed85e8090 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.