This --force seems to do it perfectly, I'll take care. Thanks. Arch rules. Laurent 2012/1/4 Lars Madson <rwx700@xxxxxxxxx> > Well, the problem is actually caused by the /usr folder cause it's common > to the old and recent /opt /var. So the old feel unsync with this too > recent /usr folder and create conflict cause all the files are already > there. > > The /opt /var will be simply updated if I understand right as the pacman > database is in /var, isn't it? So the database is also old. > > The HDD is dead. I will rely only on the SSD till I get that second hard > drive box for laptop. I definitely hate cheap hdd external box, killed so > many. > > So I will use the --force just for this special occasion, so glad that > option exists. > Nothing has to be force with arch as it's so slick :P > > thank you > > > 2012/1/4 Leonid Isaev <lisaev@xxxxxxxxxxxx> > >> On Wed, 4 Jan 2012 20:23:35 +0100 >> Lars Madson <rwx700@xxxxxxxxx> wrote: >> >> > Hi, >> > >> > My system has two hard drive, one SSD with / and /home/user on two >> > partitions and a HDD mounted on /opt and /var. >> > >> > The HDD failed, and the system works with only the SSD as it was >> installed >> > like this and then extended to the HDD. >> > >> > Only 3 or 4 weeks of update make a difference between the content of >> /var >> > and /opt on the SSD and the HDD. >> > >> > Now I'm performing an upgrade of the whole system to get back to normal >> but >> > all files in /usr are making conflict as the /opt and /var are older and >> > trying to install files that are already there. >> > >> > So I could - but it seems really painful - rename all the conflicting >> files >> > (they are a lot), if anyone as an idea how to automatize this. Or maybe >> I >> > would love some kind of option in pacman that would overwrite or ignore >> > those conflicts, I know that's against how pacman is build so I'm asking >> > here. >> > >> > Hope I make sens. >> > >> > thx >> > Laurent >> >> You could use the -f option but I wonder if this is more troublesome and >> time-consuming than a simple reinstall. >> >> -- >> Leonid Isaev >> GnuPG key ID: 164B5A6D >> Key fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D >> > >
