Bug 1949767

Summary: seamonkey- is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: seamonkeyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: caillon+fedoraproject, dmitry, gecko-bugs-nobody, kai-engert-fedora
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-15 18:53:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Upstream Release Monitoring 2021-04-15 04:24:56 UTC
Latest upstream release:
Current version/release in rawhide: 2.53.7-3.fc35
URL: http://www.seamonkey-project.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://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/4788/

Comment 1 Upstream Release Monitoring 2021-04-15 04:25:06 UTC
An HTTP error occurred downloading the package's new Source URLs: Getting http://archive.mozilla.org/pub/seamonkey/releases/ to ./seamonkey-

Comment 2 Dmitry Butskoy 2021-04-15 18:53:28 UTC
All the changes from this minor release are already applied to 2.53.7-3 .

*** This bug has been marked as a duplicate of bug 1944532 ***