Bug 817348

Summary: isync-1.0.5 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: isyncAssignee: Fabian Affolter <mail>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: mail
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: irclog2html-2.10.0-1.fc16 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-13 01:53:08 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:

Description Upstream Release Monitoring 2012-04-29 10:25:55 UTC
Latest upstream release: 1.0.5
Current version in Fedora Rawhide: 1.0.4
URL: http://sourceforge.net/api/file/index/project-name/isync/mtime/desc/limit/20/rss

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 Fedora Update System 2012-04-29 18:50:00 UTC
isync-1.0.5-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/isync-1.0.5-1.fc16

Comment 2 Fedora Update System 2012-04-29 18:50:08 UTC
isync-1.0.5-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/isync-1.0.5-1.fc15

Comment 3 Fedora Update System 2012-04-29 18:50:18 UTC
isync-1.0.5-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/isync-1.0.5-1.fc17

Comment 4 Fedora Update System 2012-04-30 18:49:14 UTC
Package isync-1.0.5-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing isync-1.0.5-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-6972/isync-1.0.5-1.fc17
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2012-04-30 19:06:10 UTC
irclog2html-2.10.0-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/irclog2html-2.10.0-1.fc17

Comment 6 Fedora Update System 2012-04-30 19:06:19 UTC
irclog2html-2.10.0-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/irclog2html-2.10.0-1.fc16

Comment 7 Fedora Update System 2012-04-30 19:06:27 UTC
irclog2html-2.10.0-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/irclog2html-2.10.0-1.fc15

Comment 8 Fedora Update System 2012-05-13 01:53:08 UTC
irclog2html-2.10.0-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2012-05-13 01:53:17 UTC
isync-1.0.5-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-05-13 01:56:38 UTC
isync-1.0.5-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2012-05-13 01:57:13 UTC
irclog2html-2.10.0-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 12 Fedora Update System 2012-05-26 06:55:48 UTC
irclog2html-2.10.0-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2012-05-26 07:00:49 UTC
isync-1.0.5-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.