Bug 756370

Summary: seamonkey-2.7 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: seamonkeyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cfeller, gecko-bugs-nobody, hicham.haouari, jrb, kengert, niveusluna
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: seamonkey-2.7-1.fc15 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-15 11:35:40 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 2011-11-23 11:55:02 UTC
Latest upstream release: 2.5
Current version in Fedora Rawhide: 2.4.1
URL: http://www.seamonkey-project.org/releases/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 1 Upstream Release Monitoring 2011-12-21 11:52:24 UTC
Latest upstream release: 2.6
Current version in Fedora Rawhide: 2.5
URL: http://www.seamonkey-project.org/releases/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 2 Upstream Release Monitoring 2011-12-23 11:45:41 UTC
Latest upstream release: 2.6.1
Current version in Fedora Rawhide: 2.5
URL: http://www.seamonkey-project.org/releases/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 3 Russell Golden 2012-01-09 18:44:51 UTC
2.5 is EOL, remember...

Comment 4 Upstream Release Monitoring 2012-02-02 11:59:36 UTC
Latest upstream release: 2.7
Current version in Fedora Rawhide: 2.5
URL: http://www.seamonkey-project.org/releases/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 5 Fedora Update System 2012-02-06 09:52:04 UTC
seamonkey-2.7-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/seamonkey-2.7-1.fc16

Comment 6 Fedora Update System 2012-02-06 09:52:15 UTC
seamonkey-2.7-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/seamonkey-2.7-1.fc15

Comment 7 Fedora Update System 2012-02-07 07:55:31 UTC
Package seamonkey-2.7-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing seamonkey-2.7-1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1401/seamonkey-2.7-1.fc16
then log in and leave karma (feedback).

Comment 8 Hicham HAOUARI 2012-02-09 11:29:41 UTC
*** Bug 783386 has been marked as a duplicate of this bug. ***

Comment 9 Fedora Update System 2012-02-15 11:35:40 UTC
seamonkey-2.7-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2012-02-15 11:37:32 UTC
seamonkey-2.7-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.