Bug 2165119

Summary: gpxsee-12.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: gpxseeAssignee: Nikola Forró <nforro>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: nforro, vascom2
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gpxsee-12.1-2.fc38 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-11 03:09:35 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 11.12 (#2165119)
none
Update to 12.0 (#2165119)
none
Update to 12.1 (#2165119)
none
Update to 12.1 (#2165119) none

Description Upstream Release Monitoring 2023-01-27 18:09:33 UTC
Releases retrieved: 11.12
Upstream release that is considered latest: 11.12
Current version/release in rawhide: 11.11-2.fc38
URL: http://www.gpxsee.org/

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/16205/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/gpxsee

Comment 1 Upstream Release Monitoring 2023-01-27 18:09:40 UTC
Created attachment 1940794 [details]
Update to 11.12 (#2165119)

Comment 2 Upstream Release Monitoring 2023-01-27 18:26:51 UTC
the-new-hotness/release-monitoring.org's scratch build of gpxsee-11.12-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=96781254

Comment 3 Upstream Release Monitoring 2023-02-10 14:18:16 UTC
Releases retrieved: 12.0
Upstream release that is considered latest: 12.0
Current version/release in rawhide: 11.11-2.fc38
URL: http://www.gpxsee.org/

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/16205/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/gpxsee

Comment 4 Upstream Release Monitoring 2023-02-10 14:18:22 UTC
Created attachment 1943342 [details]
Update to 12.0 (#2165119)

Comment 5 Upstream Release Monitoring 2023-02-19 00:01:25 UTC
Releases retrieved: 12.1
Upstream release that is considered latest: 12.1
Current version/release in rawhide: 11.11-2.fc38
URL: http://www.gpxsee.org/

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/16205/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/gpxsee

Comment 6 Upstream Release Monitoring 2023-02-19 00:01:31 UTC
Created attachment 1945005 [details]
Update to 12.1 (#2165119)

Comment 7 Upstream Release Monitoring 2023-02-19 00:11:03 UTC
the-new-hotness/release-monitoring.org's scratch build of gpxsee-12.1-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=97685685

Comment 8 Vasiliy Glazov 2023-02-20 10:02:48 UTC
Please update gpxsee with latest version.

Comment 9 Upstream Release Monitoring 2023-02-21 11:56:58 UTC
Created attachment 1945506 [details]
Update to 12.1 (#2165119)

Comment 10 Upstream Release Monitoring 2023-02-21 12:05:27 UTC
the-new-hotness/release-monitoring.org's scratch build of gpxsee-12.1-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=97806762

Comment 11 Fedora Update System 2023-02-25 12:47:25 UTC
FEDORA-2023-522a9c7505 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-522a9c7505

Comment 12 Fedora Update System 2023-02-26 02:02:07 UTC
FEDORA-2023-522a9c7505 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-522a9c7505

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

Comment 13 Fedora Update System 2023-03-11 03:09:35 UTC
FEDORA-2023-522a9c7505 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.