At 2011-06-20 04:03:52 +0200, <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 6/19/11 9:39 PM, zooloo wrote: >> While following this list, I have encountered this "sanity" answer many >> times, so I was quite confused when a buildlock error (that had made the >> previous 'fink update-all' fail) disappeared when I ran 'fink >> selfupdate' and then 'fink update-all' once again. Unfortunately, the >> original error message had already left the terminal buffer when I >> noticed the change. As far as I can remember, it reported some >> conflicting preconditions (like "X is required, but Y is installed"). > > The most common occurrences of the style of error you saw are the > intended behavior of the buildlock system: to keep you from removing a > dependency for the package you are currently building. > > It's possible that your selfupdate downloaded a fix to whatever package > was complaining (such that you weren't performing an _identical_ > operation when using 'update-all' again). > > If you're not seeing buildlock errors now, your Fink tree should be fine.
Thanks for this clarification. Cheers, Zoo Loo ____________________________________________________________ Receive Notifications of Incoming Messages Easily monitor multiple email accounts & access them with a click. Visit http://www.inbox.com/notifier and check it out! ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Fink-beginners mailing list [email protected] List archive: http://news.gmane.org/gmane.os.apple.fink.beginners Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-beginners
