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.
** Also affects: silo (Ubuntu Hardy)
Importance: Undecided
Status: New
** Changed in: silo (Ubuntu Hardy)
Assignee: (unassigned) => Adam Conrad (adconrad)
** Changed in: silo (Ubuntu Hardy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/431106
Title:
Patch to stop siloconfig from running from dpkg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/silo/+bug/431106/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
