You are not logged in.
keerthi ~ $ pacman -Q | grep pacman
pacman 3.1.3-1
pacman 3.1.2-1keerthi ~ $ pacman -Q | grep kernel26
kernel26 2.6.24.3-4
kernel26 2.6.24.3-3I tried force installing (with -f) pacman 3.1.3-1 and kernel26 2.6.24.3-3 (repo version). Pacman reports it upgraded successfully but duplicates appears when I query the packages. How do I deal with these?
* I only have core/extra/community enabled.
Last edited by keerthi (2008-03-14 02:31:10)
Offline
Nevermind. Fixed it.
Offline
For the record, how did you fix it? I'm as intrigued as another user with the same problem might be ![]()
And also, i'm actually very intrigued how you managed to get 2.6.24.3-4 on your system ![]()
flack 2.0.6: menu-driven BASH script to easily tag FLAC files (AUR)
knock-once 1.2: BASH script to easily create/send one-time sequences for knockd (forum/AUR)
Offline
kernel 2.6.24.3-4. I compiled it from source. I was hoping it would create a LOCALVERSION but the build upgraded the kernel I already had (2.6.24.3-3). I ended up with an unbootable system so I restored my / with an week-old backup. After restore, I found some of the packages duplicated - one I got from repos since my last backup and the other came from the restore process. LOL!
I had to manually delete the offending versions from /var/lib/pacman/local/
Lesson Learned: Remember to delete everything from / and then restore from backup to avoid ghost packages
Offline