QA Notice: ECLASS inherited illegally et al

[duderonomy]

Mod edit: Changed title from "ECLASS inherited illegally in sys-libs/gdbm-1.8" --kallamej

I do not yet know the ramifications of this error message...
Just throwing it out there as the beginning of a thread in case
other people experience a similar issue.

Code: Select all

17:35:19 (222.33 KB/s) - `/usr/portage/distfiles/gdbm-1.8.3.tar.gz' saved [228695/228695]

>>> md5 src_uri ;-) gdbm-1.8.3.tar.gz
>>> Unpacking source...
>>> Unpacking gdbm-1.8.3.tar.gz to /var/tmp/portage/gdbm-1.8.3-r1/work
 * Using GNU config files from /usr/share/libtool
  [ ok ]ting config.sub
  [ ok ]ting config.guess
 * Applying uClibc/libtool patches ...
  [ ok ]ng ${S}/configure...
>>> Source unpacked.


 ========== <snip> ==================



/bin/install -c -m 644 -o bin -g bin ./dbm.h \
        /var/tmp/portage/gdbm-1.8.3-r1/image//usr/include/gdbm/dbm.h
/bin/install -c -m 644 -o bin -g bin ./ndbm.h \
        /var/tmp/portage/gdbm-1.8.3-r1/image//usr/include/gdbm/ndbm.h
man:
gzipping man page: gdbm.3
info:
gzipping GNU info page: gdbm.info
prepallstrip:
strip: 
strip: 
   usr/lib/libgdbm.so.3.0.0
   usr/lib/libgdbm.so.2
   usr/lib/libgdbm_compat.so.3.0.0
making executable: /usr/lib/libgdbm.so.2
making executable: /usr/lib/libgdbm.so.3.0.0
making executable: /usr/lib/libgdbm_compat.so.3.0.0
>>> Completed installing into /var/tmp/portage/gdbm-1.8.3-r1/image/

>>> Merging sys-libs/gdbm-1.8.3-r1 to /
--- /usr/
--- /usr/lib/
>>> /usr/lib/libgdbm.a
>>> /usr/lib/libgdbm.so.3.0.0
>>> /usr/lib/libgdbm.la
>>> /usr/lib/libgdbm.so -> libgdbm.so.3.0.0
>>> /usr/lib/libgdbm_compat.a
>>> /usr/lib/libgdbm.so.2
>>> /usr/lib/libgdbm.so.3 -> libgdbm.so.3.0.0
>>> /usr/lib/libgdbm_compat.la
>>> /usr/lib/libgdbm_compat.so.3.0.0
--- /usr/share/
--- /usr/share/doc/
>>> /usr/share/doc/gdbm-1.8.3-r1/
>>> /usr/share/doc/gdbm-1.8.3-r1/README.gz
>>> /usr/share/doc/gdbm-1.8.3-r1/NEWS.gz
>>> /usr/share/doc/gdbm-1.8.3-r1/ChangeLog.gz
--- /usr/share/man/
--- /usr/share/man/man3/
>>> /usr/share/man/man3/gdbm.3.gz
--- /usr/share/info/
>>> /usr/share/info/gdbm.info.gz
--- /usr/include/
--- /usr/include/gdbm/
>>> /usr/include/gdbm/dbm.h
>>> /usr/include/gdbm/ndbm.h
>>> /usr/include/gdbm.h
>>> /usr/lib/libgdbm_compat.so.3 -> libgdbm_compat.so.3.0.0
>>> /usr/lib/libgdbm_compat.so -> libgdbm_compat.so.3.0.0
 * Please run revdep-rebuild --soname libgdbm.so.2
 * After that completes, it will be safe to remove the old
 * library (//usr/lib/libgdbm.so.2).
>>> Regenerating /etc/ld.so.cache...
 * Caching service dependencies...
>>> sys-libs/gdbm-1.8.3-r1 merged.

 sys-libs/gdbm
    selected: 1.8.0-r5
   protected: 1.8.3-r1
     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 sys-libs/gdbm-1.8.0-r5...
No package files given... Grabbing a set.

QA Notice: ECLASS 'gnuconfig' inherited illegally in sys-libs/gdbm-1.8.0-r5


QA Notice: ECLASS 'eutils' inherited illegally in sys-libs/gdbm-1.8.0-r5


QA Notice: ECLASS 'flag-o-matic' inherited illegally in sys-libs/gdbm-1.8.0-r5


QA Notice: ECLASS 'toolchain-funcs' inherited illegally in sys-libs/gdbm-1.8.0-r5

--- !mtime obj /usr/share/man/man3/gdbm.3.gz
--- !mtime obj /usr/share/info/gdbm.info.gz
<<<        obj /usr/share/doc/gdbm-1.8.0-r5/README.gz
<<<        obj /usr/share/doc/gdbm-1.8.0-r5/NEWS.gz
<<<        obj /usr/share/doc/gdbm-1.8.0-r5/ChangeLog.gz
<<<        obj /usr/lib/libgdbm.so.2.0.0
--- !sym   sym /usr/lib/libgdbm.so.2
--- !mtime obj /usr/lib/libgdbm.la
--- !mtime obj /usr/lib/libgdbm.a
--- !mtime obj /usr/include/gdbm/ndbm.h
--- !mtime obj /usr/include/gdbm/dbm.h
--- !mtime obj /usr/include/gdbm.h
<<<        dir /usr/share/doc/gdbm-1.8.0-r5
--- !empty dir /usr/share/man/man3
--- !empty dir /usr/share/man
--- !empty dir /usr/share/info
--- !empty dir /usr/share/doc
--- !empty dir /usr/share
--- !empty dir /usr/lib
--- !empty dir /usr/include/gdbm
--- !empty dir /usr/include
--- !empty dir /usr
--- !targe sym /usr/lib/libgdbm.so
>>> Regenerating /etc/ld.so.cache...
 * Caching service dependencies...
>>> Regenerating /etc/ld.so.cache...
 * Caching service dependencies...
>>> Auto-cleaning packages ...

[Genone]

In general you can simply ignore the 'QA Notice' stuff. It's a hint for developers to improve something in the ebuild (or a hint for portage devs that portage is playing stupid again).

[MickKi]

Whatever causes this notice must have been brought about by a recent change, because it started a couple of days ago.

[kallamej]

The reason you get these messages while uninstalling is that emerge stores all relevant environment information for a package, including the ebuild, in the package database upon installation. It is this ebuild that is used when you unmerge a package. Any changes made to live tree and portage itself is not, and shouldn't be, propagated to the old stored ebuild.

[MickKi]

Aha! It all makes sense now. I was getting ready to re-emerge portage thinking that I borked it somehow!

Thanks kallamej

[worldgnat]

Ok, so I'm installing gentoo, as in boot disk, and I get the same thing. Now with the little I knwo about gentoo, I can guess that unmerge on installation is a bad thing, right? well, I entered

Code: Select all

 emerge --emptytree -e system 

(ya, I know the --emptytree is redundent, but the I saw the word unmerge (not in an error message either), and I get those --!empty dir messages. Any hints? I'm a newb, and I've never had any luck with any console program what so ever, so as you can imagine I'm sort of on the edge of my seat after formatting my harddrive

-Peter