Add the file (minus the leading slash) to the list of files to exclude in your /etc/pacman.conf file:
[options]
NoUpgrade = path/to/file
sarah31 wrote:well first just some advice ... after installing upgrade pacman first before you upgrade anything else.
Doesn't pacman automatically check if there is a new version of pacman now? (assuming you ran Sy first).
Dusty
probably but does the initially installed pacman do so?
anyway it seems clear to me that he is not properly synced if he is getting non existent package errors
]]>well first just some advice ... after installing upgrade pacman first before you upgrade anything else.
Doesn't pacman automatically check if there is a new version of pacman now? (assuming you ran Sy first).
Dusty
]]>even before this make sure that you have refreshed (resynced) with the archlinux package databases. your package does not exist errors are due to your local db not being synced with the current db.
before you do a full system upgrade as well make sure you hit the the arch homepage and read the news and announcement so that you are aware of any prolematic upgrades.
one of the packages that was upgrade was likely your kernel and one of the possible reasons you may not be able to reboot is that you may be using the lilo bootloader which requires you to run 'lilo'
after ANY kernel upgrade.
i doubt that the package removed is the cause of your system instability it is more likely your lack of familiarity with how to maintain an arch linux install.
]]>before this happens everything runs correctly :-/ what have i done wrong???
maybe it´s because pacman said something with conflict of xfree and a package beginning with v (vera or velra or something like that) and pacman asks me to remove this and i said yes :-)
ok thats it.....
what was my mistake and what should i do know? intall arch new or repair it (how to do)
greetings matto