krb5-admin-server postinst has broken debconf if RUN_KADMIND set in /etc/default/krb5-admin-server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
krb5 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Package installation fails on postinst due to broken debconf when /etc/default/
This happens because the .config script [0] sets debconf question krb5-admin-
[0] https:/
[1] https:/
This bug seems to go back to at least Xenial (and also affects debian packaging too). We worked around this locally by removing RUN_KADMIND from our local defaults file, but this was an annoying bug to sort out and should probably be fixed. That said I'm not sure if it would be more appropraite to remove the db_set from [0] or add the question back to [1].
summary: |
- krb5-admin-server postinst has broken debconf if RUN_KADMIND set to - false in /etc/default/krb5-admin-server + krb5-admin-server postinst has broken debconf if RUN_KADMIND set in + /etc/default/krb5-admin-server |
Changed in krb5 (Ubuntu): | |
status: | New → Confirmed |
I think this is basically only a problem on upgrade from older versions of krb5, in particular from prior to the 1.12 era to the current packaging. krb5-admin- server.
As part of adding support for systemd units, I decided to drop support for the run_kadmind variable, and bungled the upgrade path.
This is an issue for upgrades from trusty or precise to anything newer if you are running krb5-admin-server.
There's a very simple work around: remove run_kadmind from /etc/default/
I'll fix for Debian shortly.
What Ubuntu versions is this worth doing a fix for?