Bug 1837360 - Breakage due to updated RPM backend
Summary: Breakage due to updated RPM backend
Keywords:
Status: CLOSED DUPLICATE of bug 1461313
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-19 10:50 UTC by Vít Ondruch
Modified: 2020-06-02 21:06 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-27 15:28:36 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
setroubleshoot log (751.96 KB, text/plain)
2020-05-19 10:50 UTC, Vít Ondruch 		no flags Details
View All

Description Vít Ondruch 2020-05-19 10:50:24 UTC 
Created attachment 1689841 [details]
setroubleshoot log

Description of problem:
Change in RPM backend breaks SELinux and ABRT issue handling and I am not sure what else. See the attached log.

Version-Release number of selected component (if applicable):
$ rpm -q rpm
rpm-4.15.90-0.git14971.12.fc33.x86_64

$ rpm -q setroubleshoot
setroubleshoot-3.3.23-1.fc33.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
setroubleshoot spits a lot of errors into log.

Expected results:
setroubleshoot/ABRT works without warnings.


Additional info:
Comment 1 Vít Ondruch 2020-05-19 10:54:03 UTC 
This might be just duplicate of bug 1461313, not sure
Comment 2 Panu Matilainen 2020-05-26 08:12:06 UTC 
AFAICS selinux-policy doesn't contain anything specific to BDB backend names, these should cover all backend formats:

/var/lib/rpm(/.*)?                      gen_context(system_u:object_r:rpm_var_lib_t,s0)
/var/lib/rpmrebuilddb.*(/.*)?  gen_context(system_u:object_r:rpm_var_lib_t,s0)

...so I think its just a dupe of 1461313.
Comment 3 Zdenek Pytela 2020-05-27 15:28:36 UTC 
It is a duplicate. See also bz#1824265 for some additional information to backend change.

*** This bug has been marked as a duplicate of bug 1461313 ***
Note You need to log in before you can comment on or make changes to this bug.