Pacman

Welcome to the Pacman bug tracker. Please search the current bugs and feature requests before filing a new one! Use advanced search and select "Search in Comments".

* Please select the correct category and version.
* Write a descriptive summary, background info, and provide a reproducible test case whenever possible.
Tasklist

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
Task Type Bug Report
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture i686
Severity High
Priority Normal
Reported Version 3.0.4
Due in Version 3.1.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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

This task blocks these from closing
 FS#8109 - Pacman 3.1 Release Roadmap 
Closed by  Dan McGee (toofishes)
Wednesday, 14 November 2007, 22:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in GIT
Comment by Aaron Griffin (phrakture) - Wednesday, 23 May 2007, 17:07 GMT
Fixed in git, setting to "requires testing" until the feature is pushed out.
Comment by Dan McGee (toofishes) - Wednesday, 30 May 2007, 18:56 GMT
Can we close this? It is on the main pacman GIT tree.
Comment by Aaron Griffin (phrakture) - Wednesday, 30 May 2007, 20:29 GMT
I think so, can you test it and verify I'm not crazy?

mkdir /var/lib/pacman/extra/blahblahlolwtf

pacman -Ss xyz
Comment by Dan McGee (toofishes) - Wednesday, 30 May 2007, 20:42 GMT
Tested and confirmed that it works, although I found another issue in the process. :)
cd /var/lib/pacman/local/<package>/
move desc desc.old
pacman -Qi <package>

Look at those nice repeating errors.

Loading...