On 2023-03-27 at 17:54:53 UTC-0400 (Mon, 27 Mar 2023 14:54:53 -0700)
Kenneth Wolcott <kennethwolc...@gmail.com>
is rumored to have said:
Weird. Getting ready to create a ticket for not being able to be
upgraded. Now I see it does not show up on the outdated list. Well,
the "replaced" ports are still in the outdated list. Guess I'll just
ignore that.
What happens if you use 'port upgrade' instead of 'port install'?
On Mon, Mar 27, 2023 at 2:45 PM Kenneth Wolcott
<kennethwolc...@gmail.com> wrote:
Just successfully completed a selfupdate and the re-install of:
port -n upgrade --enforce-variants openssl3 +universal
Now what remains is what follows:
port outdated
The following installed ports are outdated:
libtorrent-rasterbar 2.0.8_0 < 2.0.8_1
py39-pep517 0.13.0_0 < 0.13.0_1
py310-pep517 0.13.0_0 < 0.13.0_1
py311-pep517 0.13.0_0 < 0.13.0_1
So:
sudo port install libtorrent-rasterbar
Password:
---> Computing dependencies for libtorrent-rasterbar
---> Fetching archive for libtorrent-rasterbar
---> Attempting to fetch
libtorrent-rasterbar-2.0.8_1+python311.darwin_22.arm64.tbz2 from
https://packages.macports.org/libtorrent-rasterbar
---> Attempting to fetch
libtorrent-rasterbar-2.0.8_1+python311.darwin_22.arm64.tbz2.rmd160
from https://packages.macports.org/libtorrent-rasterbar
---> Installing libtorrent-rasterbar @2.0.8_1+python311
Warning: boost176 must be installed with +python311.
I know that this will fail (tried it before), but to document the
failure, here goes:
Continue? [Y/n]: y
---> Computing dependencies for libtorrent-rasterbar
---> Cleaning libtorrent-rasterbar
---> Scanning binaries for linking errors
---> Found 1 broken file, matching files to ports
---> Found 1 broken port, determining rebuild order
---> Rebuilding in order
libtorrent-rasterbar @2.0.8_1+python311
---> Computing dependencies for libtorrent-rasterbar
---> Fetching distfiles for libtorrent-rasterbar
---> Verifying checksums for libtorrent-rasterbar
---> Extracting libtorrent-rasterbar
---> Applying patches to libtorrent-rasterbar
---> Configuring libtorrent-rasterbar
Error: Failed to configure libtorrent-rasterbar: boost176 must be
installed with +python311.
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_net_libtorrent-rasterbar/libtorrent-rasterbar/main.log
for details.
Error: rev-upgrade failed: Error rebuilding libtorrent-rasterbar
Error: Follow https://guide.macports.org/#project.tickets if you
believe there is a bug.
So, I'll file a bug for this part.
Now what about the other three ports?
Why are these ports still on my outdated list if they have been
replaced?
sudo port -v -s install py39-pep517 py310-pep517 py311-pep517
py39-pep517 is replaced by py39-pyproject_hooks
---> Computing dependencies for py39-pyproject_hooks.
---> Cleaning py39-pyproject_hooks
---> Removing work directory for py39-pyproject_hooks
py310-pep517 is replaced by py310-pyproject_hooks
---> Computing dependencies for py310-pyproject_hooks.
---> Cleaning py310-pyproject_hooks
---> Removing work directory for py310-pyproject_hooks
py311-pep517 is replaced by py311-pyproject_hooks
---> Computing dependencies for py311-pyproject_hooks.
---> Cleaning py311-pyproject_hooks
---> Removing work directory for py311-pyproject_hooks
---> Scanning binaries for linking errors
Could not open
/opt/local/libexec/boost/1.76/lib/libboost_python311-mt.dylib:
Error opening or reading file (referenced from
/opt/local/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/libtorrent.cpython-311-darwin.so)
---> Found 1 broken file, 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: libtorrent-rasterbar
@2.0.8+python311
Continue? [Y/n]: n
Perhaps I should remove these ports?
I'll try that.
No, that's NOT a good idea :-(
sudo port -v uninstall py39-pep517 py310-pep517 py311-pep517
Note: It is not recommended to uninstall/deactivate a port that has
dependents as it breaks the dependents.
The following ports will break: py39-build @0.9.0_0
Continue? [y/N]: n
---> Cleaning py39-pep517
---> Removing work directory for py39-pep517
Note: It is not recommended to uninstall/deactivate a port that has
dependents as it breaks the dependents.
The following ports will break:
py310-build @0.8.0_0
py310-build @0.9.0_0
Continue? [y/N]: n
---> Cleaning py310-pep517
---> Removing work directory for py310-pep517
Note: It is not recommended to uninstall/deactivate a port that has
dependents as it breaks the dependents.
The following ports will break:
py311-build @0.8.0_0
py311-build @0.9.0_0
Continue? [y/N]: n
---> Cleaning py311-pep517
---> Removing work directory for py311-pep517
So I guess I'll write up a bug for this as well.
Ken Wolcott
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
