FS#2881 - pacman & pathological

Attached to Project: Pacman
Opened by Claudio Riva (Firetux) - Sunday, 26 June 2005, 13:14 GMT
Task Type Bug Report
Category
Status Closed
Assigned To No-one
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

I installed "pathological" that requires pygame providev by python-pygame

[root@p4m firetux]# pacman -S pathological

Targets: python-numeric-23.6-1 python-pygame-1.6-3 pathological-1.1.3-2

Total Package Size: 7.1 MB

Proceed with upgrade? [Y/n]

:: Retrieving packages from extra...
python-numeric-23.6-1 [################] 100% 549K 105.8K/s 00:00:05
python-pygame-1.6-3 [################] 100% 337K 87.0K/s 00:00:03
pathological-1.1.3-2 [################] 100% 6393K 144.2K/s 00:00:44

checking package integrity... done.
loading package data... done.
checking for file conflicts... done.
installing python-numeric... done.
installing python-pygame... done.
installing pathological... done.


After I played with this game I decided to remove it and all it dependences with the command:
pacman -Rs pathological
but pacman goes in loop and you have to teminate it with CTRL+C
I think that the problem is that pygame is not a pkg but it is a "pkg" provide by another pkg (python-pygame)
If I try to remove the pkgs one at time:
pacman -R pathological
pacman -R python-pygame
pacman -R python-numeric
all works well
...why?
This task depends upon

Closed by  Judd Vinet (judd)
Sunday, 03 July 2005, 22:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in CVS. Thanks.
Comment by Berger (Berger) - Tuesday, 28 June 2005, 15:36 GMT
I've the same problem. I successfully removed pathological with

pacman -R pathological
pacman -Rs python-pygame
Comment by Claudio Riva (Firetux) - Tuesday, 28 June 2005, 15:50 GMT
Yes, I do it in 3 steps but the result it's the same.
The problem is that pacman should do it!
Comment by Aaron Griffin (phrakture) - Tuesday, 28 June 2005, 21:51 GMT
Email the maintainer (JGC) and ask him to change the dependancy from "pygame" to python-pygame
Comment by Claudio Riva (Firetux) - Tuesday, 28 June 2005, 21:55 GMT
ok, this is a solution but I think that the problem remain for other pkgs that use a dependence provide by another pkg... don't you think?

Loading...