Bug 836599 - gprolog-1.4.3 is available
Summary: gprolog-1.4.3 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gprolog
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jochen Schmitt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-29 15:35 UTC by Upstream Release Monitoring
Modified: 2013-04-01 10:29 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-01 10:29:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2012-06-29 15:35:33 UTC
Latest upstream release: 1.4.1
Current version in Fedora Rawhide: 1.4.0
URL: http://ftp.gnu.org/gnu/gprolog/

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 2012-11-30 10:19:31 UTC
Latest upstream release: 1.4.2
Current version in Fedora Rawhide: 1.4.1
URL: http://ftp.gnu.org/gnu/gprolog/

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 2013-03-30 11:42:39 UTC
Latest upstream release: 1.4.3
Current version in Fedora Rawhide: 1.4.2
URL: http://ftp.gnu.org/gnu/gprolog/

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


Note You need to log in before you can comment on or make changes to this bug.