Bug 2151088

Summary: jacktrip-1.6.8 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: jacktripAssignee: Iñaki Ucar <i.ucar86>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: i.ucar86
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: jacktrip-1.6.8-1.fc37 jacktrip-1.6.8-1.fc36 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-15 01:42:25 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 1.6.8 (#2151088) none

Description Upstream Release Monitoring 2022-12-06 06:07:46 UTC 
Releases retrieved: 1.6.8
Upstream release that is considered latest: 1.6.8
Current version/release in rawhide: 1.6.7-1.fc38
URL: https://github.com/jacktrip/jacktrip

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/jacktrip
Comment 1 Upstream Release Monitoring 2022-12-06 06:07:53 UTC 
Created attachment 1930326 [details]
Update to 1.6.8 (#2151088)
Comment 2 Upstream Release Monitoring 2022-12-06 06:15:01 UTC 
the-new-hotness/release-monitoring.org's scratch build of jacktrip-1.6.8-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=94998515
Comment 3 Fedora Update System 2022-12-06 13:13:55 UTC 
FEDORA-2022-1668460842 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1668460842
Comment 4 Fedora Update System 2022-12-06 13:14:06 UTC 
FEDORA-2022-db88c30495 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-db88c30495
Comment 5 Fedora Update System 2022-12-07 02:50:19 UTC 
FEDORA-2022-1668460842 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-2022-1668460842`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1668460842

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2022-12-07 03:03:46 UTC 
FEDORA-2022-db88c30495 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-2022-db88c30495`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-db88c30495

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2022-12-15 01:42:25 UTC 
FEDORA-2022-1668460842 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 2022-12-15 02:16:45 UTC 
FEDORA-2022-db88c30495 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.