Hmm, it seems I misread the report because I thought that's what was happening,
I guess the strange ticket summary set the stage for strange ideas what will
follow.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2952#issuecomment-2003
Reopened #2952.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2952#event-12152413309
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mailing list
> the only reasonable course of action is erroring out.
Shall I open separate ticket?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2952#issuecomment-2003741467
You are receiving this because you are subscribed to this thread.
Messag
You're instructing rpm to both exclude and include a file. It possibly do both,
so the only reasonable course of action can be erroring out.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2952#issuecomment-2003646399
You are receiving
Closed #2952 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2952#event-12150341988
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint m
Given this .spec file:
~~~rpm-spec
Summary: summary
Name: newpackage
Version: 1
Release: 1%{?dist}
License: MIT
%description
%install
mkdir -p %{buildroot}%{_tmppath}
echo "foo" > %{buildroot}%{_tmppath}/f
%files
%exclude %{_tmppath}/f
%{_tmppath}/f
%changelog
* Tue Jan 16 2024 Vít Ondruch
-
