Bug 2225231

Summary:	389-ds-base "ships" bash-completion outside of rpm
Product:	[Fedora] Fedora	Reporter:	Jan Pazdziora <jpazdziora>
Component:	389-ds-base	Assignee:	mreynolds
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	39	CC:	abokovoy, mreynolds, spichugi, tbordaz, vashirov
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-16 08:39:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Pazdziora 2023-07-24 16:43:33 UTC

When 389-ds-base gets installed, it creates a bunch of files in /usr/share/bash-completion/completions/ that rpm database does not know about.


Reproducible: Always

Steps to Reproduce:

1. cd /usr/share/bash-completion/completions/
2. rpm -qf * | sort -u
3. dnf install -y 389-ds-base
4. rpm -qf * | sort -u

Actual Results:  

Before that dnf install -y 389-ds-base:

dnf5-5.1.0-1.fc39.x86_64
glib2-2.77.0-7.fc39.x86_64
p11-kit-0.24.1-6.fc38.x86_64
p11-kit-trust-0.24.1-6.fc38.x86_64
util-linux-core-2.39.1-2.fc39.x86_64

After that dnf install -y 389-ds-base:

dnf5-5.1.0-1.fc39.x86_64
dracut-059-8.fc39.x86_64
file /usr/share/bash-completion/completions/ds-replcheck is not owned by any package
file /usr/share/bash-completion/completions/dsconf is not owned by any package
file /usr/share/bash-completion/completions/dscreate is not owned by any package
file /usr/share/bash-completion/completions/dsctl is not owned by any package
file /usr/share/bash-completion/completions/dsidm is not owned by any package
glib2-2.77.0-7.fc39.x86_64
grub2-tools-2.06-95.fc39.x86_64
iproute-6.4.0-1.fc39.x86_64
kmod-30-5.fc39.x86_64
p11-kit-0.24.1-6.fc38.x86_64
p11-kit-trust-0.24.1-6.fc38.x86_64
policycoreutils-3.5-4.fc39.x86_64
policycoreutils-python-utils-3.5-4.fc39.noarch
systemd-254~rc2-4.fc39.x86_64
systemd-networkd-254~rc2-4.fc39.x86_64
systemd-resolved-254~rc2-4.fc39.x86_64
systemd-udev-254~rc2-4.fc39.x86_64
tpm2-tools-5.5-3.fc39.x86_64
util-linux-2.39.1-2.fc39.x86_64
util-linux-core-2.39.1-2.fc39.x86_64



Expected Results:  

Any file that lands in /usr/share/bash-completion/completions/ should have clear ownership via the rpm database. IOW, files created in package build time and declared as such in %files in the .spec file.



I've started to observe this behaviour with 389-ds-base-2.4.2-3.fc39.x86_64.

Comment 1 Fedora Release Engineering 2023-08-16 08:13:29 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 2 Viktor Ashirov 2023-08-16 08:39:58 UTC

This was fixed in https://bodhi.fedoraproject.org/updates/FEDORA-2023-9133b9b669

# rpm -qf /usr/share/bash-completion/completions/* | sort -u
389-ds-base-2.4.3-1.fc39.x86_64
bash-completion-2.11-12.fc39.noarch
btrfs-progs-6.3.2-3.fc39.x86_64
cloud-init-23.2.1-1.fc39.noarch
dnf-4.16.2-2.fc39.noarch
dracut-059-12.fc39.x86_64
firewalld-2.0.0-5.fc39.noarch
fwupd-1.9.3-1.fc39.x86_64
git-core-2.41.0-2.fc39.x86_64
glib2-2.77.2-1.fc39.x86_64
grub2-tools-2.06-95.fc39.x86_64
iproute-6.4.0-2.fc39.x86_64
kmod-30-6.fc39.x86_64
mokutil-0.6.0-7.fc39.x86_64
NetworkManager-1.44.0-1.fc39.x86_64
p11-kit-0.25.0-2.fc39.x86_64
p11-kit-trust-0.25.0-2.fc39.x86_64
policycoreutils-3.5-7.fc39.x86_64
policycoreutils-python-utils-3.5-7.fc39.noarch
python3-lib389-2.4.3-1.fc39.noarch
systemd-254.1-2.fc39.x86_64
systemd-resolved-254.1-2.fc39.x86_64
systemd-udev-254.1-2.fc39.x86_64
udisks2-2.10.0-2.fc39.x86_64
util-linux-2.39.1-3.fc39.x86_64
util-linux-core-2.39.1-3.fc39.x86_64

Closing as CURRENTRELEASE