[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: up2date aborted with pango.modules conflict
- From: "Chiu, PCM (Peter) " <P C M Chiu rl ac uk>
- To: "Chiu, PCM (Peter) " <P C M Chiu rl ac uk>, "'Discussion of Red Hat Enterprise Linux 3 (Taroon)'" <taroon-list redhat com>
- Cc:
- Subject: RE: up2date aborted with pango.modules conflict
- Date: Mon, 26 Jul 2004 09:02:12 +0100
Having just received an update from Bugzilla, I am somewhat disappointed
that despite of two updates, RHEL 3 x86_64 is unfortunately still not quite
a mature product for normal production or business purpose.
Attached is their response.
What |Removed |Added
----------------------------------------------------------------------------
QAContact| |jamisonm redhat com
Component|pango |up2date
AssignedTo|otaylor redhat com |alikins redhat com
CC| |otaylor redhat com
------- Additional Comments From otaylor redhat com 2004-07-24 11:56
------- It's a known issue that not all libraries parallel install between
x86_64 and i386 in RHEL3. Work has been done to fix this in develment
versions but the changes are quite substantial and thus potentially
dangerous. It is not yet decided when to introduce those changes into
a RHEL3 update.
I'm going to reassing this bug to up2date since it isn't clear to me why
up2date should be trying to pull in the i386 version of additional packages.
There may be some debug options you can add to get more information about
why it's pulling in the above packages.
-----Original Message-----
From: Chiu, PCM (Peter)
Sent: 23 July 2004 15:03
To: 'Discussion of Red Hat Enterprise Linux 3 (Taroon)'
Cc: Chiu, PCM (Peter)
Subject: RE: up2date aborted with pango.modules conflict
I logged this call a week ago to bugzilla, but no response.
I wonder what their average response time is?
Anyway, I reinstalled a new copy of RHEL-64 to a different partition. This
time, I managed to apply up2date, after removing a list of products by trial
and error.
During the up2date process, I have noticed some products such as samba are
automatically included to install for both i386 and x86_64.
Is that a fault or something intentional?
The end result is that I cannot get up2date to run automatically unless I
know which package to skip.
Peter
========================================================================
Fetching package list for channel: rhel-x86_64-as-3...
Fetching Obsoletes list for channel: rhel-x86_64-as-3...
Fetching rpm headers...
Name Version Rel
----------------------------------------------------------
gdb 6.0post 0.20040223.20
i386
krb5-libs 1.2.7 24
i386
laus 0.1 56RHEL3
x86_64
libpng 1.2.2 24
i386
libpng 1.2.2 24
x86_64
libpng10 1.0.13 14
x86_64
openoffice.org 1.1.0 16.7.EL
i386
openoffice.org-i18n 1.1.0 16.7.EL
i386
openoffice.org-libs 1.1.0 16.7.EL
i386
samba 3.0.4 6.3E
i386
samba 3.0.4 6.3E
x86_64
samba-client 3.0.4 6.3E
x86_64
samba-common 3.0.4 6.3E
x86_64
Testing package set / solving RPM inter-dependencies...
RPM package conflict error. The message was:
Test install failed because of package conflicts:
The following packages were added to your selection to satisfy dependencies:
Name Version Release
--------------------------------------------------------------
laus-libs 0.1 56RHEL3
laus-libs 0.1 56RHEL3
file /lib/liblaus.so.1.0.0 from install of laus-libs-0.1-56RHEL3 conflicts
with file from package laus-0.1-54RHEL3 file /lib/liblaussrv.so.0.0.0 from
install of laus-libs-0.1-56RHEL3 conflicts with file from package
laus-0.1-54RHEL3
-----Original Message-----
From: taroon-list-bounces redhat com [mailto:taroon-list-bounces redhat com]
On Behalf Of Chiu, PCM (Peter)
Sent: 16 July 2004 18:32
To: 'Discussion of Red Hat Enterprise Linux 3 (Taroon)'
Subject: RE: up2date aborted with pango.modules conflict
Could well be.
rpm -qa | grep -i pango
reveals pango-1.2.5-2.0 has been loaded.
Under /var/spool/up2date, then I found
pango-1.2.5-2.0.i386.hdr
but no rpm.
It appears that up2date somehow is trying to install the i386 version.
I have checked the file "/etc/pango/pango.modules" on the system,
and it is a x86-64 version, so that is what it should be.
It appears that some package requires pango (i386) during the up2date but I
cannot tell which.
I have logged a call to bugzilla.
-----Original Message-----
From: taroon-list-bounces redhat com [mailto:taroon-list-bounces redhat com]
On Behalf Of Garrick Staples
Sent: 16 July 2004 18:09
To: Discussion of Red Hat Enterprise Linux 3 (Taroon)
Subject: Re: up2date aborted with pango.modules conflict
We have just acquired a new dual opteron 248 and loaded in RHEL 3
(3.2.3-26).
After setting up the system, I tried to apply the latest updates from RHN,
but it fails with this error:
Test install failed because of package conflicts:
The following packages were added to your selection to satisfy
dependencies:
atk 1.2.4 3.0
glib2 2.2.3 2.0
gtk2 2.2.4 4.0
laus-libs 0.1 56RHEL3
laus-libs 0.1 56RHEL3
mozilla-nspr 1.4.2 3.0.2
mozilla-nss 1.4.2 3.0.2
pango 1.2.5 2.0
file /etc/pango/pango.modules from install of pango-1.2.5-2.0 conflicts with
file from package pango-1.2.5-2.0
It is rather odd as the two packages said to be in conflict are identical to
me.
I then tried it again with the -u --force option with up2date, but it fails
with the same error.
I have also tried removing the file pango.modules, no joy.
If I tried to remove the package pango, it complains a huge list of products
requires libpangoft2-1, libpangox etc.
--
Taroon-list mailing list
Taroon-list redhat com http://www.redhat.com/mailman/listinfo/taroon-list
--
Taroon-list mailing list
Taroon-list redhat com http://www.redhat.com/mailman/listinfo/taroon-list
--
Taroon-list mailing list
Taroon-list redhat com http://www.redhat.com/mailman/listinfo/taroon-list
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]