On Wednesday, November 2, 2016 12:08:50 PM CDT Pierre-Yves Chibon wrote:
> On Fri, Oct 28, 2016 at 01:24:39PM -0500, Dennis Gilmore wrote:
> > so anything that adds or excludes %{arm} armv7hl aarch64 should go to
> > fedora- arm-members@xxxxxxxxxxxxxxxxx
> > ppc64 ppc64p7 and ppc64le should go to
> > fedora-ppc-members@xxxxxxxxxxxxxxxxx
> > and snything excluding s390x should go to fedora-s390-
> > members@xxxxxxxxxxxxxxxxx
>
> The hook is now deployed and sending everything to me for now.
> I'll adjust it based on these suggestions.
>
> One thing I realized is that now is that there might be some false-positive,
> for example:
> ````
> The package rpms/R-DynDoc.git has added or updated either ExclusiveArch or
> ExcludesArch
> in commit(s):
> http://pkgs.fedoraproject.org/cgit/rpms/R-DynDoc.git/commit/?id=1186b2e7013a
> eaa3e88c5b36541a4b841f3b7dc3.
>
> Change:
> +ExclusiveArch: armv7, ppc, go_arch
> ````
>
> But all I did was adding 'go_arch', so two solutions:
> 1) warn arm and ppc folks again
> 2) make some of diff between:
> -ExclusiveArch: armv7, ppc
> +ExclusiveArch: armv7, ppc, go_arch
> and extract which arch got changed to warn only the groups of interest
>
> Thoughts?
>
> There are also changes such as:
> +ExclusiveArch: %{?go_arches:%{go_arches}}%{!?go_arches:%{ix86} x86_64
> %{arm}}
>
> How should these be treated? Warn the alternative-arch list? arm?
>
>
> Thanks,
> Pierre
likely in the case of something confusing we should default to generic. I am
not sure the best way to figure out the macros used in different exclude
lists. and they can and do change on a per release basis
DennisAttachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
