Upgrading problem: confused dependencies
derek at computinginnovations.com
Mon Jun 16 20:51:58 UTC 2008
At 03:24 PM 6/16/2008, Dr. Jennifer Nussbaum wrote:
>Sorry, this was all discussed in the original thread. The port is the
>sysutils/libcdio port. I
>use portupgrade to keep things up to date. This machine is running FreeBSD
>In this case libcdio itself upgrades correctly, but other ports (for
>when i try to update them, report that libcdio is already installed and i
>need to make
>deinstall and then make reinstall of libcdio. I can do this, and it
>"works", but then rerunning
>portupgrade on gvfs reports the same thing about libcdio. If just do a
>make deinstall of
>libcdio and run portupgrade on gvfs, then gvfs will "sucessfully" install
>libcdio but when
>it gets back to gvfs, reports the same make deinstall/make reinstall
>thing. In general
>it seems that no matter what i do, other ports wont see libcdio as being
>installed at the current version, and im looking for a way to solve this.
I think your problem is that you are still on 6.2 which is no longer a
supported release. You can easily upgrade to 6.3 which is supported, then
update your ports. I know I have upgraded a few servers from 6.2 to 6.3
and don't recall any major issues.
>--- On Mon, 6/16/08, Derek Ragona <derek at computinginnovations.com>
>From: Derek Ragona <derek at computinginnovations.com>
>Subject: Re: Upgrading problem: confused dependencies
>To: bg271828 at yahoo.com, freebsd-questions at freebsd.org
>Date: Monday, June 16, 2008, 1:09 PM
>At 01:11 PM 6/16/2008, Dr. Jennifer Nussbaum wrote:
>Im sorry to repeat a thread from
>last week, but ive been trying ever since to upgrade a
>port and havent been able to. If someone can make another suggestion, i
>very very greatful.
>As i said in the "libcdio upgrade problems" thread, i have
>installed the libcdio port, but
>when other ports try to build, they fail, telling me that libcdio is
>already installed and i
>need to make deinstall and make reinstall of it. I did this, but got the
>Ive tried every variant, and would be happy to try brute force versions
>too. I deinstalled
>it and let the other port try to install it, i deinstalled all related
>ports so things could try
>again from scratch, i set the environment variables about forcing package
>whatever i could.
>The ports tree is up to date. Id install libcdio as a package, but its
>not new enough.
>Something must be corrupted somewhere and i want to fix it, manually if
>necessary, but i
>just dont know what to do.
>Thanks again and sorry for the new thread, but Im running out of
>Your post doesn't specify what version of FreeBSD you are using.
>Nor does your post specify what port(s) are the issue, or what utility if
>any you are using to upgrade a port.
>In general, you can use either portupgrade or portmanager to keep
>installed ports up to date.
>freebsd-questions at freebsd.org mailing list
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the freebsd-questions