Opened 9 years ago

Closed 9 years ago

#48104 closed defect (fixed)

p5-test-file conflicts with p5-test-mockobject

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 2.3.99
Keywords: Cc:
Port: p5-test-file, p5-test-mockobject

Description 

--->  Computing dependencies for p5.20-test-file
--->  Fetching distfiles for p5.20-test-file
--->  Verifying checksums for p5.20-test-file
--->  Extracting p5.20-test-file
--->  Configuring p5.20-test-file
--->  Building p5.20-test-file
--->  Staging p5.20-test-file into destroot
--->  Installing p5.20-test-file @1.420.0_0
--->  Cleaning p5.20-test-file
--->  Computing dependencies for p5.20-test-file
--->  Deactivating p5.20-test-file @1.410.0_0
--->  Activating p5.20-test-file @1.420.0_0
Error: Failed to activate p5.20-test-file: Image error: /opt/local/lib/perl5/vendor_perl/5.20/Test/README.pod is being used by the active p5.20-test-mockobject port.  Please deactivate this port first, or use 'port -f activate p5.20-test-file' to force the activation.
Error: See /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_perl_p5-test-file/p5.20-test-file/main.log for details.
--->  Uninstalling p5.20-test-file @1.410.0_0

Change History (1)

comment:1 Changed 9 years ago by dbevans (David B. Evans)

Resolution: → fixed
Status: new → closed

The README.pod file itself seems to be the problem here. Its presence at top level causes Makefile.PL to install it in the module's parent's directory (Test) rather than the module's own directory (Test::File, Test::MockObject). A corresponding misplaced man page is also automatically generated.

Since both Test::File and Test::MockObject do this, the conflict occurs.

Fixed in r137785.

Note: See TracTickets for help on using tickets.