Opened 9 years ago

Closed 9 years ago

#48882 closed defect (fixed)

plplot and plplot510 conflict

Reported by: kjy9308@… Owned by: tenomoto (Takeshi Enomoto)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: plplot plplot510

Description

i successed

sudo port -d selfupdate

then

i tried

sudo port upgrade outdated

but error..

help me.

Attachments (1)

selfupdate_main.log (21.9 KB) - added by kjy9308@… 9 years ago.

Download all attachments as: .zip

Change History (5)

Changed 9 years ago by kjy9308@…

Attachment: selfupdate_main.log added

comment:1 Changed 9 years ago by kjy9308@…

and i wrote julia error (ticket #48346).

julia error comes up because this error(upgrade error)?

comment:2 in reply to:  1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Owner: changed from macports-tickets@… to takeshi@…
Port: plplot plplot510 added; upgrade removed
Summary: upgrade outdatedplplot and plplot510 conflict

Replying to kjy9308@…:

julia error comes up because this error(upgrade error)?

The two problems do not appear to be related.

The log you attached here says:

:error:activate org.macports.activate for port plplot510 returned: Image error: /opt/local/bin/pltcl is being used by the active plplot port.  Please deactivate this port first, or use 'port -f activate plplot510' to force the activation.

The problem is that the plplot and plplot510 ports apparently try to install files to the same locations. They should be modified to not do this.

In fact, plplot510 was already modified not to do this in r140034. However, the port's revision was not increased, so anyone whose MacPorts installation receives binaries from our build server would still get the old conflicting version.

The problem should be fixed by r140256 which increased the port's revision. Please run "sudo port selfupdate" again and then try upgrading the outdated ports again.

comment:3 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

On further inspection, I see that although r140034 fixed the problem by changing the install location, r140230 unfixed it by changing it back. Takeshi, can you fix it again, please?

comment:4 Changed 9 years ago by tenomoto (Takeshi Enomoto)

Resolution: fixed
Status: newclosed

Done in r140394. Thanks.

Note: See TracTickets for help on using tickets.