RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1124792 - Cannot install lzo-devel after installing lzo-2.06-6.el7_0.2.x86_64
Summary: Cannot install lzo-devel after installing lzo-2.06-6.el7_0.2.x86_64
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lzo
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-30 10:26 UTC by Thomas Sondergaard
Modified: 2014-07-30 15:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-30 15:02:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Thomas Sondergaard 2014-07-30 10:26:55 UTC
"yum install lzo-devel" fails and tries to install i686 software. Problem started after lzo-2.06-6.el7_0.2.x86_64 was installed. Note that lzo-devel is still at 2.06-6.el7, not 2.06-6.el7_0.2 - I think that is the problem.

Commands demonstrating the problem:

[ ~]$ yum clean all
Loaded plugins: product-id, subscription-manager
Cleaning repos: atrpms epel merlinthp-el7-openconnect mi rhel-7-server-rpms rhel-ha-for-rhel-7-server-rpms rhel-rs-for-rhel-7-server-rpms temp-local
              : temp-local-server-optional vmware-tools
Cleaning up everything
[~]$ rpm -qa |grep lzo
lzo-2.06-6.el7_0.2.x86_64
lzo-minilzo-2.06-6.el7_0.2.x86_64
[ ~]$ yum install lzo-devel
Loaded plugins: product-id, subscription-manager
Resolving Dependencies
--> Running transaction check
---> Package lzo-devel.x86_64 0:2.06-6.el7 will be installed
--> Processing Dependency: lzo-minilzo = 2.06-6.el7 for package: lzo-devel-2.06-6.el7.x86_64
--> Processing Dependency: lzo = 2.06-6.el7 for package: lzo-devel-2.06-6.el7.x86_64
--> Running transaction check
---> Package lzo.i686 0:2.06-6.el7 will be installed
--> Processing Dependency: libc.so.6(GLIBC_2.4) for package: lzo-2.06-6.el7.i686
--> Processing Dependency: libc.so.6(GLIBC_2.1.3) for package: lzo-2.06-6.el7.i686
--> Processing Dependency: libc.so.6(GLIBC_2.0) for package: lzo-2.06-6.el7.i686
--> Processing Dependency: libc.so.6 for package: lzo-2.06-6.el7.i686
---> Package lzo-minilzo.i686 0:2.06-6.el7 will be installed
--> Running transaction check
---> Package glibc.i686 0:2.17-55.el7 will be installed
--> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-55.el7.i686
--> Processing Dependency: libfreebl3.so for package: glibc-2.17-55.el7.i686
--> Running transaction check
---> Package nss-softokn-freebl.i686 0:3.15.4-2.el7 will be installed
--> Finished Dependency Resolution
Error:  Multilib version problems found. This often means that the root
       cause is something else and multilib version checking is just
       pointing out that there is a problem. Eg.:
       
         1. You have an upgrade for lzo-minilzo which is missing some
            dependency that another package requires. Yum is trying to
            solve this by installing an older version of lzo-minilzo of the
            different architecture. If you exclude the bad architecture
            yum will tell you what the root cause is (which package
            requires what). You can try redoing the upgrade with
            --exclude lzo-minilzo.otherarch ... this should give you an error
            message showing the root cause of the problem.
       
         2. You have multiple architectures of lzo-minilzo installed, but
            yum can only see an upgrade for one of those architectures.
            If you don't want/need both architectures anymore then you
            can remove the one with the missing update and everything
            will work.
       
         3. You have duplicate versions of lzo-minilzo installed already.
            You can use "yum check" to get yum show these errors.
       
       ...you can also use --setopt=protected_multilib=false to remove
       this checking, however this is almost never the correct thing to
       do as something else is very likely to go wrong (often causing
       much more problems).
       
       Protected multilib versions: lzo-minilzo-2.06-6.el7.i686 != lzo-minilzo-2.06-6.el7_0.2.x86_64
Error: Protected multilib versions: lzo-2.06-6.el7.i686 != lzo-2.06-6.el7_0.2.x86_64

Comment 2 Jaroslav Škarvada 2014-07-30 14:45:04 UTC
Interesting, I can see lzo-devel-2.06-6.el7_0.2.x86_64.rpm in the "RHSA-2014:0861-06 Moderate: lzo security update" errata, and it should be included in the optional channel.

Do you enable optional channel and have you applied this errata? I will try to reproduce this locally.

Comment 3 Thomas Sondergaard 2014-07-30 14:59:26 UTC
(In reply to Jaroslav Škarvada from comment #2)
> Interesting, I can see lzo-devel-2.06-6.el7_0.2.x86_64.rpm in the
> "RHSA-2014:0861-06 Moderate: lzo security update" errata, and it should be
> included in the optional channel.
> 
> Do you enable optional channel and have you applied this errata? I will try
> to reproduce this locally.

No need. Your input helped. The following worked:

yum --enablerepo=rhel-7-server-optional-rpms install lzo-devel

Bad bug report.

Comment 4 Jaroslav Škarvada 2014-07-30 15:02:51 UTC
Thanks for info, closing.


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