In line with the Mass Python 2 Package Removal [0], the following (sub)packages of sssd were marked for removal: * python2-sss * python2-sssdconfig According to our query, those (sub)packages only provide a Python 2 importable module. If this is not true, please tell us why, so we can fix our query. Please remove them from your package. As said in the change document, if there is no objection in a week, we will remove the package(s) as soon as we get to it. This change might not match your packaging style, so we'd prefer if you did the change. If you need more time, please let us know here. We hope this doesn't come to you as a surprise. If you want to know our motivation for this, please read the change document [0]. [0] https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal
sssd python2 bindings are used by freeIPA project sh# dnf repoquery --whatrequires python2-sss-murmur Last metadata expiration check: 0:11:54 ago on Mon 17 Sep 2018 07:45:05 PM CEST. python2-ipalib-0:4.7.0-4.fc30.noarch
This bug explicitly lists python2-sss and python2-sssdconfig, not python2-sss-murmur. See also https://fedoraproject.org/wiki/Changes/FreeIPA_Python_2_Removal
We will be dropping Python 2 subpackages on IPA side in F30 timeframe (FreeIPA 4.8 or 5.0 version, not decided yet). FreeIPA git master has already dropped full Python 2 support, so this should not be a big deal but please do not remove dependencies until we release that next FreeIPA version to Fedora. Overall, I think this bug is probably a bit too fast to file/fix in this particular case. Rawhide can certainly wait for a month or two until we coordinate upstream releases.
Is python2-sss or python2-sssdconfig a dependency of anything? If so, we might want to change our tooling. However, repoquery doesn't show a thing: dnf repoquery --repo=rawhide --whatrequires python2-sss / python2-sssdconfig
(In reply to Miro Hrončok from comment #4) > Is python2-sss or python2-sssdconfig a dependency of anything? If so, we > might want to change our tooling. > > However, repoquery doesn't show a thing: > > dnf repoquery --repo=rawhide --whatrequires python2-sss / > python2-sssdconfig It will be simpler to drop all python2 sub-packages together from autotools POV. Or is there any benefit for dropping it ASAP? IMHO this BZ should be renamed to drop python2 sub-packages and blocked by freeIPA BZ1629080
That sounds reasonable.
python2-ipalib is no more.
(In reply to Miro Hrončok from comment #7) > python2-ipalib is no more. yep, sh-4.4# dnf repoquery --whatrequires python2-libipa_hbac Last metadata expiration check: 0:12:18 ago on Sat 06 Oct 2018 08:59:36 PM CEST. sh-4.4# dnf repoquery --whatrequires python2-libsss_nss_idmap Last metadata expiration check: 0:12:30 ago on Sat 06 Oct 2018 08:59:36 PM CEST. sh-4.4# dnf repoquery --whatrequires python2-sss Last metadata expiration check: 0:12:42 ago on Sat 06 Oct 2018 08:59:36 PM CEST. sh-4.4# dnf repoquery --whatrequires python2-sss-murmur Last metadata expiration check: 0:12:55 ago on Sat 06 Oct 2018 08:59:36 PM CEST. sh-4.4# dnf repoquery --whatrequires python3-sss-murmur Last metadata expiration check: 0:13:01 ago on Sat 06 Oct 2018 08:59:36 PM CEST. python3-ipalib-0:4.7.0-5.fc30.noarch And this is fixed in upstream for quite a long.
You are assigned to this BZ. So could you fix it in rawhide?
Michal maintains Fedora these days.
Bump.
Should be fixed now in Rawhide.
This BZ broke update. Moving to assigned. sh# dnf update Last metadata expiration check: 0:19:45 ago on Mon 12 Nov 2018 11:18:33 PM CET. Dependencies resolved. Problem 1: cannot install both libipa_hbac-2.0.0-5.fc30.x86_64 and libipa_hbac-2.0.0-4.fc30.x86_64 - package python2-libipa_hbac-2.0.0-4.fc30.x86_64 requires libipa_hbac = 2.0.0-4.fc30, but none of the providers can be installed - cannot install the best update candidate for package libipa_hbac-2.0.0-4.fc30.x86_64 - problem with installed package python2-libipa_hbac-2.0.0-4.fc30.x86_64 Problem 2: package libsss_autofs-2.0.0-5.fc30.x86_64 conflicts with sssd-common < 2.0.0-5.fc30 provided by sssd-common-2.0.0-4.fc30.x86_64 - package python2-sss-2.0.0-4.fc30.x86_64 requires sssd-common = 2.0.0-4.fc30, but none of the providers can be installed - cannot install the best update candidate for package libsss_autofs-2.0.0-4.fc30.x86_64 - problem with installed package python2-sss-2.0.0-4.fc30.x86_64 Problem 3: cannot install both libsss_nss_idmap-2.0.0-5.fc30.x86_64 and libsss_nss_idmap-2.0.0-4.fc30.x86_64 - package python2-libsss_nss_idmap-2.0.0-4.fc30.x86_64 requires libsss_nss_idmap = 2.0.0-4.fc30, but none of the providers can be installed - cannot install the best update candidate for package libsss_nss_idmap-2.0.0-4.fc30.x86_64 sh# dnf update --best Last metadata expiration check: 0:20:39 ago on Mon 12 Nov 2018 11:18:33 PM CET. Error: Problem 1: cannot install both libipa_hbac-2.0.0-5.fc30.x86_64 and libipa_hbac-2.0.0-4.fc30.x86_64 - package python2-libipa_hbac-2.0.0-4.fc30.x86_64 requires libipa_hbac = 2.0.0-4.fc30, but none of the providers can be installed - cannot install the best update candidate for package libipa_hbac-2.0.0-4.fc30.x86_64 - problem with installed package python2-libipa_hbac-2.0.0-4.fc30.x86_64 Problem 2: package libsss_autofs-2.0.0-5.fc30.x86_64 conflicts with sssd-common < 2.0.0-5.fc30 provided by sssd-common-2.0.0-4.fc30.x86_64 - package python2-sss-2.0.0-4.fc30.x86_64 requires sssd-common = 2.0.0-4.fc30, but none of the providers can be installed - cannot install the best update candidate for package libsss_autofs-2.0.0-4.fc30.x86_64 - problem with installed package python2-sss-2.0.0-4.fc30.x86_64 Problem 3: cannot install both libsss_nss_idmap-2.0.0-5.fc30.x86_64 and libsss_nss_idmap-2.0.0-4.fc30.x86_64 - package python2-libsss_nss_idmap-2.0.0-4.fc30.x86_64 requires libsss_nss_idmap = 2.0.0-4.fc30, but none of the providers can be installed - cannot install the best update candidate for package libsss_nss_idmap-2.0.0-4.fc30.x86_64 - problem with installed package python2-libsss_nss_idmap-2.0.0-4.fc30.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages) - problem with installed package python2-libsss_nss_idmap-2.0.0-4.fc30.x86_64 ================================================================================ Package Arch Version Repository Size ================================================================================ Upgrading: python3-sss-murmur x86_64 2.0.0-5.fc30 rawhide 25 k Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): libipa_hbac x86_64 2.0.0-5.fc30 rawhide 42 k libsss_autofs x86_64 2.0.0-5.fc30 rawhide 44 k libsss_nss_idmap x86_64 2.0.0-5.fc30 rawhide 52 k Transaction Summary ================================================================================ Upgrade 1 Package Skip 3 Packages Total download size: 25 k Is this ok [y/N]: N Operation aborted.
I know there is dnf parameter --allowerasing. But it is not a solution; it is just a temporary workaround. And --allowerasing might not be acceptable in automatic updates.
The solution is to obsolete the removed packages. I do it in batches from https://src.fedoraproject.org/rpms/fedora-obsolete-packages/ - if you cannot wait for next batch, feel free to send a PR.
(In reply to Miro Hrončok from comment #15) > The solution is to obsolete the removed packages. > > I do it in batches from > https://src.fedoraproject.org/rpms/fedora-obsolete-packages/ - if you cannot > wait for next batch, feel free to send a PR. rawhide does not have bodhi and thus cannot chve combined updates. And because there are strict dependencies between sssd sub-packages then it have to be solved in sssd spec file. sh$ rpm -q --requires python2-sss | grep common sssd-common = 2.0.0-4.fc30 sh$ rpm -q python2-sss python2-sss-2.0.0-4.fc30.x86_64
There are not any python2 packages in sssd-2.0.0-6.fc30 and upgrade works well because of fedora-obsolete-packages.