From: Don Zickus on
gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1117#note_5703...
CKI Gitlab commented:
Marcelo Ricardo Leitner <mleitner(a)redhat.com> commented via email:
```
>
https://gitlab.com/cki-project/kernel-
ark/-/merge_requests/1117#note_570213935
>
> > Anyway, the commands I used are: time find . -name "Makefile\*"
-exec
> grep '.o' {} ; > /tmp/don.list (3 seconds) for i in
`cat
> redhat/rhel_files/*.list.rhel redhat/fedora_files/*.list.fedora`;do
> mod="$(echo $i | sed 's/ko$/o/')"; grep -q $mod /tmp/don.list ||
echo
> "Bad module: $i"; done|wc -l
>
> I don't think that addresses the issue, I think the issue is when a
new
> module comes along with a dep on a module that was in extras,
and
moves
> the extras module back to kernel-modules. The only real way to
do
that
> is to diff the file lists of module every time and list anything
missing
> that was in the previous verison.
Or treat mod-extra.list (and others) as mandatory. If it's there, and
the module is not listed in the final file list, as in:
%{expand:%%files -f %{name}-%{?3:%{3}-}modules-extra.list
%{?3:%{3}-}modules-extra}\
it's a bug.
That said, the best place to handle it would be while building the
package.
That was my first thought until I wondered if every module in
modules-extra.list is applicable to every arch. Is it possible that
some of
those modules are not built for an arch or its variant?