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 734542 - Cannot install httpd-devel.x86_64, cannot upgrade NetworkManager to el6_1.1
Summary: Cannot install httpd-devel.x86_64, cannot upgrade NetworkManager to el6_1.1
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: James Antill
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-30 17:50 UTC by nugulus
Modified: 2014-01-21 06:24 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-30 19:54:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description nugulus 2011-08-30 17:50:46 UTC 
Description of problem:
libz.so.1 is needed by libcurl-7.19.7-26.el6_1.2.i686
libz.so.1 is needed by nss-3.12.9-9.el6.i686
Please report this error in https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%206&component=yum
** Found 9 pre-existing rpmdb problem(s), 'yum check' output follows:
1:NetworkManager-gnome-0.8.1-5.el6_0.1.x86_64 has missing requires of NetworkManager = ('1', '0.8.1', '5.el6_0.1')
1:NetworkManager-gnome-0.8.1-5.el6_0.1.x86_64 has missing requires of NetworkManager-glib = ('1', '0.8.1', '5.el6_0.1')
libcurl-7.19.7-16.el6.i686 has missing requires of libz.so.1
libssh2-1.2.2-7.el6.i686 has missing requires of libz.so.1
libxml2-2.7.6-1.el6.i686 has missing requires of libz.so.1
nss-3.12.8-1.el6_0.i686 has missing requires of libz.so.1
openssl-1.0.0-4.el6_0.2.i686 has missing requires of libz.so.1
zlib-devel-1.2.3-25.el6.i686 has missing requires of libz.so.1
zlibrary-0.12.10-1.el6.i686 has missing requires of libz.so.1
Your transaction was saved, rerun it with: yum load-transaction /tmp/yum_save_tx-2011-08-30-12-277xFOtS.yumtx

Version-Release number of selected component (if applicable):
3.2.29-17.el6

How reproducible:
reproducible every time.

Steps to Reproduce:
1.yum upgrade networkmanager
2.
3.
  
Actual results:
networkmanager not upgrade

Expected results:
Apply available newer version of packages

Additional info:
Comment 2 James Antill 2011-08-30 19:54:23 UTC 
libz.so.1 is needed by libcurl-7.19.7-26.el6_1.2.i686
libz.so.1 is needed by nss-3.12.9-9.el6.i686
[...]
** Found 9 pre-existing rpmdb problem(s), 'yum check' output follows:
[...]
libcurl-7.19.7-16.el6.i686 has missing requires of libz.so.1


 As it says, there is a preexisting problem with the rpmdb. If you fix that it'll work.
Note You need to log in before you can comment on or make changes to this bug.