On Mon, Mar 30, 2009 at 10:03:28PM -0000, Andreas Hasenack wrote: > I'm sorry, I don't mean to transform this into a Debian Packaging 101 :) > We can continue elsewhere, or just point me to some docs or other > packages that have a similar problem. > > So what if only python-zopeinterface is being upgraded? landscape- > sysinfo is installed and is not being upgraded in this example. Then > suddenly when python-zopeinterface is being configured (the new > version), the cron job hits. How can the cron job detect this situation > and decide to not run?
Oh, that wasn't clear from this report. If only python-zopeinterface was being upgraded, I would expect the window for this race to be very small (but still present). The window is very large, though, when upgrading from 8.10 to 9.04. Because so many packages are being upgraded at once, the packages will stay unconfigured (and potentially non-functional) for a long time. I'm surprised this hasn't come up before (which means it probably has and I'm not aware of it). There may be a standard pattern for dealing properly with this. I suggest taking the question to [email protected]. -- - mdz ** Changed in: landscape-client (Ubuntu) Importance: Undecided => Low ** Changed in: landscape-client (Ubuntu) Status: New => Triaged -- landscape-sysinfo crashed with ImportError in <module>() https://bugs.launchpad.net/bugs/349996 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
