Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#59787 closed defect (fixed)

Including a nonexistent portgroup should be an error

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by:
Priority: Normal Milestone: MacPorts 2.7.0
Component: base Version: 2.6.2
Keywords: Cc: kurthindenburg (Kurt Hindenburg)
Port:

Description

When a Portfile includes a portgroup that does not exist, MacPorts prints a warning, then tries to build the port anyway, which can't possibly succeed. For example, I saw this when trying to use an old version of a portfile I grabbed from our history:

Warning: PortGroup python27 1.0 could not be located. python27-1.0.tcl does not exist.
Warning: PortGroup python27 1.0 could not be located. python27-1.0.tcl does not exist.
--->  Computing dependencies for py27-pylibelf
--->  Fetching distfiles for py27-pylibelf
--->  Verifying checksums for py27-pylibelf
--->  Extracting py27-pylibelf
--->  Applying patches to py27-pylibelf
--->  Configuring py27-pylibelf
Error: Failed to configure py27-pylibelf: configure failure: command execution failed

Including a nonexistent portgroup should be an error after which we stop, not a warning after which we try to proceed.

Change History (3)

comment:1 Changed 5 years ago by kurthindenburg (Kurt Hindenburg)

Cc: kurthindenburg added

comment:2 Changed 5 years ago by kurthindenburg (Kurt Hindenburg)

Resolution: fixed
Status: newclosed

comment:3 Changed 4 years ago by jmroot (Joshua Root)

Milestone: MacPorts 2.7.0
Note: See TracTickets for help on using tickets.