On 2012-07-05 14:17, joaoBR wrote:
Em Thu, 05 Jul 2012 13:18:36 -0500
Rusty Nejdl <[email protected]> escreveu:
>>
>> Well, the one example you include is a busted port:
>>
>> ===> libkonq-4.8.4 is already installed
>> You may wish to ``make deinstall'' and install this port
>> again
>> by ``make reinstall'' to upgrade it properly.
>> If you really wish to overwrite the old port of
x11/libkonq
>> without deleting it first, set the variable
>> "FORCE_PKG_REGISTER" in your environment or the "make install"
>> command line.
>>
>> You simply need to deinstall and reinstall that one as it is not
>> installed fully/correctly.
>>
>> portmaster -f libkonq
>>
>> That doesn't seem that big of a deal and should cover a portion
of
>> your issues... what's next?
>>
>
>
> you do not need to repeat what I already have said ...
>
> take your time to read my last comment for better understanding
>
> I know how to solve the problems, thing is that makes the problem
> not go away
These comments are not going to get you any help.
>
>
> but I am curious, what make you think the port is busted?
Whenever I see the above, it is because a port shows as being
installed but then a piece of it is missing (a specific file) so the
ports system tries to reinstall it.
From reading your emails, including this one, I don't think you
want
to get this fixed and instead want to complain about this.
slow down, don't assume things ... you have not read with attention
before
I explain again
no port is damaged (or busted), before starting the upgrade process
everything is fine as reported by pkgdb -F, pkgdb -L and pkg_libchk,
absolutely clean and everything working fine and smooth
then, sooner or later while upgrading, one dependency port is still
the former version
the install script looks for the actual version which is not
installed
and goes to "add the apparently missing port"
after compiling it, it tries to install it AND NOW IT IS FAILING
because the port is already installed, that was quite clear to see in
the attached file
what was necessary was an upgrade and not a new install
ok, better explained now?
and that is the reason WHY `portupgrade -a` is not working for the
kde4
upgrade, because it IS necessary to proceed in a certain order for
not
being caught by this problem
BTW this problem is an old and nasty upgrade problem, only it is easy
to
solve when only one or two ports are envolved
I have seen some bumps on upgrades and usually for the major ones, I
wait about 2 days for any port changes to occur and then run the
upgrades. I have to ask but did you follow the instructions in
/usr/ports/UPDATING? If not, you will run into problems like this.
Rusty Nejdl
_______________________________________________
kde-freebsd mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-freebsd
See also http://freebsd.kde.org/ for latest information
