Conflicting Files

tzoi516

tzoi516

I have a few QT4 related ports that are getting like errors after running portmaster -a:

Code: 
===>   Installing ldconfig configuration file
===>  Installing for qt4-clucene-4.8.5
===>  Checking if textproc/clucene-qt4 already installed
===>   Registering installation for qt4-clucene-4.8.5
Installing qt4-clucene-4.8.5...pkg-static: qt4-clucene-4.8.5 conflicts with qt4-clucene-4.8.5 (installs files into the same place).  Problematic file: /usr/local/lib/qt4/libQtCLucene.la
*** Error code 70

Stop.
make: stopped in /usr/ports/textproc/clucene-qt4

===>>> Installation of qt4-clucene-4.8.5 (textproc/clucene-qt4) failed
===>>> Aborting update

When I try to portmaster -R clucene-qt4 it says it's not installed. When I try to install it from ports I get that error. I try pkg delete clucene-qt4 and it says it's not installed. Happens with the other QT4 related files. Any suggestions would be appreciated. Thanks. :)
 
The package may have registered as clucene instead of qt4-clucene.

I try pkg delete clucene-qt4 and it says it's not installed. Happens with the other QT4 related files.
Click to expand...
If anything it's qt4-clucene not clucene-qt4.
 
SirDice said:
The package may have registered as clucene instead of qt4-clucene.

I try pkg delete clucene-qt4 and it says it's not installed. Happens with the other QT4 related files.
Click to expand...
If anything it's qt4-clucene not clucene-qt4.
Click to expand...
I hand poked everything but the quote, so I typed it wrong. Sorry for the confusion. :)
 
SirDice said:
What does pkg info -x clucene produce?
Click to expand...
Code: 
clucene-2.3.3.4_2
qt4-clucene-4.8.5

I re-ran portmaster -a again. I don't understand why part of it says "clucene-qt4"
Code: 
===>   Installing ldconfig configuration file
===>  Installing for qt4-clucene-4.8.5
===>  Checking if textproc/clucene-qt4 already installed
===>   Registering installation for qt4-clucene-4.8.5 as automatic
Installing qt4-clucene-4.8.5...pkg-static: qt4-clucene-4.8.5 conflicts with qt4-clucene-4.8.5 (installs files into the same place).  Problematic file: /usr/local/lib/qt4/libQtCLucene.la
*** Error code 70

Stop.
[b]make: stopped in /usr/ports/textproc/clucene-qt4

===>>> Installation of qt4-clucene-4.8.5 (textproc/clucene-qt4) failed
===>>> Aborting update

===>>> Update for textproc/clucene-qt4 failed[/b]
===>>> Aborting update

===>>> Killing background jobs
Terminated
===>>> The following actions were performed:
	Installation of devel/qmake4 (qt4-qmake-4.8.5_1)

===>>> Deleting installed build-only dependencies
Deinstallation has been requested for the following 1 packages:

	qt4-qmake-4.8.5_1

The deinstallation will free 5 MB
[1/1] Deleting qt4-qmake-4.8.5_1... done


===>>> You can restart from the point of failure with this command line:
       portmaster <flags> textproc/clucene-qt4 devel/qt4-designer devel/qt4-moc devel/qt4-rcc devel/qt4-uic devel/qt4-testlib 

===>>> Exiting
 
I also looked at /usr/local/lib/qt4/libQtCLucene.la and didn't see textproc/clucene-qt4 in there.
Code: 
# libQtCLucene.la - a libtool library file
# Generated by qmake/libtool (2.01a) (Qt 4.8.5) on: Thu Jan 9 08:06:38 2014
# The name that we can dlopen(3).
dlname='libQtCLucene.so.4'

# Names of this library.
library_names='libQtCLucene.so.4.8.5 libQtCLucene.so.4 libQtCLucene.so'

# The name of the static archive.
old_library='libQtCLucene.a'

# Libraries that this one depends upon.
dependency_libs='-L/usr/local/lib/qt4 -L/usr/local/lib/qt4 -L/usr/local/lib  -lQtCore -L/usr/local/lib/qt4 -L/usr/local/lib/qt4 -L/usr/local/lib '

# Version information for libQtCLucene.la
current=48
age=0
revision=5

# Is this an already installed library.
installed=yes

# Files to dlopen/dlpreopen.
dlopen=''
dlpreopen=''

# Directory that this library needs to be installed in:
libdir='/usr/local/lib/qt4'
 
It almost looks like portmaster has a problem with PKGNAMEPREFIX and uses it as PKGNAMESUFFIX.
 
Several QT4 ports have been renamed:

20140107:
AFFECTS: users of Qt 4 ports
AUTHOR: makc@FreeBSD.org

Qt 4 ports framework has been reworked, several ports have been renamed.
To ease upgrading run the following set of commands:

# pkg set -o devel/qt4-declarative:x11-toolkits/qt4-declarative
# pkg set -o devel/qt4-qtestlib:devel/qt4-testlib
# pkg set -o textproc/qt4-clucene:textproc/clucene-qt4
# pkg set -o www/qt4-webkit:www/webkit-qt4
# pkg set -o x11/qt4-opengl:graphics/qt4-opengl
Click to expand...

I upgraded before this information was in /usr/ports/UPDATING, so in turn ended up deleting and reinstalling the affected ports one at a time :(
 
Interesting. I've been dealing with this since Monday, and when I didn't see it in /usr/ports/UPDATING I assumed from that point on it was my system. Thanks.
 
That worked. Thanks @protocelt.

Sidenote: I wish the UPDATING would've been updated sooner, but c'est la vie.
 
Last edited by a moderator:
I forgot to add, you may need to check and fix any dependency issues resulting from manually reinstalling the affected ports with portmaster. :r

Sidenote: I wish the UPDATING would've been updated sooner, but c'est la vie
Click to expand...

Many maintainers/committers take care of several ports and are very busy. Once in a while /usr/ports/UPDATING isn't updated immediately with a port(s). I have no problem giving the maintainers/committers a break as I absolutely think they deserve it, and oui c'est vrai.
 
protocelt said:
I forgot to add, you may need to check and fix any dependency issues resulting from manually reinstalling the affected ports with portmaster. :r
Click to expand...

So far no issues - I've installed/reinstalled since updating. Now on to upgrading to FreeBSD 10.0-RC5

protocelt said:
Many maintainers/committers take care of several ports and are very busy. Once in a while /usr/ports/UPDATING isn't updated immediately with a port(s). I have no problem giving the maintainers/committers a break as I absolutely think they deserve it, and oui c'est vrai.
Click to expand...

I agree. When it comes to FreeBSD it's more of a "under my breath/if it happens it happens" type of comment. I only posted it because I do use the mailing lists and if I had known then I can send off an email if I had additional issues to report. Just something to ponder if deemed worthy.
 
You must log in or register to reply here.
Back
Top