W dniu 4 października 2010 13:10 użytkownik Michał Piotrowski
<mkkp4x4(a)gmail.com> napisał:
>
> Apart from that it seems that everything went well.
>
I can not upgrade my system after this preupgrade update. Anyone else
has this problem?
https://bugzilla.redhat.com/show_bug.cgi?id=639960
BTW. I've got a few 'yum check' warnings caused by an old self build
packages
** Found 25 pre-existing rpmdb problem(s), 'yum check' output follows:
e2fsprogs-1.41.10-7.fc13.i686 has missing requires of libblkid.so.1
e2fsprogs-1.41.10-7.fc13.i686 has missing requires of libblkid.so.1(BLKID_1.0)
e2fsprogs-1.41.10-7.fc13.i686 has missing requires of libblkid.so.1(BLKID_2.15)
e2fsprogs-1.41.10-7.fc13.i686 has missing requires of libblkid.so.1(BLKID_2.17)
e2fsprogs-1.41.10-7.fc13.i686 has missing requires of libss.so.2
e2fsprogs-1.41.12-5.fc13.x86_64 is a duplicate with
e2fsprogs-1.41.10-7.fc13.x86_64
e2fsprogs-1.41.12-5.fc14.x86_64 is a duplicate with
e2fsprogs-1.41.12-5.fc13.x86_64
e2fsprogs-libs-1.41.12-5.fc13.x86_64 is a duplicate with
e2fsprogs-libs-1.41.10-7.fc13.x86_64
e2fsprogs-libs-1.41.12-5.fc14.i686 is a duplicate with
e2fsprogs-libs-1.41.12-5.fc13.x86_64
exim-4.72-1.fc13.x86_64 has missing requires of perl(:MODULE_COMPAT_5.10.1)
git-1.7.2.3-1.fc13.x86_64 has missing requires of perl-Git = ('0',
'1.7.2.3', '1.fc13')
git-1.7.3-1.fc13.x86_64 is a duplicate with git-1.7.2.3-1.fc13.x86_64
git-1.7.3-1.fc13.x86_64 has missing requires of perl-Git = ('0',
'1.7.3', '1.fc13')
git-1.7.3.rc2-1.fc13.x86_64 is a duplicate with git-1.7.3-1.fc13.x86_64
git-1.7.3.rc2-1.fc13.x86_64 has missing requires of perl-Git = ('0',
'1.7.3.rc2', '1.fc13')
git-email-1.7.3.rc2-1.fc13.x86_64 is a duplicate with
git-email-1.7.3-1.fc13.x86_64
git-gui-1.7.3.rc2-1.fc13.x86_64 is a duplicate with git-gui-1.7.3-1.fc13.x86_64
gitk-1.7.3.rc2-1.fc13.x86_64 is a duplicate with gitk-1.7.3-1.fc13.x86_64
gitweb-1.7.3-2.fc14.noarch has missing requires of git = ('0',
'1.7.3', '2.fc14')
perl-Git-1.7.3-2.fc14.noarch has missing requires of git = ('0',
'1.7.3', '2.fc14')
Is there any way to remove these warnings? These versions are no
longer in the system AFAICT.
This seems to support the idea (see other thread) that the upgrade
process was rebooted while still upgrading. :(
Thanks,
James