Cannot unmerge due to missing eclass

mmontg1 · Tux's lil' helper Joined: 21 Jun 2002 Posts: 129

Mod edit: Changed title from package specific to problem specific. --kallamej

raid kdelibs # emerge -c kdelibs

kde-base/kdelibs
selected: 3.1
protected: 2.2.2a 3.0.4 3.1.5
omitted: none

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.

>>> Waiting 5 seconds before starting...
>>> (Control-C to abort)...
>>> Unmerging in: 5 4 3 2 1
>>> Unmerging kde-base/kdelibs-3.1...
No package files given... Grabbing a set.
Lockfile removed: /var/db/pkg/kde-base/kdelibs-3.1.portage_lockfile
Lockfile removed: /var/db/pkg/kde-base/kdelibs-3.1.portage_lockfile
/usr/sbin/ebuild.sh: /usr/portage/eclass/kde.org.eclass: No such file or directory

!!! ERROR: kde-base/kdelibs-3.1 failed.
!!! Function inherit, Line 83, Exitcode 1
!!! died sourcing /usr/portage/eclass/kde.org.eclass in inherit()

!!! FAILED prerm: 1
raid kdelibs #

Any ideas on this... I searched the forums, and am kinda stuck.

Thanks a ton guys.

Carlo · Developer Joined: 12 Aug 2002 Posts: 3356

-c is not -C

Carlo
_________________
Please make sure that you have searched for an answer to a question after reading all the relevant docs.

mmontg1 · Tux's lil' helper Joined: 21 Jun 2002 Posts: 129

This was first noticed when portage tries to auto clean this package. -C gives the error message also... Thanks for the update though

Anybody else got any ideas on this one?

spitzwegerich · Posted: Sat Feb 07, 2004 12:50 pm Post subject:

I have the same problem.

The first line of code in kdelibs-3.1-r2.ebuild is

spitzwegerich · Posted: Sat Feb 07, 2004 12:54 pm Post subject:

I changed the line in the kdelibs ebuild to

Gigantopithicus · n00b Joined: 05 Aug 2002 Posts: 17 Location: Chicago, IL

I also had the same problem. However, I did not find the inherit statement in any of the kdelib ebuilds that contained kde.org. So, as a quick fix, I symlinked them as such:

ln -s /usr/portage/eclass/kde.eclass /usr/portage/eclass/kde.org.eclass

... worked fine.

Carlo · Developer Joined: 12 Aug 2002 Posts: 3356

Thanks for pointing me to this topic again!

edit: Portage doesn't keep up with eclasses, which do not exist anymore. This can happen, because Portage doesn't reflect the removal of eclasses in already installed ebuilds.

There are three alternative ways to fix this:
1. grab the old eclass from cvs and put it in /usr/portage/eclass, before unmerging
2. edit the saved ebuild in /var/db/pkg/<foo>/<bar>
3. remove the files installed by the ebuild by hand

The first alternative is the best of course.

:arrow:

Bug 46223

Carlo
_________________
Please make sure that you have searched for an answer to a question after reading all the relevant docs.

joehni · Apprentice Joined: 27 Jul 2003 Posts: 175

Just for the records: One suggestion to deal with the problem was to create the missing eclass file with touch. I had the problem with package app-i18n/kde-i18n-de that referenced removed kde-i18n.eclass. After creating the empty file, I was able to unmerge the package - at least emerge told me, that it had successfully removed it. Unfortunately I had to detect later, that the package was still referenced in my system. Only after restoring the kde-i18n.eclass with the latest version from CVS enabled emerge to unmerge kde-i18n-de in a permanent way.