Bug 1781864

Summary: libsecret-0.19.1-1 weak dependency on gnome-keyring installing X packages in minimal installs
Product: [Fedora] Fedora Reporter: louisgtwo
Component: libsecretAssignee: Kalev Lember <klember>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: debarshir, klember, stefw, thomas.moschny
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libsecret-0.20.2-2.fc32 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-08 02:53:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description louisgtwo 2019-12-10 18:09:08 UTC
libsecret weak dependency on gnome-keyring installs X libraries. Installing minimal fedora installs gnupg2 which has a weak dependency on pinentry. Pinentry requires libsecret-1.so.0()(64bit). Installing gnome-keyring installs a bunch of X libs that I do not want on a minimal fedora install.

Comment 1 Kalev Lember 2019-12-10 20:31:25 UTC
Can you turn off weak deps when installing the minimal system?

Comment 2 louisgtwo 2019-12-10 21:15:47 UTC
I install my servers with a usb stick. How do you turn off weak deps in anaconda?

Comment 3 Kalev Lember 2019-12-11 09:26:03 UTC
Not sure if it's possible in anaconda. I know it's possible to disable weak dependencies in kickstart.

See https://bugzilla.redhat.com/show_bug.cgi?id=1725412 for the background why we added the weak dependency.

Comment 4 louisgtwo 2019-12-11 14:29:07 UTC
Yes I created a kickstart file with --excludeWeakdeps and it worked well. But my point is users picking minimal install from anaconda expect the smallest install possible. Maybe this is an issue for anaconda and setting --excludeWeakdeps by default for minimal installs.

Comment 5 Kalev Lember 2019-12-11 20:15:17 UTC
Yes, not sure what the right fix would be.

Comment 6 Fedora Update System 2020-04-06 21:19:43 UTC
FEDORA-2020-bec4522056 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-bec4522056

Comment 7 Fedora Update System 2020-04-07 02:28:15 UTC
FEDORA-2020-bec4522056 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-bec4522056`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-bec4522056

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2020-04-08 02:53:46 UTC
FEDORA-2020-bec4522056 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.