Bug 2172654 - gnome-control-center: make gnome-bluetooth dependency weak
Summary: gnome-control-center: make gnome-bluetooth dependency weak
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-control-center
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-22 21:32 UTC by Dominik 'Rathann' Mierzejewski
Modified: 2023-03-12 00:15 UTC (History)
2 users (show)

Fixed In Version: gnome-control-center-44~rc-1.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-27 23:51:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dominik 'Rathann' Mierzejewski 2023-02-22 21:32:48 UTC
Description of problem:
It's not possible to uninstall gnome-bluetooth (and thus bluez and bluez-obexd) due to hard dependency in gnome-shell and gnome-control-center. If a machine doesn't have a Bluetooth interface, there's no point in running obexd and having those packages installed. Both gnome-shell and gnome-control-center work just fine without gnome-bluetooth. Please make it a weak dependency (Recommends: instead of Requires:).

Version-Release number of selected component (if applicable):
gnome-bluetooth-1:42.5-1.fc37.x86_64
gnome-control-center-43.2-1.fc37.x86_64
gnome-shell-43.3-1.fc37.x86_64

How reproducible:
Always

Steps to Reproduce:
1. rpm -e bluez bluez-obexd gnome-bluetooth

Actual results:
error: Failed dependencies:
	gnome-bluetooth(x86-64) >= 1:42~alpha is needed by (installed) gnome-control-center-43.2-1.fc37.x86_64
	gnome-bluetooth(x86-64) >= 1:42.3 is needed by (installed) gnome-shell-43.3-1.fc37.x86_64

Expected results:
Successful removal.

Comment 1 Pete Walter 2023-02-23 11:54:47 UTC
Can you do PRs please?

Comment 2 Dominik 'Rathann' Mierzejewski 2023-02-27 23:29:52 UTC
Done: https://src.fedoraproject.org/rpms/gnome-control-center/pull-request/15 .

How do you handle backports to released branches? Or is this a "only in rawhide/branched" type of change in your book?

Comment 3 Pete Walter 2023-02-27 23:51:05 UTC
Thanks! I merged it to F38, but I would leave F37 alone at this point in the release cycle.

Comment 4 Fedora Update System 2023-02-28 00:37:15 UTC
FEDORA-2023-9883976476 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-9883976476

Comment 5 Fedora Update System 2023-03-01 01:50:18 UTC
FEDORA-2023-9883976476 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-9883976476

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

Comment 6 Fedora Update System 2023-03-09 01:29:36 UTC
FEDORA-2023-32625456a1 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-32625456a1

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

Comment 7 Fedora Update System 2023-03-10 01:47:52 UTC
FEDORA-2023-32625456a1 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-32625456a1

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

Comment 8 Fedora Update System 2023-03-11 05:38:51 UTC
FEDORA-2023-32625456a1 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-32625456a1

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

Comment 9 Fedora Update System 2023-03-12 00:15:59 UTC
FEDORA-2023-32625456a1 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.