On 9/5/06, Peter Dyballa <[EMAIL PROTECTED]> wrote: > > Am 05.09.2006 um 04:41 schrieb Alexander Hansen: > > > You never specified explicity what happened so i don't really have > > enough information to tell you more about what you could have done. > > If it failed because of a build conflict being swapped back in > > prematurely, then this generally goes away with repeated invocations > > of "fink update-all". > > It was during a "fink update-all": > > dpkg-deb -b /sw/src/fink.build/root-fink-buildlock- > ghostscript-8.54-1 /sw/src/fink.build > dpkg-deb: baue Paket »fink-buildlock-ghostscript-8.54-1« in »/sw/src/ > fink.build/fink-buildlock- > ghostscript-8.54-1_2006.09.03-14.55.07_darwin-powerpc.deb«. > Setting build lock... > /sw/bin/dpkg-lockwait -i /sw/src/fink.build/fink-buildlock- > ghostscript-8.54-1_2006.09.03-14.55.07_darwin-powerpc.deb > Wähle vormals abgewähltes Paket fink-buildlock-ghostscript-8.54-1. > dpkg: Betrachte .../fink-buildlock- > ghostscript-8.54-1_2006.09.03-14.55.07_darwin-powerpc.deb, welches > fink-buildlock-ghostscript-8.54-1 enthält: > fink-buildlock-ghostscript-8.54-1 kollidiert mit libjasper1 > libjasper1 (Version 1.701.0-1002) ist installiert. > /sw/bin/dpkg: Fehler beim Bearbeiten von /sw/src/fink.build/fink- > buildlock-ghostscript-8.54-1_2006.09.03-14.55.07_darwin-powerpc.deb > (--install): > kollidierende Pakete - installiere fink-buildlock-ghostscript-8.54-1 > nicht > Fehler traten auf beim Bearbeiten von: > /sw/src/fink.build/fink-buildlock- > ghostscript-8.54-1_2006.09.03-14.55.07_darwin-powerpc.deb > ### execution of /sw/bin/dpkg-lockwait failed, exit code 1 > Can't set build lock for ghostscript (8.54-1) > > If any of the above dpkg error messages mention conflicting packages > or > missing dependencies -- for example, telling you that the package > fink-buildlock-ghostscript-8.54-1 conflicts with something else -- > fink has > probably gotten confused by trying to build many packages at once. > Try > building just this current package ghostscript (i.e, "fink build > ghostscript"). When that has completed successfully, you could retry > whatever you did that led to the present error. > > Regardless of the cause of the lock failure, don't worry: you have > not wasted > compiling time! Packages that had been completely built before this > error > occurred will not have to be recompiled. > > See http://wiki.finkproject.org/index.php/Fink:buildlocks for more > information. > Failed: buildlock failure > > > Last night another "fink update-all" was performed and > ghostscript-8.54-2 was (re-)installed. And now libjasper1 did not > matter at all. > > -- > Greetings > > Pete > > From error to error, one discovers the entire truth. > - Sigmund Freud > > > > > But what happened just before this? fink usually tries to remove a package that is buildconflicted. What you're showing looks like what I said before: something else got added after libjasper1 was removed, which unfortunately makes the buildconflict code put the removed package back.
-- Alexander K. Hansen Fink Documenter (still) ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
