Yesterday I did a fresh install of F8 on a new machine. Then I attempted to upgrade it to rawhide.
I generally update by hand, doing about 4 chunks of packages to do the upgrade. I usually start by upgrading rpm and yum.
In current rawhide, yum (or yum utils) has a dependency on a particular python module, but it the python chunk isn't pulled in by the yum upgrade. After upgrading yum, yum won't run any more.
I downgraded the yum packages, did the upgrade, this time with rpm and yum going last. I was too grouchy to record the exact message.
So, the short moral, if doing an F8 to rawhide upgrade, leave rpm/yum for the last.
darrell
On Sun, 2008-01-20 at 12:06 -0800, darrell pfeifer wrote:
Yesterday I did a fresh install of F8 on a new machine. Then I attempted to upgrade it to rawhide.
I generally update by hand, doing about 4 chunks of packages to do the upgrade. I usually start by upgrading rpm and yum.
In current rawhide, yum (or yum utils) has a dependency on a particular python module, but it the python chunk isn't pulled in by the yum upgrade. After upgrading yum, yum won't run any more.
I downgraded the yum packages, did the upgrade, this time with rpm and yum going last. I was too grouchy to record the exact message.
So, the short moral, if doing an F8 to rawhide upgrade, leave rpm/yum for the last.
No dependencies have changed in yum for rawhide. It's the exact same version as that which is in f8.
-sv
On Jan 20, 2008 1:45 PM, seth vidal skvidal@fedoraproject.org wrote:
No dependencies have changed in yum for rawhide. It's the exact same version as that which is in f8.
Darn, I should have written down the message.
Is it possible that the rawhide yum uses something in the python libraries that isn't in the older F8 version of python?
darrell
2008/1/20 darrell pfeifer darrellpf@gmail.com:
On Jan 20, 2008 1:45 PM, seth vidal skvidal@fedoraproject.org wrote:
No dependencies have changed in yum for rawhide. It's the exact same version as that which is in f8.
Darn, I should have written down the message.
Is it possible that the rawhide yum uses something in the python libraries that isn't in the older F8 version of python?
darrell
This is an F8 updates-testing box.
13:17:31 |lordmorgul.CirithUngol:3| |43 files:2.9M@~| |0 jobs| -> rpm -q yum yum-3.2.8-2.fc8.noarch
14:13:45 |lordmorgul.CirithUngol:3| |43 files:2.9M@~| |0 jobs| -> cat /etc/fedora-release Fedora release 8 (Werewolf)
14:11:57 |root:0| |96 files:309M@tmp| |1 jobs| - yum --enablerepo development update yum updates-testing 100% |=========================| 2.3 kB 00:00 livna 100% |=========================| 2.1 kB 00:00 fedora 100% |=========================| 2.1 kB 00:00 development 100% |=========================| 2.2 kB 00:00 primary.sqlite.bz2 100% |=========================| 5.7 MB 00:11 updates 100% |=========================| 2.3 kB 00:00 fusion 100% |=========================| 951 B 00:00 Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package yum.noarch 0:3.2.8-2.fc9 set to be updated --> Finished Dependency Resolution
Dependencies Resolved
============================================================================= Package Arch Version Repository Size ============================================================================= Updating: yum noarch 3.2.8-2.fc9 development 509 k
Transaction Summary ============================================================================= Install 0 Package(s) Update 1 Package(s) Remove 0 Package(s)
Total download size: 509 k Is this ok [y/N]: y Downloading Packages: (1/1): yum-3.2.8-2.fc9.no 100% |=========================| 509 kB 00:01 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating : yum ######################### [1/2] Cleanup : yum ######################### [2/2] Jan 20 14:14:14 localhost avahi-daemon[2314]:last message repeated 4 times Jan 20 14:14:14 localhost yum: Updated: yum - 3.2.8-2.fc9.noarch
Updated: yum.noarch 0:3.2.8-2.fc9 Complete!
14:14:16 |root:0| |96 files:309M@tmp| |1 jobs| - yum list updates Updated Packages buildsys-build-rpmfusion.i686 23-1.lvn8 livna buildsys-build-rpmfusion-kerneldevpkgs-c 23-1.lvn8 livna buildsys-build-rpmfusion-kerneldevpkgs-n 23-1.lvn8 livna kmod-nvidia.i686 169.07-1.lvn8 livna xorg-x11-drv-nvidia.i386 169.07-4.lvn8 livna
14:14:31 |root:0| |96 files:309M@tmp| |1 jobs|
No problems with current devel yum on F8 updated (maybe on a base F8 install).
darrell pfeifer wrote:
In current rawhide, yum (or yum utils) has a dependency on a particular python module, but it the python chunk isn't pulled in by the yum upgrade. After upgrading yum, yum won't run any more.
I had a minimal F8 vmware VM, and yesterday intended to do a yum upgrade to get to rawhide. I installed fedora-release which gets me the fedora-development.repo and fedora-release files. I then tried a yum check-update, and saw the heap of updates. Next I yum update rpm* yum*, which seemed OK. After that yum didn't work anymore. rpm was still working, so I upgraded groups of packages at a time.
I managed to kill it in this process by running out of disk space while upgrading glibc, and others ;( and now she doesn't run commands or boot, I'm going to try again to get the error message.
DaveT.
David Timms wrote:
darrell pfeifer wrote:
In current rawhide, yum (or yum utils) has a dependency on a particular python module, but it the python chunk isn't pulled in by the yum upgrade. After upgrading yum, yum won't run any more.
I had a minimal F8 vmware VM, and yesterday intended to do a yum upgrade to get to rawhide. I installed fedora-release which gets me the fedora-development.repo and fedora-release files. I then tried a yum check-update, and saw the heap of updates. Next I yum update rpm* yum*, which seemed OK. After that yum didn't work anymore. rpm was still working, so I upgraded groups of packages at a time.
I managed to kill it in this process by running out of disk space while upgrading glibc, and others ;( and now she doesn't run commands or boot, I'm going to try again to get the error message.
DaveT.
Ok that definitely sounds like an issue that needs looked at deeper. Upgrading rpm and yum first off should not break yum right away! Doing just yum works fine for an updated machine as I showed, but maybe the base versions of rpm and yum for F8 have issues with that update.
Andrew Farris wrote:
David Timms wrote:
Next I yum update rpm* yum*, which seemed OK. After that yum didn't work anymore.
...
Ok that definitely sounds like an issue that needs looked at deeper. Upgrading rpm and yum first off should not break yum right away! Doing just yum works fine for an updated machine as I showed, but maybe the base versions of rpm and yum for F8 have issues with that update.
OK, made that install work again: $ rpm -qa yum* rpm* python* sql*|sort python-2.5.1-21.fc9 python-iniparse-0.2.3-3.fc9 python-libs-2.5.1-21.fc9 python-numeric-24.2-6.fc8 python-setuptools-0.6c7-2.fc8 python-urlgrabber-3.0.0-3.fc8 rpm-4.4.2.2-13.fc9 rpm-libs-4.4.2.2-13.fc9 rpm-python-4.4.2.2-13.fc9 rpm -qa|sort sqlite-3.5.4-2.fc9 yum-3.2.8-2.fc8 yum-metadata-parser-1.1.2-4.fc9 [davidt@localhost ~]$ yum --help There was a problem importing one of the Python modules required to run yum. The error leading to this problem was:
/usr/lib/python2.5/site-packages/_sqlitecache.so: undefined symbol: g_assertion_message_expr
Please install a package which provides this module, or verify that the module is installed correctly.
It's possible that the above module doesn't match the current version of Python, which is: 2.5.1 (r251:54863, Jan 17 2008, 11:02:11) [GCC 4.1.2 20071124 (Red Hat 4.1.2-36)]
If you cannot solve this problem yourself, please go to the yum faq at: http://wiki.linux.duke.edu/YumFaq
$ uname -a Linux localhost.localdomain 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 athlon i386 GNU/Linux
Is this a "silly" on my part / would a bugzilla be appreciated ?
DaveT
On Wed, 2008-01-23 at 00:24 +1100, David Timms wrote:
Andrew Farris wrote:
David Timms wrote:
Next I yum update rpm* yum*, which seemed OK. After that yum didn't work anymore.
...
Ok that definitely sounds like an issue that needs looked at deeper. Upgrading rpm and yum first off should not break yum right away! Doing just yum works fine for an updated machine as I showed, but maybe the base versions of rpm and yum for F8 have issues with that update.
OK, made that install work again: $ rpm -qa yum* rpm* python* sql*|sort python-2.5.1-21.fc9 python-iniparse-0.2.3-3.fc9 python-libs-2.5.1-21.fc9 python-numeric-24.2-6.fc8 python-setuptools-0.6c7-2.fc8 python-urlgrabber-3.0.0-3.fc8 rpm-4.4.2.2-13.fc9 rpm-libs-4.4.2.2-13.fc9 rpm-python-4.4.2.2-13.fc9 rpm -qa|sort sqlite-3.5.4-2.fc9 yum-3.2.8-2.fc8 yum-metadata-parser-1.1.2-4.fc9 [davidt@localhost ~]$ yum --help There was a problem importing one of the Python modules required to run yum. The error leading to this problem was:
/usr/lib/python2.5/site-packages/_sqlitecache.so: undefined symbol:g_assertion_message_expr
Please install a package which provides this module, or verify that the module is installed correctly.
It's possible that the above module doesn't match the current version of Python, which is: 2.5.1 (r251:54863, Jan 17 2008, 11:02:11) [GCC 4.1.2 20071124 (Red Hat 4.1.2-36)]
If you cannot solve this problem yourself, please go to the yum faq at: http://wiki.linux.duke.edu/YumFaq
$ uname -a Linux localhost.localdomain 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 athlon i386 GNU/Linux
Is this a "silly" on my part / would a bugzilla be appreciated ?
bugzilla would be appreciated, yes, thanks. -sv
David Timms wrote:
Andrew Farris wrote:
David Timms wrote:
Next I yum update rpm* yum*, which seemed OK. After that yum didn't work anymore.
...
Ok that definitely sounds like an issue that needs looked at deeper. Upgrading rpm and yum first off should not break yum right away! Doing just yum works fine for an updated machine as I showed, but maybe the base versions of rpm and yum for F8 have issues with that update.
OK, made that install work again: $ rpm -qa yum* rpm* python* sql*|sort python-2.5.1-21.fc9 python-iniparse-0.2.3-3.fc9 python-libs-2.5.1-21.fc9 python-numeric-24.2-6.fc8 python-setuptools-0.6c7-2.fc8 python-urlgrabber-3.0.0-3.fc8 rpm-4.4.2.2-13.fc9 rpm-libs-4.4.2.2-13.fc9 rpm-python-4.4.2.2-13.fc9 rpm -qa|sort sqlite-3.5.4-2.fc9 yum-3.2.8-2.fc8 yum-metadata-parser-1.1.2-4.fc9 [davidt@localhost ~]$ yum --help There was a problem importing one of the Python modules required to run yum. The error leading to this problem was:
/usr/lib/python2.5/site-packages/_sqlitecache.so: undefined symbol: g_assertion_message_expr
Please install a package which provides this module, or verify that the module is installed correctly.
It's possible that the above module doesn't match the current version of Python, which is: 2.5.1 (r251:54863, Jan 17 2008, 11:02:11) [GCC 4.1.2 20071124 (Red Hat 4.1.2-36)]
If you cannot solve this problem yourself, please go to the yum faq at: http://wiki.linux.duke.edu/YumFaq
$ uname -a Linux localhost.localdomain 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 athlon i386 GNU/Linux
Is this a "silly" on my part / would a bugzilla be appreciated ?
DaveT
Yes, python-urlgrabber should have been upgraded to fc9 as should the other python rpms. It looks like there could be a requires missing to get those to move up to the fc9 version. Did you see anything about that when updating python? Do you have the yumskipbroken plugin when doing that upgrade?
Andrew Farris wrote:
David Timms wrote:
/usr/lib/python2.5/site-packages/_sqlitecache.so: undefined symbol: g_assertion_message_expr
...
Yes, python-urlgrabber should have been upgraded to fc9
I don't have the .fc9 one at the moment, however: rpm -q --requires yum /usr/bin/python config(yum) = 3.2.8-2.fc9 python >= 2.4 python(abi) = 2.5 python-iniparse python-sqlite rpm >= 0:4.4.2 rpm-python rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 urlgrabber yum-metadata-parser >= 1.1.0
* note no version of urlgrabber mentioned so any should do.
[davidt@localhost ~]$ rpm -q --whatprovides urlgrabber python-urlgrabber-3.0.0-3.fc8 * I have one installed.
as should the other python rpms.
python and python-libs are part of python itself. The others are independent developments, with their own versions.
It looks like there could be a requires missing to get those to move up to the fc9 version.
I might be getting this wrong; the requires is trying to guarantee the packages work with each other, by requiring stuff provided by other packages, and specifying versions, if a specific version is required. I don't think it is necessary to have all packages with .fc9. for things to work normally. In any case, a later yum update would notice the things that have updates, and update them.
Did you see anything about that when updating python?
no.
Do you have the yumskipbroken plugin when doing that upgrade?
no. yum-skip-broken is not installed.
DaveT.
On Wed, 2008-01-23 at 00:24 +1100, David Timms wrote:
Andrew Farris wrote:
David Timms wrote:
Next I yum update rpm* yum*, which seemed OK. After that yum didn't work anymore.
...
Ok that definitely sounds like an issue that needs looked at deeper. Upgrading rpm and yum first off should not break yum right away! Doing just yum works fine for an updated machine as I showed, but maybe the base versions of rpm and yum for F8 have issues with that update.
OK, made that install work again: $ rpm -qa yum* rpm* python* sql*|sort python-2.5.1-21.fc9 python-iniparse-0.2.3-3.fc9 python-libs-2.5.1-21.fc9 python-numeric-24.2-6.fc8 python-setuptools-0.6c7-2.fc8 python-urlgrabber-3.0.0-3.fc8 rpm-4.4.2.2-13.fc9 rpm-libs-4.4.2.2-13.fc9 rpm-python-4.4.2.2-13.fc9 rpm -qa|sort sqlite-3.5.4-2.fc9 yum-3.2.8-2.fc8 yum-metadata-parser-1.1.2-4.fc9 [davidt@localhost ~]$ yum --help There was a problem importing one of the Python modules required to run yum. The error leading to this problem was:
/usr/lib/python2.5/site-packages/_sqlitecache.so: undefined symbol:g_assertion_message_expr
Please install a package which provides this module, or verify that the module is installed correctly.
It's possible that the above module doesn't match the current version of Python, which is: 2.5.1 (r251:54863, Jan 17 2008, 11:02:11) [GCC 4.1.2 20071124 (Red Hat 4.1.2-36)]
If you cannot solve this problem yourself, please go to the yum faq at: http://wiki.linux.duke.edu/YumFaq
$ uname -a Linux localhost.localdomain 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 athlon i386 GNU/Linux
Is this a "silly" on my part / would a bugzilla be appreciated ?
remove yum-metadata-parser via rpm -e, please
and then try running yum.
if yum works then yum install yum-metadata-parser and tell me if it still balks.
-sv
On Tue, 2008-01-22 at 08:49 -0500, seth vidal wrote:
remove yum-metadata-parser via rpm -e, please
and then try running yum.
if yum works then yum install yum-metadata-parser and tell me if it still balks.
I rebuild yum-metadata-parser into rawhide. Nothing changed in it - just a rebuild - let's see if that makes things better.
-sv
seth vidal wrote:
On Tue, 2008-01-22 at 08:49 -0500, seth vidal wrote: I rebuild yum-metadata-parser into rawhide. Nothing changed in it - just a rebuild - let's see if that makes things better.
actions and workaround at: https://bugzilla.redhat.com/show_bug.cgi?id=428847
DaveT.
seth vidal wrote:
On Wed, 2008-01-23 at 00:24 +1100, David Timms wrote:
$ rpm -qa yum* rpm* python* sql*|sort yum-3.2.8-2.fc8
* this was .fc8. because I tried downgrading to see if yum would work again. current: yum-3.2.8-2.fc9
yum-metadata-parser-1.1.2-4.fc9 [davidt@localhost ~]$ yum --help
...
/usr/lib/python2.5/site-packages/_sqlitecache.so: undefined symbol:g_assertion_message_expr
remove yum-metadata-parser via rpm -e, please
# rpm -e yum-metadata-parser error: Failed dependencies: yum-metadata-parser >= 1.1.0 is needed by (installed) yum-3.2.8-2.fc9.noarch # rpm -e yum-metadata-parser --nodeps
and then try running yum.
# yum update There was a problem importing one of the Python modules required to run yum. The error leading to this problem was:
No module named sqlitecachec
Please install a package which provides this module, or verify that the module is installed correctly.
It's possible that the above module doesn't match the current version of Python, which is: 2.5.1 (r251:54863, Jan 17 2008, 11:02:11) [GCC 4.1.2 20071124 (Red Hat 4.1.2-36)]
* the module missing changed, but no go.
if yum works then yum install yum-metadata-parser and tell me if it still balks.
else: rpm -Uvh yum-metadata-parser-1.1.2-4.fc9.i386.rpm Preparing... ########################################### [100%] 1:yum-metadata-parser ########################################### [100%] [root@localhost packages]# yum There was a problem importing one of the Python modules required to run yum. The error leading to this problem was:
/usr/lib/python2.5/site-packages/_sqlitecache.so: undefined symbol: g_assertion_message_expr
* back to original message
Will install the newer -metadata-parser when it becomes visible...
DaveT.
David Timms wrote:
seth vidal wrote:
On Wed, 2008-01-23 at 00:24 +1100, David Timms wrote:
$ rpm -qa yum* rpm* python* sql*|sort yum-3.2.8-2.fc8
- this was .fc8. because I tried downgrading to see if yum would work
again. current: yum-3.2.8-2.fc9
yum-metadata-parser-1.1.2-4.fc9 [davidt@localhost ~]$ yum --help
...
/usr/lib/python2.5/site-packages/_sqlitecache.so: undefinedsymbol: g_assertion_message_expr
remove yum-metadata-parser via rpm -e, please
# rpm -e yum-metadata-parser error: Failed dependencies: yum-metadata-parser >= 1.1.0 is needed by (installed) yum-3.2.8-2.fc9.noarch # rpm -e yum-metadata-parser --nodeps
and then try running yum.
# yum update There was a problem importing one of the Python modules required to run yum. The error leading to this problem was:
No module named sqlitecachec
Please install a package which provides this module, or verify that the module is installed correctly.
It's possible that the above module doesn't match the current version of Python, which is: 2.5.1 (r251:54863, Jan 17 2008, 11:02:11) [GCC 4.1.2 20071124 (Red Hat 4.1.2-36)]
- the module missing changed, but no go.
if yum works then yum install yum-metadata-parser and tell me if it still balks.
else: rpm -Uvh yum-metadata-parser-1.1.2-4.fc9.i386.rpm Preparing... ########################################### [100%] 1:yum-metadata-parser ########################################### [100%] [root@localhost packages]# yum There was a problem importing one of the Python modules required to run yum. The error leading to this problem was:
/usr/lib/python2.5/site-packages/_sqlitecache.so: undefined symbol: g_assertion_message_expr
- back to original message
Will install the newer -metadata-parser when it becomes visible...
Does updating glib2 to the version in Rawhide help?
Paul.
-
Andrew Farris -
darrell pfeifer -
Development discussions related to Fedora -
Paul Howarth -
Seth Vidal