Bug 1672622 - dovecot-2.3.6 is available
Summary: dovecot-2.3.6 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: dovecot
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Hlavinka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1696156
TreeView+ depends on / blocked
 
Reported: 2019-02-05 13:01 UTC by Upstream Release Monitoring
Modified: 2019-06-03 07:50 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-03 07:50:20 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2019-02-05 13:01:38 UTC
Latest upstream release: 2.3.4.1
Current version/release in rawhide: 2.3.4-2.fc30
URL: http://www.dovecot.org/download.html

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.

Based on the information from anitya:  https://release-monitoring.org/project/456/

Comment 1 Upstream Release Monitoring 2019-03-05 19:24:55 UTC
Latest upstream release: 2.3.5
Current version/release in rawhide: 2.3.4-2.fc30
URL: http://www.dovecot.org/download.html

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.

Based on the information from anitya:  https://release-monitoring.org/project/456/

Comment 2 Upstream Release Monitoring 2019-03-28 13:02:55 UTC
Latest upstream release: 2.3.5.1
Current version/release in rawhide: 2.3.4-2.fc30
URL: http://www.dovecot.org/download.html

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.

Based on the information from anitya:  https://release-monitoring.org/project/456/

Comment 3 Upstream Release Monitoring 2019-04-18 09:38:39 UTC
Latest upstream release: 2.3.5.2
Current version/release in rawhide: 2.3.4-2.fc30
URL: http://www.dovecot.org/download.html

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.

Based on the information from anitya:  https://release-monitoring.org/project/456/

Comment 4 Bojan Smojver 2019-04-19 23:42:27 UTC
Michal, do you know why F30 builds are failing? I see some test are segfaulting, but not quite sure what the root cause is. I was attempting to upgrade my mail server from F29 to F30 today and noticed dovecot would get downgraded.

Comment 5 Michal Hlavinka 2019-04-29 15:39:58 UTC
it seems it's related to GCC 9 https://dovecot.org/pipermail/dovecot/2019-January/114494.html upstream is already aware of this, so I expect a fixed release will be available soon

Comment 6 Upstream Release Monitoring 2019-04-30 15:03:25 UTC
Latest upstream release: 2.3.6
Current version/release in rawhide: 2.3.4-2.fc30
URL: http://www.dovecot.org/download.html

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.

Based on the information from anitya:  https://release-monitoring.org/project/456/

Comment 7 Bojan Smojver 2019-05-11 21:21:28 UTC
If I am reading the changelog correctly, a couple of CVEs got fixed in 2.3.6. Most people probably won't reach for F29 builds on F30, so it would be great if you could produce something usable for F30.

Comment 8 Bojan Smojver 2019-05-24 12:31:30 UTC
So, what's the solution here? Build with an older compiler?

Right now, it seems F30 has a package with known vulnerabilities and no way to build a patched version. Can we have this addressed in some way?

Comment 9 Bojan Smojver 2019-06-02 22:58:38 UTC
Thanks for building the packages. Much appreciated.


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