Bug 138427
Summary: | Update from Oct 28th 2004 for FC2 conflicts with released FC3 package | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Robert 'Bob' Jensen <bobjensen> |
Component: | libxml2 | Assignee: | Daniel Veillard <veillard> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | bobjensen, katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-30 15:19:34 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Robert 'Bob' Jensen
2004-11-09 05:56:51 UTC
"cause conflict" : how ??? Describe what is happening. This should not be a problem, i.e. this should not prevent the upgrade. Daniel The conflicts I found were post CD upgrade. tThe problems I found were with yum and up2date from the FC3 CD. The solution I came up with was to downgrade the installed packages to match the CD version. I am still asking "cause conflict", how did the problem show up ? what did break ? when ? In which circumstances ? During the update ? what message did you got ? Did the upgrade completed anyway ? In a nutshell what did *actually* happen, not the 2 lines about what you think happened please ! Daniel I.e. what is yum saying ? What is up2date saying ? How did you called them ? This should not break, you may get a warning that the installed version is older than the available one. This is not a problem. Only if they fail to update other packages then this is a bug and this should be fixed in yum or up2date ! Daniel Sorry for the incomplete info, I am new to this bug thing. My FC2 box was "up2date". I used the FC3 CDs to upgrade my system. This went fine from what I could tell. Post upgrade I attempted to use yum to update my machine when I found the problem. Below you will find the message from yum, a message close to this was reported when I attempted to use up2date, sorry I do not have the exact error. # yum update Traceback (most recent call last): File "/usr/bin/yum", line 6, in ? import yummain File "/usr/share/yum-cli/yummain.py", line 23, in ? import yum File "/usr/lib/python2.3/site-packages/yum/__init__.py", line 33, in ? import groups File "/usr/lib/python2.3/site-packages/yum/groups.py", line 3, in ? import comps File "/usr/lib/python2.3/site-packages/yum/comps.py", line 5, in ? import libxml2 File "/usr/lib/python2.3/site-packages/libxml2.py", line 1, in ? import libxml2mod ImportError: /usr/lib/python2.3/site-packages/libxml2mod.so: undefined symbol: xmlNewDocPI I originally reported this bug as a yum bug #138425. I was told in #fedora that it should have been reported here. thanks, can you report the output of rpm -q libxml2 libxml2-devel libxml2-python /usr/lib/python2.3/site-packages/libxml2mod.so comes from libxml2-python the only possibility of this arising is if libxml2 and libxml2-python rpms are not in sync. Daniel I have resolved the issue on my machine so currently all are 2.6.14-2. When I noticed this atleast libxml2-python and libxml2-devel were 2.6.15-2 I am not sure about libxml2. Since you're the only person reporting this, and that a number of people have now upgraded from Fedora Core 2 to Fedora Core 3, it seems a relatively rare hard to reproduce failure. Since you don't have the environment allowing to debug this further I think we won't be able to fix this problem. thanks, Daniel |