Enlightenment update fail due to broken package

[Buntu Bunny]

Check if you are using third party repositories. If so disable them, since they are a common source of problems.
Furthermore run the following command in a Terminal: apt-get install -f

The following packages have unmet dependencies:

evas-loaders: Depends: libefl (>= 201212211037) but it is not installed
Depends: libgcc1 (>= 1:4.1.1) but 1:4.6.3-1ubuntu5 is installed
Depends: zlib1g (>= 1:1.1.4) but 1:1.2.3.4.dfsg-3ubuntu4 is installed
libedbus1: Depends: libefl (>= 201212211037) but it is not installed
libedbus2: Depends: libefl (>= 201212211037) but it is not installed
libedje1: Depends: libefl (>= 201212211037) but it is not installed
libeeze1: Depends: libefl (>= 201212211630) but it is not installed
libefreet1: Depends: libefl (>= 201212211630) but it is not installed

So far I've never encountered this type of problem. Do I need to disable ppa:hannes-janetzek/enlightenment-svn? Before I type that command in terminal, I would like to know what it will do. Can someone tell me please?

[Frogs Hair]

I have used the PPA in the past and the maintainer made errors at times. I usually just waited for updates which came sometimes twice daily. Do not mix the PPA with any other E17 packages from the repository or the package system will break. Go ahead and run the command with the PPA enabled.

[Buntu Bunny]

I have used the PPA in the past and the maintainer made errors at times. I usually just waited for updates which came sometimes twice daily. Do not mix the PPA with any other E17 packages from the repository or the package system will break. Go ahead and run the command with the PPA enabled.

Thank you Frogs Hair! This is what I get when I run the command

(Reading database ... 419759 files and directories currently installed.)
Unpacking libefl (from .../libefl_201212220429-538~precise1_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libefl_201212220429-538~precise1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/libecore_evas.so.1.7.99', which is also in package libecore1 201210092056-5139~precise1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libefl_201212220429-538~precise1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Are you saying that I should wait a bit and keep trying?

[Frogs Hair]

I would wait for the next round of updates.

[Buntu Bunny]

That's what I needed to know. Thanks Frogs Hair!

[Mr.Goose]

Buntu Bunny thanks for raising this issue. My system is also similarly messed up due to this bug. And thanks to Frogs Hair for your clear explanation of the situation. I had suspected as much myself.

But with all due respect chaps, describing the matter as "solved" is a tad premature IMHO. It isn't actually solved until the PPA maintainer solves it, by fixing the dependency error(s) in his packages. Is it?

In the meantime, anyone who is using his PPA will be unable to upgrade their systems, do any security patches or install any software.

I will attempt to contact the guy and alert him to the problem. Hopefully this might speed things up a bit. Then we can mark the problem as truly solved.

Best wishes, G.

[Mr.Goose]

As a temporary fix (NOT a permanent solution that justifies the matter being described as "solved"!) the following enabled my package management system to work properly:-

sudo apt-get remove libedbus1 libedbus2 libedje1 libeeze1 libefreet1 libemotion0 libethumb libethumb-bin libethumb-data

I took the view that getting E17 working was not as important as being able to receive security updates and install other stuff, if I needed to.

HTH. G.

[Buntu Bunny]

But with all due respect chaps, describing the matter as "solved" is a tad premature IMHO. It isn't actually solved until the PPA maintainer solves it, by fixing the dependency error(s) in his packages. Is it?

In the meantime, anyone who is using his PPA will be unable to upgrade their systems, do any security patches or install any software.

I will attempt to contact the guy and alert him to the problem. Hopefully this might speed things up a bit. Then we can mark the problem as truly solved.

I took the view that getting E17 working was not as important as being able to receive security updates and install other stuff, if I needed to.

Mr. Goose, thank you for pointing that out. I agree with your concerns. I confess I was a bit hesitant to mark it solved because it actually isn't yet. My hopes were that it would be solved with a proper update.

Needless to say that was easily remedied and we can wait until we're satisfied it is solved properly.

[Mr.Goose]

Well, I have just emailed Hannes Janetzek (the PPA maintainer) and alerted him to the issue. Judging by all the work he has done on his PPA, he seems a very hard-working and enthusiastic sort of chap. My guess is he will be on the case pretty soon.

Best wishes, G.

[Frogs Hair]

After trying repository packages and 3 different PPAs I decided my next E17 experience would come via Bodhi.

By all means use the PPA if you want but it is hard to get a really good experience running E17 on top of Ubuntu with Gnome 3 applications. I like E17 and trying as a stand alone desktop on Bohdi was far Superior to PPA experiences.

http://www.bodhilinux.com/