obsolete

bind-9.11.5-4.P4.fc28

FEDORA-2019-86412405d5 created by pemensik 4 years ago for Fedora 28

More details are in upstream release notes. Disabled autodetected support of ED448, it does not work.

This update has been submitted for testing by pemensik.

4 years ago

This update has been pushed to testing.

4 years ago
User Icon samoht0 commented & provided feedback 4 years ago
karma

no regressions noted

User Icon adamwill commented & provided feedback 4 years ago

Openqa test failures suggest there may be dependency issues here. I'm on my phone ATM, will look in more detail later.

User Icon adamwill commented & provided feedback 4 years ago
karma

OK, so yes, there is a problem. This build comes with soname bumps. It provides libdns-export.so.1104 , libirs-export.so.161, libisc-export.so.1100 and libisccfg-export.so.163. The current stable build - bind-9.11.4-13.P2.fc28 - provides libdns-export.so.1102, libirs-export.so.160, libisc-export.so.169 and libisccfg-export.so.160. This update breaks the deps of anything built against bind - including dhcp-client - and it should not go out as-is. The soname bumps should be avoided for a stable release update if at all possible, if not possible, all dependent packages must be rebuilt and included in the update.

BZ#1679925 CVE-2018-5744 CVE-2018-5745 CVE-2019-6465 bind: various flaws [fedora-all]

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

4 years ago
User Icon samoht0 commented & provided feedback 4 years ago
karma

Adam, did you notice?

FEDORA-2019-6c4e362bd0

No problems with dhcp here. But yeah, need to be pushed first.

This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes

4 years ago
User Icon adamwill commented & provided feedback 4 years ago

Updates are tested as, and should be, independent units. Any update in updates-testing might be pushed to stable at any time; it should always be in a state where doing so would not cause problems.

This update should not have been created independently while that other update was still in testing. Either the new bind build from this update should have been edited into that update, or this update should not have been submitted before that one was pushed stable.

User Icon filiperosset commented & provided feedback 4 years ago
karma

no regressions noted


Please login to add feedback.

Metadata
Type
security
Severity
high
Karma
1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
4 years ago
in testing
4 years ago
BZ#1679925 CVE-2018-5744 CVE-2018-5745 CVE-2019-6465 bind: various flaws [fedora-all]
0
0

Automated Test Results