[pacman-dev] [PATCH] Fix bug 9395 by allowing pacman to remove unresolvable packages from a transaction

Bryan Ischo bji-keyword-pacman.3644cb at www.ischo.com
Tue Jan 13 05:07:29 EST 2009

OK, in my own repository I have fixed the bug that I realized while 
writing my description of the is_needed() function in a previous email, 
and also have committed an additional 2 test cases which exercise some 
of the bugs that would have occurred had I not fixed issues pointed out 
to me on this list.

I'm ready to send my patches as 2 patches:

- One with everything except the removal of the "would you like to not 
ignore this package that you put in your IgnorePkg/IgnoreGroup list" dialog
- One to subsequently remove said dialog

Is there anything that would prevent these patches from being accepted?

By the way, discovering the pactest stuff was a very pleasant surprise.  
I didn't expect such a nice testing facility to be present, I don't know 
why, I guess because even commercial codebases I have worked on often 
don't have good testing facilities ... pactest is super awesome.  One 
thing that would be nice would be a way to run pactest with the version 
of pacman built into the source tree in which pactest is embedded, 
rather than having pactest just run the system pacman.  I wrote a simple 
shell script wrapper for pactest.py that does this:


export PATH=/path/to/my/sources/for/pacman/src/pacman/.libs:$PATH

pactest.py $@

This works for me, but it took me a while to figure out how pactest.py 
was working (and if it had some convenient way to run the local pacman 
instead of the system pacman).  Did I miss something, or is there an 
easier way?


More information about the pacman-dev mailing list