Azureus_188.8.131.52 dependency missing
boris at brooknet.com.au
Fri Nov 4 19:26:26 PST 2005
On 05/11/2005, at 2:17 PM, Kris Kennaway wrote:
> On Fri, Nov 04, 2005 at 05:06:28PM -1000, Randy Bush wrote:
>>> 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-184.108.40.206_3
>> => Checksum OK for Azureus_220.127.116.11_source.zip.
>> ===> azureus-18.104.22.168_3 depends on file: /usr/local/eclipse/
>> plugins/org.eclipse.swt.gtk.freebsd.x86_3.1.1.jar - found
>> ===> azureus-22.214.171.124_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).
Actually, I've pulled lioux up for this before :) The azureus port
needs JAVA_EXTRACT=yes since it is using jar in the extract stage.
Pointyhat would have picked it up soon enough.
More information about the freebsd-ports