[pacman-dev] Problems with pacman -Rs (pacman3)
I was just using pacman 3 (RC 1) and the -Rs option doesn't work as expected, the dependencies are not removed from the system, even though the pacman database believes they have. For example: I type 'pacman -S aalib' to install aalib Pacman informs me that both gpm-1.20.1-6 and aalib-1.4rc5-4 are to be installed I press enter to continue with the installation. I then type 'pacman -Rs aalib' to remove it and its dependency (gpm) Pacman informs me that both aalib and gpm are to be uninstalled I press enter to confirm and all I get is the following: (1/2) removing aalib [#####################] 100% jeff@jeff:~$ It does not mention removing gpm at all, apart from in the 'Targets' section This has removed aalib from the system and the database, but has not removed gpm from the system, only the database. To prove this I try to install gpm and it complains that all the files already exist in the filesystem and fails with errors. To remove the files I have to force-install, then remove each package manually, which is rather tedious when you do this for a package with many dependencies. Jeff
On 3/12/07, Jeff Bailes <thepizzaking@gmail.com> wrote:
I was just using pacman 3 (RC 1) and the -Rs option doesn't work as expected, the dependencies are not removed from the system, even though the pacman database believes they have. For example: I type 'pacman -S aalib' to install aalib Pacman informs me that both gpm-1.20.1-6 and aalib-1.4rc5-4 are to be installed I press enter to continue with the installation. I then type 'pacman -Rs aalib' to remove it and its dependency (gpm) Pacman informs me that both aalib and gpm are to be uninstalled I press enter to confirm and all I get is the following: (1/2) removing aalib [#####################] 100% jeff@jeff:~$
It does not mention removing gpm at all, apart from in the 'Targets' section
This has removed aalib from the system and the database, but has not removed gpm from the system, only the database. To prove this I try to install gpm and it complains that all the files already exist in the filesystem and fails with errors.
To remove the files I have to force-install, then remove each package manually, which is rather tedious when you do this for a package with many dependencies.
Jeff
Heh, this was fixed in CVS about an hour ago (I think... maybe 2). Thanks for reporting it!
On Mon, 2007-03-12 at 01:35 -0600, Aaron Griffin wrote:
Heh, this was fixed in CVS about an hour ago (I think... maybe 2). Thanks for reporting it!
Good to hear it's fixed, I'm looking forward to the v3 release, great work! Jeff
I was just using pacman 3 (RC 1) and the -Rs option doesn't work as expected, the dependencies are not removed from the system, even though the pacman database believes they have. For example: I type 'pacman -S aalib' to install aalib Pacman informs me that both gpm-1.20.1-6 and aalib-1.4rc5-4 are to be installed I press enter to continue with the installation. I then type 'pacman -Rs aalib' to remove it and its dependency (gpm) Pacman informs me that both aalib and gpm are to be uninstalled I press enter to confirm and all I get is the following: (1/2) removing aalib [#####################] 100% jeff@jeff:~$
Hi! It's interesting, it seems to work for me. One note: this should remove gpm if no other packages requires it. I think an error occurs during removing aalib, instead of being an -Rs bug, since (1/2) is displayed; and as you described, aalib still exists on the system. (On my machine pacman -S aalib and pacman -R aalib works without any problem anyway.) Bye, NG. PS: I'm using the latest CVS version, please test with it
On 3/12/07, Nagy Gabor <ngaba@petra.hos.u-szeged.hu> wrote:
PS: I'm using the latest CVS version, please test with it
It's not really expected that most people will use the version from CVS. As I already stated, I'm pretty sure this is fixed in CVS, and a new RC will be pushed out tomorrow (well, now+12 hours or so)
participants (3)
-
Aaron Griffin
-
Jeff Bailes
-
Nagy Gabor