On Fri, Aug 07, 2009 at 11:23:47AM -0500, Robert Wyatt wrote: > I had gdal-dev and -shlibs installed (but not gdal) and in updating all > I had to manually remove gdal-dev in order to update gdal-shlibs. > > * Here are the installed but outdated packages: > Information about 9284 packages read in 1 seconds. > (i) gdal-dev 1.6.1-1001 > GDAL/OGR development headers > (i) gdal-shlibs 1.6.1-1001 > GDAL/OGR shared libraries > > bash-4.0$ date; fink update-all [...] > The following 2 packages will be installed or updated: > gdal-dev gdal-shlibs > Setting runtime build-lock... > dpkg-deb -b /sw/src/fink.build/root-fink-buildlock-gdal-1.6.1-1001 > /sw/src/fink.build > dpkg-deb: building package `fink-buildlock-gdal-1.6.1-1001' in > `/sw/src/fink.build/fink-buildlock-gdal-1.6.1-1001_2009.08.07-10.36.30_darwin-powerpc.deb'. > Installing build-lock package... > /sw/bin/dpkg-lockwait -i > /sw/src/fink.build/fink-buildlock-gdal-1.6.1-1001_2009.08.07-10.36.30_darwin-powerpc.deb > Selecting previously deselected package fink-buildlock-gdal-1.6.1-1001. > dpkg: regarding > .../fink-buildlock-gdal-1.6.1-1001_2009.08.07-10.36.30_darwin-powerpc.deb > containing fink-buildlock-gdal-1.6.1-1001: > fink-buildlock-gdal-1.6.1-1001 conflicts with gdal-dev (<< 1.6.1) > gdal-dev (version 1.6.0-1002) is installed. > /sw/bin/dpkg: error processing > /sw/src/fink.build/fink-buildlock-gdal-1.6.1-1001_2009.08.07-10.36.30_darwin-powerpc.deb > > (--install): > conflicting packages - not installing fink-buildlock-gdal-1.6.1-1001 > Errors were encountered while processing: > > /sw/src/fink.build/fink-buildlock-gdal-1.6.1-1001_2009.08.07-10.36.30_darwin-powerpc.deb > ### execution of /sw/bin/dpkg-lockwait failed, exit code 1 > Can't set build lock for gdal (1.6.1-1001) > > gdal: > depends: gdal-shlibs (= 1.6.1-1001) > buildconflicts: gdal-dev (<< 1.6.1) > > gdal-dev: > depends: gdal-shlibs (= 1.6.1-1001) > replaces: gdal (<< 1.6.1-1001) > conflicts: gdal (<< 1.6.1-1001) > > gdal-shlibs: > replaces: gdal (<< 1.6.1-1001) > conflicts: gdal (<< 1.6.1-1001) > > So gdal failed because the older gdal-dev was present, but it couldn't > remove it because gdal-dev was what was really being updated?
That's the pattern, yes. I don't know if it's "because it's being updated" or "because it's being built", but I know that if a .info specifies a BuildConflicts:FOO when FOO is a package in the same .info, the engine sometimes does not remove FOO before building, and then the buildlock fails because the BConflicts'ed pkg is not removed. It's ugly, it's a long-standing problem, and I can think of several places in the engine where it *could* be bugged but have never actually looked carefully. But the present behavior makes it clear how to fix the problem: just remove the pkg that the buildlock says is in the way. dan -- Daniel Macks dma...@netspace.org http://www.netspace.org/~dmacks ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
