From 0e9fe13141f88eee5c50c63a2045a30cc2855f8a Mon Sep 17 00:00:00 2001
From: Churchyard <Churchyard@fedoraproject.org/w>
Date: Jul 16 2018 16:57:05 +0000
Subject: avoid ambiguous python in example


---

diff --git a/Packaging:Guidelines.mw b/Packaging:Guidelines.mw
index 8f6c83e..68e4374 100644
--- a/Packaging:Guidelines.mw
+++ b/Packaging:Guidelines.mw
@@ -397,15 +397,15 @@ It is important that your package list all necessary build dependencies using th
 You MUST NOT use arched BuildRequires.  The arch ends up in the built SRPM but SRPMs need to be architecture independent.  For instance, if you did this:
 <pre>
 # Example of what *not* to do
-BuildRequires:	python%{?_isa} >= 2.7
+BuildRequires:	foo%{?_isa} >= 3.3
 </pre>
 
 Then the SRPM that is built in Fedora would have one of these Requirements depending on what builder the SRPM was created on:
 
 <pre>
-python(x86-32) >= 2.7
+foo(x86-32) >= 3.3
 # or
-python(x86-64) >= 2.7
+foo(x86-64) >= 3.3
 </pre>
 
 This would prevent yum-builddep or similar tools that use the SRPM's requirements from operating correctly.