Given that it's hard to say, several years later, if the above fix is "correct" for hardy (since it changes the behaviour experienced over the last several years), I'm going to just "cheat" and skip running siloconfig if we're running in a launchpad-style buildd chroot.
Given that it's hard to say, several years later, if the above fix is "correct" for hardy (since it changes the behaviour experienced over the last several years), I'm going to just "cheat" and skip running siloconfig if we're running in a launchpad-style buildd chroot.