Azureus_220.127.116.11 dependency missing
kris at obsecurity.org
Fri Nov 4 19:17:46 PST 2005
On Fri, Nov 04, 2005 at 05:06:28PM -1000, Randy Bush wrote:
> >> FORCE_PKG_REGISTER=YES
> > This is a nice recipe for corrupting your package installations. If
> > you are encountering situations where you think you need to use it,
> > you're doing something wrong.
> it's been there since 1948, $diety is about the only one who
> knows why. what's the danger?
You spam new packages on top of old, leaving behind extra files that
can confuse later builds.
> so, i removed it and
> roam.psg.com:/usr/src# cvsup -g -L 2 cvs-supfile 2>&1 > tee cvsup.log
> roam.psg.com:/usr/src# grep azureus cvsup.log
> roam.psg.com:/usr/src# cd /usr/ports/net/azureus
> roam.psg.com:/usr/ports/net/azureus# make
> ===> Vulnerability check disabled, database not found
> ===> Extracting for azureus-18.104.22.168_3
> => Checksum OK for Azureus_22.214.171.124_source.zip.
> ===> azureus-126.96.36.199_3 depends on file: /usr/local/eclipse/plugins/org.eclipse.swt.gtk.freebsd.x86_3.1.1.jar - found
> ===> azureus-188.8.131.52_3 depends on executable: unzip - found
> /usr/local/jdk1.5.0/bin/jar: not found
> *** Error code 127
> Stop in /usr/ports/net/azureus.
Right, I didn't say it was a magic fix. It's possible that if you've
been relying on this for a long time because of an incorrect way you
do your upgrades then your system is cluttered with old files and that
caused the ports tree to become confused here.
Look at the example in the pkg_which manpage and go through and clean
out all the old cruft you have on your system (back it up first in
case you make a mistake).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20051104/92c382ad/attachment.bin
More information about the freebsd-ports