Opened 15 years ago

Closed 3 years ago

#24233 closed defect (fixed)

advancemame and advancemenu conflict

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: advancemame, advancemenu

Description

advancemame and advancemenu conflict:

$ sudo port install advancemame
--->  Computing dependencies for advancemame
--->  Fetching advancemame
--->  Verifying checksum(s) for advancemame
--->  Extracting advancemame
--->  Applying patches to advancemame
--->  Configuring advancemame
--->  Building advancemame
--->  Staging advancemame into destroot
--->  Installing advancemame @0.106.1_0+darwin_i386+universal
--->  Activating advancemame @0.106.1_0+darwin_i386+universal
Error: Target org.macports.activate returned: Image error: /opt/local/share/doc/advance/advcfg.html is being used by the active advancemenu port.  Please deactivate this port first, or use 'port -f activate advancemame' to force the activation.
Error: Status 1 encountered during processing.

Is this intentional? I thought advancemame and advancemenu were meant to work together. But if the conflict is intentional, both ports should be marked as conflicting with one another using the "conflicts" keyword.

Change History (2)

comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from milosh@… to macports-tickets@…

milosh has retired.

comment:2 Changed 3 years ago by chrstphrchvz (Christopher Chavez)

Resolution: fixed
Status: newclosed

In 725e88258070bc8968a24fd2b25bd0d9647a5265/macports-ports (master):

advancemenu: remove obsolete port

Replaced by advancemame in be8b539fd9 over a year ago
Closes: #24233

Note: See TracTickets for help on using tickets.