Welcome! Log In Create A New Profile
We moved to this Improved Forum!







Do not use this old forum, we MOVED to here!

Advanced

Installing E16

Posted by manchette 
This forum is currently read only. You can not log in or make any changes. This is a temporary situation.
Installing E16
April 08, 2008 11:50PM
Hello,

i'd like to install E16 but a file from E17 cvs ( Enlightenment_DR17-cv
s-core-metapackage-cvs-32.1) is blocking the E16 install process.

I can't get rid of this file so far, can you help me ?

thanks wink

- from yast i can't remove the E17 file (errors)

- from console :
via smart packet manager it gives an error or via rpm command it says the package is not installed (though it produces conflicts in yast or smart ...)

# smart remove Enlightenment_DR17-cvs-core-metapackage-cvs-32.1

... ...

/sbin/ldconfig: chemin relatif `0' utilisé pour construire la cache
error: %postun(Enlightenment_DR17-cvs-core-metapackage-cvs-32.1.i586) scriptlet failed, exit status 1

- from console with rpm command it gives me errors again : saying the package is not installed !! But when i try to install enlightenment it gives me many conflicts

.... ...

# rpm -e --nodeps --noscripts --notriggers Enlightenme
nt_DR17-cvs-core-metapackage-cvs-32.1@i586
erreur: le paquetage Enlightenment_DR17-cvs-core-metapackage-cvs-32.1@i586 n'est
pas installé
linux-os103:/home/fabrice # exit
exit
fabrice@linux-os103:~> su
Mot de passe :
linux-os103:/home/fabrice # smart install enlightenment
... ... ...
erreur: file /usr/bin/enlightenment from install of enlightenment-0.16.999.042-3
.1 conflicts with file from package Enlightenment_DR17-cvs-core-metapackage-cvs-
32.1
erreur: file /usr/bin/enlightenment_fm from install of enlightenment-0.16.999.04
2-3.1 conflicts with file from package Enlightenment_DR17-cvs-core-metapackage-c
vs-32.1
erreur: file /usr/bin/enlightenment_imc from install of enlightenment-0.16.999.0 42-3.1 conflicts with file from package Enlightenment_DR17-cvs-core-metapackage- cvs-32.1
erreur: file /usr/bin/enlightenment_init from install of enlightenment-0.16.999. 042-3.1 conflicts with file from package Enlightenment_DR17-cvs-core-metapackage -cvs-32.1
erreur: file /usr/bin/enlightenment_remote from install of enlightenment-0.16.99 9.042-3.1 conflicts with file from package Enlightenment_DR17-cvs-core-metapacka ge-cvs-32.1
erreur: file /usr/bin/enlightenment_start from install of enlightenment-0.16.999 .042-3.1 conflicts with file from package Enlightenment_DR17-cvs-core-metapackag e-cvs-32.1
erreur: file /usr/bin/enlightenment_sys from install of enlightenment-0.16.999.0 42-3.1 conflicts with file from package Enlightenment_DR17-cvs-core-metapackage- cvs-32.1
erreur: file /usr/bin/enlightenment_thumb from install of enlightenment-0.16.999 .042-3.1 conflicts with file from package Enlightenment_DR17-cvs-core-metapackag e-cvs-32.1
erreur: file /usr/share/xsessions/enlightenment.desktop from install of enlighte nment-0.16.999.042-3.1 conflicts with file from package Enlightenment_DR17-cvs-c ore-metapackage-cvs-32.1


Any idea of how i can get rid of the E17 cvs file ? this will certainly unblock the E16 install process

Cheers wink



Edited 1 time(s). Last edit at 04/08/2008 11:52PM by manchette.
Re: Installing E16
April 09, 2008 09:39PM
hi,
fyi it looks like embryo was responsible for all this mess.

1st : add E channel to smart :
# smart channel --add [software.opensuse.org]

2d :
Removing embryo and then installing enlightenment with smart package manager was ok .

you need to check you've got all these :
ecore-0.9.9.031-2.4@i586 eet-0.9.10.031-2.1@i586 evas-0.9.9.031-4.1@i586
edb-1.0.5.007-5.1@i586 embryo-0.9.1.031-2.1@i586
edje-0.5.0.031-2.3@i586 enlightenment-0.16.999.031-7.3@i586

i'd not, so i had to add some extra packages like edb ... which is quite strange.
But at the end it Works :p
Re: Installing E16
April 13, 2008 06:50AM
manchette, it seems you are not using Elive,but OpenSuse...it's an Elive forum, so, i close this subject.



Edited 1 time(s). Last edit at 04/13/2008 06:52AM by phoenix.
Sorry, you can't reply to this topic. It has been closed.