Bug 2166914

Summary: pioneer-20230203 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: pioneerAssignee: Antonio T. sagitter <trpost>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: trpost
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pioneer-20230203-1.fc37 pioneer-20230203-1.fc36 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-13 00:41:03 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:
Attachments:
Description Flags
Update to 20230203 (#2166914) none

Description Upstream Release Monitoring 2023-02-03 13:43:17 UTC 
Releases retrieved: 20230203
Upstream release that is considered latest: 20230203
Current version/release in rawhide: 20220203-5.fc38
URL: http://pioneerspacesim.net

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://docs.fedoraproject.org/en-US/package-maintainers/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/12293/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/pioneer
Comment 1 Upstream Release Monitoring 2023-02-03 13:45:05 UTC 
Created attachment 1942034 [details]
Update to 20230203 (#2166914)
Comment 2 Upstream Release Monitoring 2023-02-03 14:10:11 UTC 
the-new-hotness/release-monitoring.org's scratch build of pioneer-20230203-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=97048182
Comment 3 Fedora Update System 2023-02-04 17:54:21 UTC 
FEDORA-2023-cf5d644e9f has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-cf5d644e9f
Comment 4 Fedora Update System 2023-02-04 17:54:23 UTC 
FEDORA-2023-33626d0e5d has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-33626d0e5d
Comment 5 Fedora Update System 2023-02-05 02:06:10 UTC 
FEDORA-2023-33626d0e5d has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-33626d0e5d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-33626d0e5d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2023-02-05 02:24:22 UTC 
FEDORA-2023-cf5d644e9f has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-cf5d644e9f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cf5d644e9f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2023-02-13 00:41:03 UTC 
FEDORA-2023-33626d0e5d has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 8 Fedora Update System 2023-02-13 01:23:46 UTC 
FEDORA-2023-cf5d644e9f has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.