Bug 1903927

Summary: eiskaltdcpp-2.4.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: eiskaltdcppAssignee: Vasiliy Glazov <vascom2>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: vascom2
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: eiskaltdcpp-2.4.0-1.fc33 eiskaltdcpp-2.4.0-1.fc32 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-13 02:09:42 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
[patch] Update to 2.4.0 (#1903927) none

Description Upstream Release Monitoring 2020-12-03 07:00:11 UTC 
Latest upstream release: 2.4.0
Current version/release in rawhide: 2.2.11-30.20200616git2ec27a2.fc33
URL: https://github.com/eiskaltdcpp/eiskaltdcpp

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/15551/
Comment 1 Upstream Release Monitoring 2020-12-03 07:00:14 UTC 
One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.
Comment 2 Upstream Release Monitoring 2020-12-03 07:00:17 UTC 
Created attachment 1735959 [details]
[patch] Update to 2.4.0 (#1903927)
Comment 3 Fedora Update System 2020-12-04 13:48:21 UTC 
FEDORA-2020-ad10de64c4 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-ad10de64c4
Comment 4 Fedora Update System 2020-12-04 13:48:23 UTC 
FEDORA-2020-608f4aef60 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-608f4aef60
Comment 5 Fedora Update System 2020-12-05 01:59:45 UTC 
FEDORA-2020-ad10de64c4 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-ad10de64c4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-ad10de64c4

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

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2020-12-13 02:09:42 UTC 
FEDORA-2020-ad10de64c4 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 8 Fedora Update System 2020-12-13 02:35:20 UTC 
FEDORA-2020-608f4aef60 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.