I ran test cases using rpm-4.18.2 and found one test case failed:
```
...
383: rpm -e and verify conflicting files removed 1 FAILED (rpme.at:327)
...
```
I encountered this problem in 4.18.0, but it was too late to provide a
reproduction method, resulting in the
issue(https://github.com/rpm-software-management/rpm/issues/2376) being closed.
The steps to reproduce it are as follows:
```
[root@localhost SPECS]# cat conflicttest.spec
# avoid depending on rpm configuration
%define _datadir /usr/share
Name: conflict%{pkg}
Version: 1.0
Release: 1
Summary: Testing file conflict behavior
Group: Testing
License: GPL
BuildArch: noarch
%description
%{summary}
%install
mkdir -p $RPM_BUILD_ROOT/%{_datadir}
echo "%{filedata}" > $RPM_BUILD_ROOT/%{_datadir}/my.version
%files
%defattr(-,root,root,-)
%{?fileattr} %{_datadir}/my.version
```
1. rpmbuild -bb --quiet --define "pkg a" --define "filedata pkg-a"
conflicttest.spec
2. rpmbuild -bb --quiet --define "pkg b" --define "filedata pkg-b"
conflicttest.spec
3. rpm -U --ignoreos /root/rpmbuild/RPMS/noarch/conflicta-1.0-1.noarch.rpm
4. rpm -U --ignoreos --force
/root/rpmbuild/RPMS/noarch/conflictb-1.0-1.noarch.rpm
5. rpm -Vav --nogroup --nouser conflicta conflictb
I get the following results that do not meet expectations:
```
[root@localhost noarch]# rpm -Vav --nogroup --nouser conflicta conflictb
......... /usr/share/my.version
......... /usr/share/my.version (not installed)
```
According to the test cases, the expected results are as follows:
```
[root@localhost noarch]# rpm -Vav --nogroup --nouser conflicta conflictb
......... /usr/share/my.version (not installed)
......... /usr/share/my.version
```
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3242
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3...@github.com>_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
