On 3/16/13 10:13 AM, Viv Kendon wrote: > Many thanks, nearly there...new error below, old error snipped: > > On Sat, 16 Mar 2013, Alexander Hansen wrote: > >> On 3/16/13 5:00 AM, Viv Kendon wrote: >>> I am not sure when image-oct362 last built for me, I have been updating >>> the rest by hand for a while. Should I perhaps just update to octave >>> 364 instead? >>> >>> <big snip> >>> >> Oops. That was supposed to be "mkoctfile-gcc4.7"--it's autogenerated >> and I picked the wrong format. A fixed has been sent out, and it will >> be available via selfupdate shortly. > > And after it arrived, I tried again. Now I get (on a headless server): > > Preparing to replace image-oct362 1.0.15-4 (using > .../image-oct362_2.0.0-1_darwin-x86_64.deb) ... > X connection to localhost:10.0 broken (explicit kill or server shutdown). > X connection to localhost:10.0 broken (explicit kill or server shutdown). > dpkg: warning - old pre-removal script returned error exit status 1 > dpkg - trying script from the new package instead ... > /sw/bin/xvfb-run: line 172: > /sw/share/octave/3.6.2/image-2.0.0/octave-forge-prerm: No such file or > directory > /sw/bin/dpkg: error processing > /sw/fink/dists/stable/main/binary-darwin-x86_64/sci/image-oct362_2.0.0-1_darwin-x86_64.deb > (--install): > subprocess new pre-removal script returned error exit status 127 > X connection to localhost:10.0 broken (explicit kill or server shutdown). > X connection to localhost:10.0 broken (explicit kill or server shutdown). > dpkg: error while cleaning up: > subprocess post-installation script returned error exit status 1 > Errors were encountered while processing: > > /sw/fink/dists/stable/main/binary-darwin-x86_64/sci/image-oct362_2.0.0-1_darwin-x86_64.deb > > ### execution of /sw/bin/dpkg-lockwait failed, exit code 1 > Updating the list of locally available binary packages. > Scanning dists/stable/main/binary-darwin-x86_64 > New package: > dists/stable/main/binary-darwin-x86_64/sci/image-oct362_2.0.0-1_darwin-x86_64.deb > > Failed: can't install package image-oct362-2.0.0-1 > > > The rest of octave 362 has updated without problem... > > many thanks, > -- Viv > ________________________________________________ > Dr Viv Kendon http://quantum.leeds.ac.uk/~viv > tel: +44 113 343 4864 Physics and Astronomy > Quantum Information Group University of Leeds >
[ The optional use of "xvfb-run" is common to all of the Octave Forge packages, and was motivated by a prior bug report from you. :-) ] I probably should have put the "octave-forge-prerm" and "octave-forge-postinst" scripts in a directory that doesn't have the package version, since that makes the new and old versions incompatible. Sorry about that. See if you can use "xvfb-run fink update image-oct362" to work around this. If not, try editing /sw/var/lib/dpkg/info/image-oct362 as a superuser and change /sw/share/octave/3.6.2/image-1.0.15/octave-forge-prerm to xvfb-run /sw/share/octave/3.6.2/image-1.0.15/octave-forge-prerm -- Alexander Hansen, Ph.D. Fink User Liaison My package updates: http://finkakh.wordpress.com/ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ 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
