F17 -> F18 Laptop Problems

Dave Cross davorg at gmail.com
Mon Jan 21 18:48:22 UTC 2013


On 20 January 2013 21:39, Reindl Harald <h.reindl at thelounge.net> wrote:
>
>
> Am 20.01.2013 22:37, schrieb Sam Varshavchik:
>> Dave Cross writes:
>>
>>> $ rpm -qa | grep fc18
>>> nss-tools-3.14.1-3.fc18.x86_64
>>> java-1.7.0-openjdk-1.7.0.9-2.3.4.fc18.x86_64
>>> nss-sysinit-3.14.1-3.fc18.x86_64
>>> nss-3.14.1-3.fc18.x86_64
>>> xorg-x11-drv-intel-2.20.17-1.fc18.x86_64
>>> grubby-8.22-1.fc18.x86_64
>>>
>>> So it looks like the aborted FedUp upgrade managed to install six RPMs
>>> before bombing out.
>>
>> If that's all, I'm wondering why is your 'yum update' looking to F18's repo? fedora-release isn't one of these six.
>
> because even if you start "yum calean all; yum --releasever=18 whatever"
> your yum setup points to the F18 repos unless "rm -rf /var/cache/yum/*"
>
> it has cached the f18-urls and metadata and has no reasons to drop
> them until manually intervention

Aha. Yes, they're all in the _local repository. A quick 'sudo rm
/var/lib/yum/plugins/local/*fc18*' has, at least, returned the system
to Fedora 17.

Thanks,

Dave...

-- 
Dave Cross :: dave at dave.org.uk
http://dave.org.uk/
@davorg


More information about the users mailing list