Re: Dependency issue hwinfo/libx86emu

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

 



On Fri, Apr 8, 2022 at 2:23 AM Nick Howitt via epel-devel
<epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>
>
> On 08/04/2022 04:38, Carl George wrote:
> > On Thu, Apr 7, 2022 at 7:33 PM Gemneye via epel-devel
> > <epel-devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> >>
> >>>>
> >>>> Error: Package: hwinfo-21.68-1.el7.x86_64 (epel)
> >>>>             Requires: libx86emu.so.1()(64bit)
> >>>>             Removing: libx86emu-1.1-2.1.x86_64
> >>>> (@/libx86emu-1.1-2.1.x86_64)
> >>>>                 libx86emu.so.1()(64bit)
> >>>>             Updated By: libx86emu-3.5-1.el7.x86_64 (epel)
> >>>>                ~libx86emu.so.3()(64bit)
> >>>>   You could try using --skip-broken to work around the problem
> >>>>   You could try running: rpm -Va --nofiles --nodigest
> >>>>
> >>>> Any suggestions and help appreciated.
> >>>
> >>> Hello
> >>>
> >>>
> >>> You can install hwinfo if you either disable epel-testing or filter
> >>> out (yum --exclude) libx86emu-3.5-1.el7. This package was pushed to
> >>> epel-testing and indeed, hwinfo which depends on libx86emu would need
> >>> a rebuild against it.
> >>>
> >>>
> >>> wolfy
> >>>
> >>
> >> Thank you for the response.
> >>
> >> It looks like libx86emu-3.5-1.el7.x86_64 is in the main epel repository.
> >>    Using --disablerepo=epel-testing, nor disabling repo in
> >> /etc/yum.repos.d/epel-testing.repo caused the issue to go away.
> >>
> >> You are correct in that hwinfo can be installed by using
> >> --exclude=libx86emu, but is still looks like there is a packing issue??
> >> _______________________________________________
> >> 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 on the list, report it: https://pagure.io/fedora-infrastructure
> >
> > This just recently happened in EPEL8 too [0].  I've created a
> > corresponding bug for EPEL7 [1].  This incompatible soname bump in
> > libx86emu is not allowed by EPEL policy [2].  If an update like this
> > must happen for security reasons, it should follow the incompatible
> > upgrades policy [3], which includes discussion on this list and
> > announcements on epel-announce.  Obviously that's not what happened
> > here.  The quickest fix is to rebuild hwinfo against the new soname.
> > I did that for EPEL8 a few days ago, and just submitted the EPEL7 one
> > now.  Follow along in the bugzilla for future updates.
> >
> > [0] https://bugzilla.redhat.com/show_bug.cgi?id=2071639
> > [1] https://bugzilla.redhat.com/show_bug.cgi?id=2073238
> > [2] https://docs.fedoraproject.org/en-US/epel/epel-policy/
> > [3] https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/
> >
> Or, as a short term kludge, can you force the installation of both
> packages and then symlink libx86emu.so.1 to so.3?
> _______________________________________________
> 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 on the list, report it: https://pagure.io/fedora-infrastructure

That is awful advice.  Please don't tell people to do that.  When an
soname changes the library developer is explicitly stating that the
interfaces have changed.  You are gambling that the application using
the library isn't using any of the changed interfaces.

-- 
Carl George
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure




[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