Opened 17 years ago

Last modified 14 years ago

#12344 closed defect

BUG: Uninstalling a deactivated port still triggers dependency warnings. — at Version 2

Reported by: schwern@… Owned by: macports-tickets@…
Priority: Low Milestone:
Component: base Version:
Keywords: Cc:
Port:

Description (last modified by jmpp@…)

Uninstalling a deactivated port, even while another version is active, port still checks for dependencies as if it were active. As a result I can't simply say "port uninstall inactive" without the dangers of forcing it.

Here's an example attempting to uninstall a deactive version of bison.

$ port uninstall bison
--->  The following versions of bison are currently installed:
--->    bison @2.2_0
--->    bison @2.3_0 (active)
Error: port uninstall failed: Registry error: Please specify the full version as recorded in the port registry.

$ port uninstall bison@2.2_0
--->  Unable to uninstall bison 2.2_0, the following ports depend on it:
--->    gpg-agent
--->    gpg-agent
Error: port uninstall failed: Please uninstall the ports that depend on bison first.

$ port info gpg-agent
gpg-agent 2.0.3, security/gpg-agent (Variants: universal, darwin, darwin_7, no_pinentry)
http://www.gnupg.org

gpg-agent is a key management agent similar in function to ssh-agent.

Library Dependencies: libiconv, gettext, zlib, bzip2, bison, libassuan, libksba, libgcrypt, libgpg-error, pth, pinentry
Platforms: darwin freebsd sunos
Maintainers: yeled@macports.org

Change History (2)

comment:1 Changed 17 years ago by nox@…

Milestone: MacPorts base bugs
Priority: Nice to haveLow
Summary: Uninstalling a deactivated port still triggers dependency warnings.BUG: Uninstalling a deactivated port still triggers dependency warnings.
Version: 1.5.0

comment:2 Changed 17 years ago by jmpp@…

Component: portsbase
Description: modified (diff)
Note: See TracTickets for help on using tickets.