emerge -av klamav
These are the packages that would be merged, in order:
Calculating dependencies... done!
[blocks B ] >=kde-base/kdelibs-3.5.4-r2 (is blocking kde-base/kde-env-3-r4)
[ebuild N ] kde-base/kde-env-3-r4 0 kB
[ebuild N ] app-antivirus/klamav-0.38 USE="arts xinerama -debug" 0 kB
kde-env isn't needed with the new kdelibs. Why was klamav depending directly on kde-env to begin with, shouldn't that be an indirect through some kde component?
# grep -Rni kde-env /usr/portage/app-antivirus/klamav
Fixed now, I was able to emerge klamav.
The bug was not invalid, I think the problem existed in an eclass rather then the klamav ebuild. For example, '~kde-env-3' is still being listed as a dep on http://gentoo-portage.com/app-antivirus/klamav/Dep#ptabs though I think that will also resolve itself when that site refreshes its database.
At any rate, it's better now, and if it was an eclass rather than a local klamav ebuild problem, it means probably a lot of other packages got fixed simultaneously.
Oh I just don't get it, I don't see any changes to kde eclasses or klamav in the timeframe between when it failed and it now working. Does portage cache any dependency information?