portupgrade weirdness

Nelis Lamprecht nlamprecht at gmail.com
Tue Apr 5 04:30:02 PDT 2005


Replying to my own message.

For the archives, the problem below was caused because my local cvsup
mirror was not in sync with the INDEX file I downloaded from the main
FreeBSD site. Sorry, should have checked a specific port version
Makefile before posting the question.

Nelis

On Apr 5, 2005 1:17 PM, Nelis Lamprecht <nlamprecht at gmail.com> wrote:
> Hi,
> 
> I seem to be having some difficulty upgrading some of my packages
> using portupgrade. Here is an example:
> 
> medusa# portversion -vl "<" | grep m4
> m4-1.4.1                    <  needs updating (port has 1.4.3)
> 
> medusa# portupgrade m4
> medusa#
> 
> Basically it's doing nothing as if it thinks the port is already
> updated ? This happens with my php4 port as well as the quagga port
> and one or two others. Some update fine, some don't. If I do a
> portupgrade -f it installs the same version currently installed and
> still doesn't install the new port.
> 
> Any ideas ?
> 
> Thanks.
> 
> Nelis
>


More information about the freebsd-questions mailing list