[Yum-devel] Error bootstraping CentOS with Yum from Debian SID
James Antill
james at fedoraproject.org
Thu Mar 1 18:19:56 UTC 2012
On Thu, 2012-03-01 at 22:55 +0800, Thomas Goirand wrote:
> Hi,
>
> I am trying to update yum from version 3.2.25 to 3.2.29 in Debian SID,
> so that we have the latest before Wheezy is frozen.
Why 3.2.29? 3.4.x wasn't a major change, as the release announcement
said.
I also haven't done a 3.4.2, and it's been a while, so you might want
to look at the Fedora/RHEL "semi-releases" ... but even 3.4.1 should be
better.
> Using yum 3.2.29, I ran the attached script. FYI, RPM is in version
> 4.9.1.2-1+b1. It seems everything goes well, and I believe that I got
> CentOS installed, but then, at the end of the setup, I have the
> following stack dump:
>
> Traceback (most recent call last):
> File "/usr/bin/yum", line 29, in <module>
> yummain.user_main(sys.argv[1:], exit_code=True)
> File "/usr/share/yum-cli/yummain.py", line 262, in user_main
> errcode = main(args)
> File "/usr/share/yum-cli/yummain.py", line 198, in main
> return_code = base.doTransaction()
> File "/usr/share/yum-cli/cli.py", line 580, in doTransaction
> resultobject = self.runTransaction(cb=cb)
> File "/usr/lib/python2.7/dist-packages/yum/__init__.py", line 1488, in
> runTransaction
> self.rpmdb.dropCachedDataPostTransaction(list(self.tsInfo))
> File "/usr/lib/python2.7/dist-packages/yum/rpmsack.py", line 308, in
> dropCachedDataPostTransaction
> self._cached_rpmdb_mtime = os.path.getmtime(rpmdbfname)
> File "/usr/lib/python2.7/genericpath.py", line 54, in getmtime
> return os.stat(filename).st_mtime
> OSError: [Errno 2] No such file or directory:
> '/tmp/test-centos/var/lib/rpm/Packages'
>
> While it did work well when using yum 3.2.25 (which is current version
> in both Debian stable, testing and unstable).
>
> What is going wrong here? How can I fix?
It's possible this is a bug in chroot pathing, in that the above is
trying to stat /tmp/test-centos/tmp/test-centos/var/lib/rpm/Packages ...
but the code assumes it never fails.
There were a couple of bugs like that IIRC, but it's been a while.
Could be something else too ... after the above failure, does the above
path exist?
More information about the Yum-devel
mailing list