Hi guys.
that most certainly should not be, right?
-> $ dnf list libknet1 Last metadata expiration check: 0:00:37 ago on Fri 09 Sep 2022 10:44:07 BST. Installed Packages libknet1.x86_64 1.24-2.el8 @ha Available Packages libknet1.i686 1.24-2.el8 ha libknet1.i686 1.24-2.el8 powertools
but in case it should then the problem is:
-> $ dnf update ... Error: Problem 1: package libknet1-compress-bzip2-plugin-1.24-3.el8.x86_64 requires libknet1(x86-64) = 1.22-1.el8, but none of the providers can be installed - cannot install both libknet1-1.22-1.el8.x86_64 and libknet1-1.24-2.el8.x86_64 - cannot install the best update candidate for package libknet1-compress-bzip2-plugin-1.24-2.el8.x86_64 - cannot install the best update candidate for package libknet1-1.24-2.el8.x86_64
many thanks, L.
On Fri, 9 Sept 2022 at 08:09, lejeczek via CentOS-devel < centos-devel@centos.org> wrote:
Hi guys.
that most certainly should not be, right?
-> $ dnf list libknet1 Last metadata expiration check: 0:00:37 ago on Fri 09 Sep 2022 10:44:07 BST. Installed Packages libknet1.x86_64 1.24-2.el8 @ha Available Packages libknet1.i686 1.24-2.el8 ha libknet1.i686 1.24-2.el8 powertools
but in case it should then the problem is:
-> $ dnf update ... Error: Problem 1: package libknet1-compress-bzip2-plugin-1.24-3.el8.x86_64 requires libknet1(x86-64) = 1.22-1.el8, but none of the providers can be installed
THe problem isn't that it is in two repos (that is ok since a user may have one or the other or both and the versions are the same)
The problem is that the plugin somehow requires a version which only existed when it was built versus its 'sister' package. I would expect a spec problem.
- cannot install both libknet1-1.22-1.el8.x86_64 and
libknet1-1.24-2.el8.x86_64
- cannot install the best update candidate for package
libknet1-compress-bzip2-plugin-1.24-2.el8.x86_64
- cannot install the best update candidate for package
libknet1-1.24-2.el8.x86_64
many thanks, L. _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Fri, Sep 9, 2022 at 8:40 AM Stephen Smoogen ssmoogen@redhat.com wrote:
On Fri, 9 Sept 2022 at 08:09, lejeczek via CentOS-devel centos-devel@centos.org wrote:
Hi guys.
that most certainly should not be, right?
-> $ dnf list libknet1 Last metadata expiration check: 0:00:37 ago on Fri 09 Sep 2022 10:44:07 BST. Installed Packages libknet1.x86_64 1.24-2.el8 @ha Available Packages libknet1.i686 1.24-2.el8 ha libknet1.i686 1.24-2.el8 powertools
but in case it should then the problem is:
-> $ dnf update ... Error: Problem 1: package libknet1-compress-bzip2-plugin-1.24-3.el8.x86_64 requires libknet1(x86-64) = 1.22-1.el8, but none of the providers can be installed
THe problem isn't that it is in two repos (that is ok since a user may have one or the other or both and the versions are the same)
The problem is that the plugin somehow requires a version which only existed when it was built versus its 'sister' package. I would expect a spec problem.
I don't see how that can happen. It's all built from a single SRPM (kronosnet). If you look at the Requires: in koji, you'll see it needs libknet1(x86-64) = 1.24-2.el8
https://koji.mbox.centos.org/koji/rpminfo?rpmID=465643
... very confusing.
josh
On Fri, 9 Sept 2022 at 09:14, Josh Boyer jwboyer@redhat.com wrote:
On Fri, Sep 9, 2022 at 8:40 AM Stephen Smoogen ssmoogen@redhat.com wrote:
On Fri, 9 Sept 2022 at 08:09, lejeczek via CentOS-devel <
centos-devel@centos.org> wrote:
Hi guys.
that most certainly should not be, right?
-> $ dnf list libknet1 Last metadata expiration check: 0:00:37 ago on Fri 09 Sep 2022 10:44:07
BST.
Installed Packages libknet1.x86_64 1.24-2.el8
@haAvailable Packages libknet1.i686 1.24-2.el8
halibknet1.i686 1.24-2.el8
powertoolsbut in case it should then the problem is:
-> $ dnf update ... Error: Problem 1: package libknet1-compress-bzip2-plugin-1.24-3.el8.x86_64
requires libknet1(x86-64) = 1.22-1.el8, but none of the providers can be installed
THe problem isn't that it is in two repos (that is ok since a user may
have one or the other or both and the versions are the same)
The problem is that the plugin somehow requires a version which only
existed when it was built versus its 'sister' package. I would expect a spec problem.
I don't see how that can happen. It's all built from a single SRPM (kronosnet). If you look at the Requires: in koji, you'll see it needs libknet1(x86-64) = 1.24-2.el8
https://koji.mbox.centos.org/koji/rpminfo?rpmID=465643
... very confusing.
The problem is not with CentOS Stream but with EPEL. The package with the problem is that the libknet1 built to have all the extra modules was built against the RHEL package and not the CentOS Stream ones. So it is not going to work. This package needs to be removed from epel/8 and instead be in epel/next/8
On Fri, Sep 9, 2022 at 9:24 AM Stephen Smoogen ssmoogen@redhat.com wrote:
On Fri, 9 Sept 2022 at 09:14, Josh Boyer jwboyer@redhat.com wrote:
On Fri, Sep 9, 2022 at 8:40 AM Stephen Smoogen ssmoogen@redhat.com wrote:
On Fri, 9 Sept 2022 at 08:09, lejeczek via CentOS-devel centos-devel@centos.org wrote:
Hi guys.
that most certainly should not be, right?
-> $ dnf list libknet1 Last metadata expiration check: 0:00:37 ago on Fri 09 Sep 2022 10:44:07 BST. Installed Packages libknet1.x86_64 1.24-2.el8 @ha Available Packages libknet1.i686 1.24-2.el8 ha libknet1.i686 1.24-2.el8 powertools
but in case it should then the problem is:
-> $ dnf update ... Error: Problem 1: package libknet1-compress-bzip2-plugin-1.24-3.el8.x86_64 requires libknet1(x86-64) = 1.22-1.el8, but none of the providers can be installed
THe problem isn't that it is in two repos (that is ok since a user may have one or the other or both and the versions are the same)
The problem is that the plugin somehow requires a version which only existed when it was built versus its 'sister' package. I would expect a spec problem.
I don't see how that can happen. It's all built from a single SRPM (kronosnet). If you look at the Requires: in koji, you'll see it needs libknet1(x86-64) = 1.24-2.el8
https://koji.mbox.centos.org/koji/rpminfo?rpmID=465643
... very confusing.
The problem is not with CentOS Stream but with EPEL. The package with the problem is that the libknet1 built to have all the extra modules was built against the RHEL package and not the CentOS Stream ones. So it is not going to work. This package needs to be removed from epel/8 and instead be in epel/next/8
Ah! Thanks for clearing it up.
josh
On Fri, 2022-09-09 at 09:24 -0400, Stephen Smoogen wrote:
The problem is not with CentOS Stream but with EPEL. The package with the problem is that the libknet1 built to have all the extra modules was built against the RHEL package and not the CentOS Stream ones. So it is not going to work. This package needs to be removed from epel/8 and instead be in epel/next/8
I put up https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2022-5a4e39b30a for epel8-next, but based on the discussion in the linked bug, I think the current one in epel8 is fine for RHEL 8 systems, just not for CentOS Stream ones, so we'll probably need both for a while.
Cheers Davide
-
Davide Cavalca -
Josh Boyer -
lejeczek -
Stephen Smoogen