Method to reproduce. emerge app-portage/elicense Run elicence # elicense # The following package(s) are using licenses which aren't covered by # ACCEPT_LICENSE="@FREE AdobeFlash-11.x AVASYS fairuse FraunhoferFDK freedist Google-TOS Oracle-BCLA-JavaSE PUEL dlj-1.1 googleearth linux-fw-redistributable teamspeak3" setting nor have entries in the package.license file: sys-kernel/gentoo-sources linux-firmware sys-kernel/linux-firmware linux-firmware no-source-code net-mail/checkpassword all-rights-reserved Notice sys-kernel/gentoo-sources linux-firmware Observe that sys-kernel/gentoo-sources-4.20.0 is installed. Rip it out emerge -c sys-kernel/gentoo-sources:4.20.0 Rerun elicense # elicense # The following package(s) are using licenses which aren't covered by # ACCEPT_LICENSE="@FREE AdobeFlash-11.x AVASYS fairuse FraunhoferFDK freedist Google-TOS Oracle-BCLA-JavaSE PUEL dlj-1.1 googleearth linux-fw-redistributable teamspeak3" setting nor have entries in the package.license file: sys-kernel/linux-firmware linux-firmware no-source-code net-mail/checkpassword all-rights-reserved Observe that sys-kernel/gentoo-sources linux-firmware has gone. Look in /boot and in /lib/modules and see that the binaries are still intact, so software is installed where the license is not accepted. Its a corner case as the kernel is special and this can only happen during the transition from the old ACCEPT_LICENSE default to the new one.
(In reply to Roy Bamford from comment #0) > Look in /boot and in /lib/modules and see that the binaries are still > intact, so software is installed where the license is not accepted. Kernel version 4.20.0 doesn't contain any non-free firmware, therefore you won't find any non-free binaries in /boot or /lib/modules. The problem is that the line "sys-kernel/gentoo-sources linux-firmware" isn't correct, in the first place. We were late in updating kernel-2.eclass to reflect upstream removal of the firmware tree (which happened in kernel 4.14 already), so gentoo-sources-4.20.0.ebuild was already gone when the eclass was fixed. Which cannot retroactively affect installed packages, of course. In any case, this is not a bug in the elicense tool.
I think this can be closed, per comment #1.
