Actions
Bug #5199
closed
Default value fix for package fields is not working properly
Start date:
09/24/2015
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2.5
Affected Architecture:
All
Description
The change made in 9fbcedee3b1c8e629d92a3546bf79d81ec90dca3 to improve handling of default values in package fields has a problem. It appears to not be properly reset between fields, so it is putting incorrect default values into other unrelated fields.
The easiest example is to install the FreeRADIUS2 package on a current 2.2.5 snapshot and then try adding a user. Nearly every field on the page is populated with an incorrect default value.
Definitely a problem on 2.2.5, might also be on 2.3.
Updated by Jim Pingle about 9 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 0b74438e962ead448d144f7f246f599efe01c7a9.
Updated by Jim Pingle about 9 years ago
Applied in changeset 83b48b440146be346e0b05ab6e42d82dc31b34c8.
Updated by Chris Buechler about 9 years ago
- Status changed from Feedback to Resolved
- Affected Version changed from 2.2.x to 2.2.5
fixed
Actions