Bug 2160594

Summary: tcpdump-4.99.3 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: tcpdumpAssignee: Michal Ruprich <mruprich>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: luhliari, mruprich, msekleta
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tcpdump-4.99.3-1.fc37 tcpdump-4.99.3-1.fc36 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-25 01:46:34 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 4.99.3 (#2160594) none

Description Upstream Release Monitoring 2023-01-13 00:24:32 UTC 
Releases retrieved: 4.99.3
Upstream release that is considered latest: 4.99.3
Current version/release in rawhide: 4.99.2-1.fc38
URL: https://www.tcpdump.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/4947/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/tcpdump
Comment 1 Upstream Release Monitoring 2023-01-13 00:24:39 UTC 
Created attachment 1937702 [details]
Update to 4.99.3 (#2160594)
Comment 2 Upstream Release Monitoring 2023-01-13 00:31:59 UTC 
the-new-hotness/release-monitoring.org's scratch build of tcpdump-4.99.3-1.fc36.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=96071809
Comment 3 Fedora Update System 2023-01-19 06:29:30 UTC 
FEDORA-2023-39bd46b7a3 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-39bd46b7a3
Comment 4 Fedora Update System 2023-01-19 13:23:20 UTC 
FEDORA-2023-55777f90ec has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-55777f90ec
Comment 5 Fedora Update System 2023-01-21 03:31:04 UTC 
FEDORA-2023-39bd46b7a3 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-39bd46b7a3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-39bd46b7a3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2023-01-21 16:28:33 UTC 
FEDORA-2023-55777f90ec 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-55777f90ec`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-55777f90ec

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2023-01-25 01:46:34 UTC 
FEDORA-2023-39bd46b7a3 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-05 01:52:50 UTC 
FEDORA-2023-55777f90ec has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.