Opened 2 years ago

Last modified 9 months ago

#58103 new enhancement

new command request: port broken

Reported by: TheLastLovemark Owned by:
Priority: Normal Milestone:
Component: base Version:
Keywords: Cc:
Port:

Description

This would list broken ports without having to initiate a rev-update or the upgrade/install of another port and learning that things are broken by surprise.

Essentially it is the equivalent of port installed, port inactive/active, or port outdated, but for broken ports.

Change History (6)

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

Port: all removed
Type: requestenhancement

There is no currently-existing source of information from which such a command could draw.

comment:2 Changed 2 years ago by TheLastLovemark

Then how does something like this get generated?

--->  Found 42 broken files, matching files to ports
rb-eventmachine is using libstdc++ (this installation is configured to use libc++)
sqlmap is using libstdc++ (this installation is configured to use libc++)
openmpi-gcc5 is using libstdc++ (this installation is configured to use libc++)
openmpi-gcc6 is using libstdc++ (this installation is configured to use libc++)
openmpi-gcc49 is using libstdc++ (this installation is configured to use libc++)
--->  Found 11 broken ports, determining rebuild order
DEBUG: Broken: R-app
DEBUG: Broken: enblend
DEBUG: Broken: ntop
DEBUG: Broken: objectmarker
DEBUG: Broken: libkdcraw
DEBUG: Broken: libVLC
DEBUG: Broken: rb-eventmachine
DEBUG: Broken: sqlmap
DEBUG: Broken: openmpi-gcc5
DEBUG: Broken: openmpi-gcc6
DEBUG: Broken: openmpi-gcc49
DEBUG: Processing port R-app @0:1.68_1  
DEBUG: Processing port enblend @0:4.1.5_4  
DEBUG: Processing port hugin-app @0:2018.0.0_3 +accelerate+python27 
DEBUG: Processing port luminance-hdr @0:2.5.1_4 +external 
DEBUG: Processing port ntop @0:5.0.1_3  
DEBUG: Processing port objectmarker @0:20070501_2  
DEBUG: Processing port libkdcraw @0:4.14.3_5  
DEBUG: Processing port libVLC @0:2.2.8_7 +quartz 
DEBUG: Processing port rb-eventmachine @0:0.12.10_0  
DEBUG: Processing port rb-twitter-stream @0:0.1.14_0  
DEBUG: Processing port rb-tweetstream @0:1.0.4_0  
DEBUG: Processing port sqlmap @0:0.9_1 +python27 
DEBUG: Processing port openmpi-gcc5 @0:3.0.0_0 +fortran 
DEBUG: Processing port openmpi-gcc6 @0:3.0.0_0 +fortran 
DEBUG: Processing port openmpi-gcc49 @0:3.0.0_0 +fortran 
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt:
 R-app @1.68
 enblend @4.1.5
 ntop @5.0.1
 objectmarker @20070501
 libkdcraw @4.14.3
 libVLC @2.2.8+quartz
 rb-eventmachine @0.12.10
 sqlmap @0.9+python27
 openmpi-gcc5 @3.0.0+fortran
 openmpi-gcc6 @3.0.0+fortran
 openmpi-gcc49 @3.0.0+fortran

You mean there's no way to create a command that provides such information?

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

You can already get this information by running sudo port -vy rev-upgrade.

comment:4 in reply to:  2 Changed 2 years ago by ryandesign (Ryan Schmidt)

Replying to TheLastLovemark:

Then how does something like this get generated?

Oh. That kind of "broken". I thought you meant "broken" as in the port cannot be built.

comment:5 Changed 2 years ago by TheLastLovemark

Any word on this? I've been incommunicado for a few weeks

comment:6 Changed 9 months ago by ryandesign (Ryan Schmidt)

Josh provided a way to do what you wanted. Is that not sufficient?

Note: See TracTickets for help on using tickets.