-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression: %autosetup complains about no patches in range #3230
Labels
Comments
ffesti
added a commit
to ffesti/rpm
that referenced
this issue
Aug 5, 2024
Ensure there isn't a warning created. Related: rpm-software-management#3230
ffesti
added a commit
to ffesti/rpm
that referenced
this issue
Aug 5, 2024
Add file and line number to the warning. Suppress the warning when called from %autosetup and offer -q to suppress the warning in general. Resolves: rpm-software-management#3230
pmatilai
pushed a commit
that referenced
this issue
Aug 6, 2024
Ensure there isn't a warning created. Related: #3230
pmatilai
pushed a commit
that referenced
this issue
Aug 6, 2024
Add file and line number to the warning. Suppress the warning when called from %autosetup and offer -q to suppress the warning in general. Resolves: #3230
dmnks
pushed a commit
to dmnks/rpm
that referenced
this issue
Aug 29, 2024
Ensure there isn't a warning created. Related: rpm-software-management#3230 (cherry picked from commit 6f08a20)
dmnks
pushed a commit
to dmnks/rpm
that referenced
this issue
Aug 29, 2024
Add file and line number to the warning. Suppress the warning when called from %autosetup and offer -q to suppress the warning in general. Resolves: rpm-software-management#3230 (cherry picked from commit 46b3e76)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PR #3189 (commit d94dbcc) added a new warning to
%autopatch
in the case no patches are in range, but this now causes%autosetup
to emit that message in a case where there aren't any patches to apply, which is a totally normal situation for%autosetup
.Also, the message added is really vague because there's no line number, passed arguments or such to help identify the cause in case there are many
%autopatch
invocations.The text was updated successfully, but these errors were encountered: