Bug 1311968 - postfix-3.1.0 is available
Summary: postfix-3.1.0 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: postfix
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-25 12:22 UTC by Upstream Release Monitoring
Modified: 2016-02-25 15:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-25 15:04:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2016-02-25 12:22:27 UTC
Latest upstream release: 3.1.0
Current version/release in rawhide: 3.0.4-1.fc24
URL: ftp://ftp.porcupine.org/mirrors/postfix-release/official/

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

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.

Comment 1 Upstream Release Monitoring 2016-02-25 12:22:59 UTC
Failed to kick off scratch build.

spectool was unable to grab new sources

old source: pflogsumm-1.1.3.tar.gz
old sha256: c4df11c2eaef313025e326114d9dea4b0f0f9b978880a29d2ecf075774aa7142

new source: ./pflogsumm-1.1.3.tar.gz
new sha256: c4df11c2eaef313025e326114d9dea4b0f0f9b978880a29d2ecf075774aa7142

Comment 2 Upstream Release Monitoring 2016-02-25 14:47:26 UTC
jskarvad's postfix-3.1.0-1.fc25 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=738883


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