FS#7133 - DB scanning doesn't continue when a broken entry is found
Attached to Project:
Pacman
Opened by Mike Dill (Theoden) - Saturday, 12 May 2007, 01:06 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 14 November 2007, 22:53 GMT
Opened by Mike Dill (Theoden) - Saturday, 12 May 2007, 01:06 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 14 November 2007, 22:53 GMT
|
Details
Summary and Info:After upgrading to pacman-3.0.4xxx - one of
my systems failed on the command: pacman -Q kernel26ck
Output = Ringwraith ~]# pacman -Q kernel26ck error: package "kernel26ck" not found But - the ck kernel IS installed: Ringwraith ~]# uname -a Linux Ringwraith.atlantis 2.6.20-ck #1 SMP PREEMPT Sat Apr 21 15:02:32 IST 2007 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux When I ran pacman with --debug - the following error showed up in the output: %< cut debug: opening database 'local' debug: opening database from path '/var/lib/pacman/local/' debug: loading package cache for repository 'local' error: invalid name for database entry 'cedega-4.4' error: package "kernel26ck" not found debug: unregistering database 'local' >% end-cut When I renamed the 'cedega' entry to 'cedega-4.4-1 - and ran the pacman -Q kernel26ck again - it found the ck kernel. It appears that DB scanning doesn't continue when a broken entry is found. Steps to Reproduce: Rename any pkg entry in the DB to something similar to my 'cedega' entry above and do a pacman -Q search for a given package in the DB after the error entry. |
This task depends upon
Closed by Dan McGee (toofishes)
Wednesday, 14 November 2007, 22:53 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in GIT
Wednesday, 14 November 2007, 22:53 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in GIT
mkdir /var/lib/pacman/extra/blahblahlolwtf
pacman -Ss xyz
cd /var/lib/pacman/local/<package>/
move desc desc.old
pacman -Qi <package>
Look at those nice repeating errors.