It doesn't make sense to me to worry about specifying the
correct arch list for optional packages. Optional packages are
optional by definition, so it seems fine to just specify them
and if they don't exist on the arch right now, oh well. This
way, if they do start building for the arch in future, they will
be picked up right away with no need to change comps.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We don't build or ship armhfp or ppc64 any more, so drop all
references to those arches from comps-f38 and update the
`check-missing` script.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
It would be nice to make 'package is listed in group, but does
not exist' a fatal error (at least optionally) for dnf etc, but
we can't really do that at present because it's *not* been a
fatal error for so long that our comps have tons of stale
entries for packages that no longer exist, and also entries that
aren't properly archified for packages which only exist on some
arches. This script pokes through the comps file for current
Rawhide and identifies all (I hope) pkgreqs which specify a
package that is not actually available in current Rawhide, per
arch.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Adam Williamson
Ian McInerney