Ticket #1298 (closed task: fixed)

Opened 11 years ago

Last modified 10 years ago

Get rid of debconf-hack

Reported by: jdreed Owned by:
Priority: normal Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:  zephyr:#108


The only place we use it is in zephyr-clients, and my understanding is that nobody actually _likes_ it. The note in there suggests it is used to prevent zephyr from starting before it is configured, but since 2.1.20010518.SNAPSHOT-18 (Thu, 19 Jul 2007 04:31:53 -0400), it has supported Hesiod. Also, with #702, the installer will preseed these debconf values. Also also, what are the actual consequences of zhm briefly starting, and then being restarted by zephyr-config?

Change History

comment:1 Changed 11 years ago by jdreed

OK, sigh, I see the problem. zephyr-clients restarts zhm, which looks for Hesiod sloc information, and doesn't find it because Hesiod is still configured for .localdomain, and the restart fails, which is fatal. (Arguably, _that_ is the bug here, and we should, like, file it). I'll note that fixing this is as simple as Pre-Depends: debathena-hesiod-config, but geofft also notes we can copy the code into zephyr-config's preinst, which is also fine.

comment:2 Changed 11 years ago by jdreed

  • Upstream bug set to zephyr:#108

comment:3 Changed 11 years ago by jdreed

  • Status changed from new to committed

comment:4 Changed 10 years ago by jdreed

  • Status changed from committed to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.