On Mon, 22 Aug 2011 07:42:21 -0400, Alexander Hansen wrote: > On 8/21/11 11:02 PM, Sean Lake wrote: > > > sudo fink update-all Information about 10248 packages read in 0 > > seconds. The following 2 packages will be installed or updated: > > lasi-dev lasi-shlibs The following package might be temporarily > > removed: lasi-dev Do you want to continue? [Y/n] Setting runtime > > build-lock... dpkg-deb -b > > /sw/src/fink.build/root-fink-buildlock-lasi-shlibs-1.1.0-1004 > > /sw/src/fink.build dpkg-deb: building package > > `fink-buildlock-lasi-shlibs-1.1.0-1004' in > > > `/sw/src/fink.build/fink-buildlock-lasi-shlibs-1.1.0-1004_2011.08.21-19.56.34_darwin-x86_64.deb'. > > > > > Installing build-lock package... > > /sw/bin/dpkg-lockwait -i > > > /sw/src/fink.build/fink-buildlock-lasi-shlibs-1.1.0-1004_2011.08.21-19.56.34_darwin-x86_64.deb > > > > dpkg: regarding > .../fink-buildlock-lasi-shlibs-1.1.0-1004_2011.08.21-19.56.34_darwin-x86_64.deb > containing fink-buildlock-lasi-shlibs-1.1.0-1004: > > fink-buildlock-lasi-shlibs-1.1.0-1004 conflicts with lasi-dev > > lasi-dev (version 1.1.0-1003) is installed. /sw/bin/dpkg: error > > processing > > > /sw/src/fink.build/fink-buildlock-lasi-shlibs-1.1.0-1004_2011.08.21-19.56.34_darwin-x86_64.deb > > (--install): conflicting packages - not installing > > fink-buildlock-lasi-shlibs-1.1.0-1004 Errors were encountered while > > processing: > > /sw/src/fink.build/fink-buildlock-lasi-shlibs-1.1.0-1004_2011.08.21-19.56.34_darwin-x86_64.deb > > > > ### execution of /sw/bin/dpkg-lockwait failed, exit code 1 > > Can't set build lock for lasi-shlibs (1.1.0-1004) > > I'm cc'ing the last person to commit updates to this package, because > the package currently won't build without manual intervention. It > looks like the intention is that any currently installed lasi-dev > package gets removed before the build, but this doesn't happen. > > As a workaround, use > > fink remove lasi-dev > fink install lasi-dev > > and it will get updated. Then you should be able to run "fink > update-all."
Yup. There are flag-ordering problems I wasn't able to solve (thanks cmake!) that cause incorrect or failed building of it if a lasi-dev is currently installed. Here's the commit note about it: RCS file: /cvsroot/fink/dists/10.4/unstable/main/finkinfo/graphics/Attic/lasi.info,v revision 1.19 date: 2010/08/03 02:38:23; author: dmacks; state: Exp; lines: +1 -0 avoid seeing previously-installed self during build (due to buggy -I ordering)...may trigger a fink engine bug, but at least prevents pkg from mis-building I don't know why the BuildConflicts:lasi-dev doesn't trigger removal of the package, but buildlock is behaving correctly here as the last and strictest checkpoint to enforce it. I vaguely recognize "foo:BuildConflicts:foo gets ignored" as a long-standing engine bug that is rare enough nobody has worked to solve. dan -- Daniel Macks [email protected] ------------------------------------------------------------------------------ uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Fink-users mailing list [email protected] List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
