...well, dunno if it's buildlock, but something's gone whacky:
If this is not true (perhaps the previous build process crashed?),
just remove the fink package:
fink remove fink-buildlock-distcc-2.18.3-1
Then retry whatever you did that led to the present error.
...
Benjamin Reed wrote:
disco-volante:/sw/fink/dists/local/rangerrick/common/main/finkinfo/devel
ranger$ fink remove fink-buildlock-distcc-2.18.3-1
Information about 4465 packages read in 7 seconds.
Failed: no package specified for command 'remove'!
On closer look, that package wasn't even
On Jan 8, 2005, at 4:06 PM, Benjamin Reed wrote:
Should be easy enough to replicate, just have a package that fails
CompileScript.
No need even:
/sw/lib/perl5/Fink# fink remove ztrack-1.0-1
Information about 5062 packages read in 4 seconds.
Failed: no package specified for command 'remove'!
I have been using the freetype2-2.1.9-1 package from neeri's exp dir for
quite some time without problems. For all my purposes it was backward
compatible with 2.1.3 (i.e. things compiled with the old library
continue to run with the new one, and everything builds against the new
version
On Jan 8, 2005, at 6:39 PM, Martin Costabel wrote:
I have been using the freetype2-2.1.9-1 package from neeri's exp dir
for quite some time without problems. For all my purposes it was
backward compatible with 2.1.3 (i.e. things compiled with the old
library continue to run with the new one,
When a user decides no longer to use one of fink's
perl packages, and to use apple's perl, he is left with
a large number of broken pkgs, which have hardcoded
somewhere /sw/bin/perl, w/o explicitly depending on it.
To get an idea of the extent of the problem, I just tested
files in /sw/bin _ and
On Jan 8, 2005, at 9:39 AM, Martin Costabel wrote:
I have been using the freetype2-2.1.9-1 package from neeri's exp dir
for quite some time without problems. For all my purposes it was
backward compatible with 2.1.3 (i.e. things compiled with the old
library continue to run with the new one,
Jean-François Mertens wrote:
[]
Would an update to 2.1.7 (for a short time hopefully) not satisfy scribus ?
Unfortunately not. I cannot say I understand this, but there it is.
I made a freetype2-2.1.7 package (had to redo the patch file), but I
still get the crash with it. Looking at the
