[MacPorts] #58634: cargo is built before cargo-stage1 with rev-upgrade
MacPorts
noreply at macports.org
Mon Jun 24 02:43:48 UTC 2019
#58634: cargo is built before cargo-stage1 with rev-upgrade
----------------------+--------------------
Reporter: marka63 | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: |
----------------------+--------------------
Comment (by marka63):
Also when re-activating cargo rev-upgrade needed to be manually run.
{{{
% sudo port deactivate cargo
Password:
---> Deactivating cargo @0.36.0_0
---> Cleaning cargo
% sudo port rev-upgrade
---> Scanning binaries for linking errors
---> Found 2 broken files, matching files to ports
---> Found 1 broken port, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt: cargo-stage1 @0.36.0
Continue? [Y/n]: y
---> Computing dependencies for cargo-stage1
---> Cleaning cargo-stage1
---> Scanning binaries for linking errors
---> Found 2 broken files, matching files to ports
---> Found 1 broken port, determining rebuild order
---> Rebuilding in order
cargo-stage1 @0.36.0
---> Computing dependencies for cargo-stage1
---> Fetching distfiles for cargo-stage1
---> Verifying checksums for cargo-stage1
---> Extracting cargo-stage1
---> Configuring cargo-stage1
---> Building cargo-stage1
---> Staging cargo-stage1 into destroot
---> Deactivating cargo-stage1 @0.36.0_0
---> Cleaning cargo-stage1
---> Uninstalling cargo-stage1 @0.36.0_0
---> Cleaning cargo-stage1
---> Computing dependencies for cargo-stage1
---> Installing cargo-stage1 @0.36.0_0
---> Activating cargo-stage1 @0.36.0_0
---> Cleaning cargo-stage1
---> Scanning binaries for linking errors
---> No broken files found.
---> No broken ports found.
% sudo port activate cargo
The following versions of cargo are currently installed:
1) cargo @0.27.0_0
2) cargo @0.27.0_1
3) cargo @0.31.1_2
4) cargo @0.36.0_0
Enter a number to select an option: 4
---> Activating cargo @0.36.0_0
% sudo port rev-upgrade
---> Scanning binaries for linking errors
---> Found 2 broken files, matching files to ports
---> Found 1 broken port, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt: cargo @0.36.0
Continue? [Y/n]: y
---> Computing dependencies for cargo
---> Cleaning cargo
---> Scanning binaries for linking errors
---> Found 2 broken files, matching files to ports
---> Found 1 broken port, determining rebuild order
---> Rebuilding in order
cargo @0.36.0
---> Computing dependencies for cargo
---> Fetching distfiles for cargo
---> Verifying checksums for cargo
---> Extracting cargo
---> Configuring cargo
---> Building cargo
---> Staging cargo into destroot
---> Deactivating cargo @0.36.0_0
---> Cleaning cargo
---> Uninstalling cargo @0.36.0_0
---> Cleaning cargo
---> Computing dependencies for cargo
---> Installing cargo @0.36.0_0
---> Activating cargo @0.36.0_0
---> Cleaning cargo
---> Scanning binaries for linking errors
---> No broken files found.
---> No broken ports found.
%
}}}
--
Ticket URL: <https://trac.macports.org/ticket/58634#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list