Once I removed dns_canonicalize_hostname = false from libdefaults in /etc/krb5.conf (not quite sure why I had that there in the first place), everything started working as before.
yes, this broke my setup
and I believe this violates packaging guidelines - these are not specific for doing changes via sed instead of new file, but I believe this section can be applied appropriately: "In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when /not/ to use noreplace is when a package's configuration file changes so that the new package revision wouldn't work with the config file from the previous package revision." ... the new package works just fine without the change, so the change is forbidden
sad that the person who found out before me didn't stop this update and gave positive karma instead :-(
Please keep comments to the bugzilla you have filed. The changes are working as intended, and we will work to fix it over there, not in the comments of an update that was submitted to stable a day before you necro'd the comment thread.
This update has been submitted for testing by rharwood.
This update has been pushed to testing.
Works
Works for me. No regressions noted compared to previous version.
works for me
Once I removed dns_canonicalize_hostname = false from libdefaults in /etc/krb5.conf (not quite sure why I had that there in the first place), everything started working as before.
Works great! LGTM! =)
This update has been submitted for stable by rharwood.
This update has been pushed to stable.
yes, this broke my setup and I believe this violates packaging guidelines - these are not specific for doing changes via sed instead of new file, but I believe this section can be applied appropriately: "In other words, think hard before overwriting local changes in configuration files on package upgrades. An example case when /not/ to use noreplace is when a package's configuration file changes so that the new package revision wouldn't work with the config file from the previous package revision." ... the new package works just fine without the change, so the change is forbidden sad that the person who found out before me didn't stop this update and gave positive karma instead :-(
Please keep comments to the bugzilla you have filed. The changes are working as intended, and we will work to fix it over there, not in the comments of an update that was submitted to stable a day before you necro'd the comment thread.
Why people give +1 karma, it should marked with -1
I gave +1 because I didn't realise that is wasn't me that put dns_canonicalize_hostname = false into krb5.conf. Too late to fix now anyway.