From 92d12d11a8075484372496a83d26e0f5f1638d41 Mon Sep 17 00:00:00 2001
From: Neil Hanlon <neil@shrug.pw>
Date: Jan 26 2023 19:08:59 +0000
Subject: Add note about conflict between rpmautospec and `fedpkg import`


---

diff --git a/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc b/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc
index 0081135..94da935 100644
--- a/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc
+++ b/modules/ROOT/pages/New_Package_Process_for_New_Contributors.adoc
@@ -230,14 +230,28 @@ Obviously, replace `PATH_TO_SRPM` with the full path
 to your approved SRPM,
 and `XXXXXX` with the package review bug number.
 
-If your package is using _autochangelog_, writing the bug number as specified
-will make the Fedora update system automatically close the bug when your package is
-submitted to Rawhide stable repository.
-
 This imports into, commits, and builds only the *main*
 (https://fedoraproject.org/wiki/Releases/Rawhide[Rawhide])
 branch.
 
+[NOTE]
+====
+If your package is using dynamic spec generation tools such as _autochangelog_
+or _autorelease_ from `rpmautospec`, there are a few things to consider.
+
+If using _autochangelog_, writing the bug number as specified
+will make the Fedora update system automatically close the bug when your package is
+submitted to Rawhide stable repository.
+
+Lastly, if any dynamic spec generation is used, you must use `fedpkg
+new-sources PATH_TO_SOURCES...` instead of `fedpkg import` to upload them or
+you may receive a message like
+....
+Could not execute import_srpm: SRPM was processed by rpmautospec 
+(specfile "your_package.spec" was analyzed)
+....
+====
+
 If the push fails with this kind of message:
 
 ....