Re: [CentOS-devel] libknet1- in more than one repo

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Fri, 9 Sept 2022 at 09:14, Josh Boyer <jwboyer@xxxxxxxxxx> wrote:
On Fri, Sep 9, 2022 at 8:40 AM Stephen Smoogen <ssmoogen@xxxxxxxxxx> wrote:
>
>
>
> On Fri, 9 Sept 2022 at 08:09, lejeczek via CentOS-devel <centos-devel@xxxxxxxxxx> 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
 

--
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux