Jump to content

2007.0-2007.1 upgrade - software repair


So_it_goes
 Share

Recommended Posts

Hi guys

 

Need help/ideas.

 

Machine 1 Running a 2007.1 which was ( not so successfull )upgraded from 2007.0, by changing sources,

Machine 2 Running a 'fresh' installed 2007.1

 

Machine 1:

Everything worked Ok for me until I made updates/upgrades 10th October,

this update/upgrade installed 3 libvorbis packages.

Then the machine crashed when I started a FAH folding job.

 

Machine 2 :

The 10th October update installed 4 libvorbis packages.

Works OK, no crashes, FAH folding running.

 

This made me search and I found that

on Machine 1 :

Had libvorbis----.2 installed and libvorbis---.3 locked

Machine 2 :

Had libvorbis----.3 installed

 

So this is one of the places where my upgrade failed.

So now I'm assuming, that I've got more of these mismatches.

Is there a way to find/solve these ?

I..e.

1) Detect mismatches/problems

2) Upgrade/update them

 

Thanks for any help

 

//

 

PS

A fresh install is the last resort.

DS

Link to comment
Share on other sites

Run this in a command prompt:

 

rpm -qa | sort | xargs -n 1 -t rpm -V &> /home/<username>/Desktop/rpm-Va.txt | exit

 

What it does is it scans your system for all RPMS installed, their associated files, and whether any of those files are missing, and creates a file on your desktop with this information. If any missing files are found, then reinstall the RPMS associated to the missing files.

 

In your case, I would also reinstall the RPM that borked manually. Use:

 

rpm -ivh <messed up rpm>.rpm --force

 

Without the --force at the end, you'll be informed that the package is already installed and stop.

Link to comment
Share on other sites

If you updated using sources, you have to make sure all config files were updated. So, as long as you have slocate or etc-update installed, you can do one of:

 

etc-update

 

as root (su first), and then replace the config files. Or:

 

slocate rpmnew

 

and then replace all .conf files with the .conf.rpmnew files. A little more painful because you're manually doing it, so etc-update is better in this instance. Then you will be fine, I know because I did upgrade from 2007.0 to 2007.1.

 

Also, make sure you install a newer kernel too, because by default you will stay with the 2007.0 kernel otherwise.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...