Re: ports that are outdated but cannot be upgraded.
Thank you for the clarification, but I prefer building from source (I have the M1 chip) because at least once some x86-64 port really screwed things up for awhile (it could have been one of my many non-forced errors :-) ) Ken On Thu, Mar 30, 2023 at 12:10 AM Christopher Jones wrote: > > > > > On 30 Mar 2023, at 2:28 am, Kenneth Wolcott > > wrote: > > > > Not too bad. The uninstall and install from source sequence completed > > fairly quickly. > > Chances are you did not need to build from source, as this is only required > for specific reasons, like if you pick non-default variants (which the > commands you where given do not) or if you are using a non-default > installation prefix. > > Chris > > > > > Thanks, > > Ken > > > > On Wed, Mar 29, 2023 at 10:12 AM Bill Cole > > wrote: > >> > >> On 2023-03-29 at 07:49:28 UTC-0400 (Wed, 29 Mar 2023 12:49:28 +0100) > >> Christopher Jones > >> is rumored to have said: > >> > >>> Hio, > >>> > >>> Your problem is precisely what it says at the end > >>> > Error: Failed to configure libtorrent-rasterbar: boost176 must be > installed with +python311. > >>> > >>> you will likely have it installed with a different python version > >>> selected, and port respects this as your ‘choice’. You need to > >>> uninstall boost176 and reinstall it with the new default variants. > >> > >> I agree 100%. Simple commands: > >> > >> port uninstall boost176 > >> port install boost176 > >> > >> Beware: building Boost from source is painfully slow. > >> > >> > >> -- > >> Bill Cole > >> b...@scconsult.com or billc...@apache.org > >> (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > >> Not Currently Available For Hire >
Re: ports that are outdated but cannot be upgraded.
> On 30 Mar 2023, at 2:28 am, Kenneth Wolcott wrote: > > Not too bad. The uninstall and install from source sequence completed > fairly quickly. Chances are you did not need to build from source, as this is only required for specific reasons, like if you pick non-default variants (which the commands you where given do not) or if you are using a non-default installation prefix. Chris > > Thanks, > Ken > > On Wed, Mar 29, 2023 at 10:12 AM Bill Cole > wrote: >> >> On 2023-03-29 at 07:49:28 UTC-0400 (Wed, 29 Mar 2023 12:49:28 +0100) >> Christopher Jones >> is rumored to have said: >> >>> Hio, >>> >>> Your problem is precisely what it says at the end >>> Error: Failed to configure libtorrent-rasterbar: boost176 must be installed with +python311. >>> >>> you will likely have it installed with a different python version >>> selected, and port respects this as your ‘choice’. You need to >>> uninstall boost176 and reinstall it with the new default variants. >> >> I agree 100%. Simple commands: >> >> port uninstall boost176 >> port install boost176 >> >> Beware: building Boost from source is painfully slow. >> >> >> -- >> Bill Cole >> b...@scconsult.com or billc...@apache.org >> (AKA @grumpybozo and many *@billmail.scconsult.com addresses) >> Not Currently Available For Hire
Re: ports that are outdated but cannot be upgraded.
Not too bad. The uninstall and install from source sequence completed fairly quickly. Thanks, Ken On Wed, Mar 29, 2023 at 10:12 AM Bill Cole wrote: > > On 2023-03-29 at 07:49:28 UTC-0400 (Wed, 29 Mar 2023 12:49:28 +0100) > Christopher Jones > is rumored to have said: > > > Hio, > > > > Your problem is precisely what it says at the end > > > >> Error: Failed to configure libtorrent-rasterbar: boost176 must be > >> installed with +python311. > > > > you will likely have it installed with a different python version > > selected, and port respects this as your ‘choice’. You need to > > uninstall boost176 and reinstall it with the new default variants. > > I agree 100%. Simple commands: > > port uninstall boost176 > port install boost176 > > Beware: building Boost from source is painfully slow. > > > -- > Bill Cole > b...@scconsult.com or billc...@apache.org > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > Not Currently Available For Hire
Re: ports that are outdated but cannot be upgraded.
On 2023-03-29 at 07:49:28 UTC-0400 (Wed, 29 Mar 2023 12:49:28 +0100) Christopher Jones is rumored to have said: Hio, Your problem is precisely what it says at the end Error: Failed to configure libtorrent-rasterbar: boost176 must be installed with +python311. you will likely have it installed with a different python version selected, and port respects this as your ‘choice’. You need to uninstall boost176 and reinstall it with the new default variants. I agree 100%. Simple commands: port uninstall boost176 port install boost176 Beware: building Boost from source is painfully slow. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
Re: ports that are outdated but cannot be upgraded.
Hio, Your problem is precisely what it says at the end > Error: Failed to configure libtorrent-rasterbar: boost176 must be > installed with +python311. you will likely have it installed with a different python version selected, and port respects this as your ‘choice’. You need to uninstall boost176 and reinstall it with the new default variants. Chris > On 29 Mar 2023, at 4:26 am, Kenneth Wolcott wrote: > > Hi Bill; > > I ran selfupdate again. > > Then port outdated > > Then sudo port -v -s upgrade outdated > > Now I get the message: > > ---> 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 > ~: sudo port rev-upgrade > ---> Scanning binaries for linking errors > ---> 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]: 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. > > On Tue, Mar 28, 2023 at 12:48 PM Kenneth Wolcott > wrote: >> >> Hi Bill; >> >> I've tried that, but the problem remains even if I do respond affirmatively. >> >> I think that there's a root problem here, but I just can't grasp >> what it is precisely. >> >> Thanks, >> Ken >> >> On Tue, Mar 28, 2023 at 12:41 PM Bill Cole >> wrote: >>> >>> On 2023-03-28 at 15:03:48 UTC-0400 (Tue, 28 Mar 2023 12:03:48 -0700) >>> Kenneth Wolcott >>> is rumored to have said: >>> HI; I ran a selfupdate successfully today. Then "sudo port -v -s upgrade outdated" seemed successful. But then: ---> 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 ~: port diagnose [nothing returned] port outdated No installed ports are outdated. So, this still seems less than ideal. >>> >>> It seems to me that the right answer to rev-upgrade's "Continue?" prompt >>> should always be "y" but I could be wrong. >>> >>> -- >>> Bill Cole >>> b...@scconsult.com or billc...@apache.org >>> (AKA @grumpybozo and many *@billmail.scconsult.com addresses) >>> Not Currently Available For Hire
Re: ports that are outdated but cannot be upgraded.
Hi Bill; I ran selfupdate again. Then port outdated Then sudo port -v -s upgrade outdated Now I get the message: ---> 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 ~: sudo port rev-upgrade ---> Scanning binaries for linking errors ---> 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]: 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. On Tue, Mar 28, 2023 at 12:48 PM Kenneth Wolcott wrote: > > Hi Bill; > > I've tried that, but the problem remains even if I do respond affirmatively. > > I think that there's a root problem here, but I just can't grasp > what it is precisely. > > Thanks, > Ken > > On Tue, Mar 28, 2023 at 12:41 PM Bill Cole > wrote: > > > > On 2023-03-28 at 15:03:48 UTC-0400 (Tue, 28 Mar 2023 12:03:48 -0700) > > Kenneth Wolcott > > is rumored to have said: > > > > > HI; > > > > > > I ran a selfupdate successfully today. > > > > > > Then "sudo port -v -s upgrade outdated" seemed successful. > > > > > > But then: > > > > > > ---> 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 > > > ~: port diagnose > > > [nothing returned] > > > port outdated > > > No installed ports are outdated. > > > > > > So, this still seems less than ideal. > > > > It seems to me that the right answer to rev-upgrade's "Continue?" prompt > > should always be "y" but I could be wrong. > > > > -- > > Bill Cole > > b...@scconsult.com or billc...@apache.org > > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > > Not Currently Available For Hire
Re: ports that are outdated but cannot be upgraded.
Hi Bill; I've tried that, but the problem remains even if I do respond affirmatively. I think that there's a root problem here, but I just can't grasp what it is precisely. Thanks, Ken On Tue, Mar 28, 2023 at 12:41 PM Bill Cole wrote: > > On 2023-03-28 at 15:03:48 UTC-0400 (Tue, 28 Mar 2023 12:03:48 -0700) > Kenneth Wolcott > is rumored to have said: > > > HI; > > > > I ran a selfupdate successfully today. > > > > Then "sudo port -v -s upgrade outdated" seemed successful. > > > > But then: > > > > ---> 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 > > ~: port diagnose > > [nothing returned] > > port outdated > > No installed ports are outdated. > > > > So, this still seems less than ideal. > > It seems to me that the right answer to rev-upgrade's "Continue?" prompt > should always be "y" but I could be wrong. > > -- > Bill Cole > b...@scconsult.com or billc...@apache.org > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > Not Currently Available For Hire
Re: ports that are outdated but cannot be upgraded.
On 2023-03-28 at 15:03:48 UTC-0400 (Tue, 28 Mar 2023 12:03:48 -0700) Kenneth Wolcott is rumored to have said: HI; I ran a selfupdate successfully today. Then "sudo port -v -s upgrade outdated" seemed successful. But then: ---> 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 ~: port diagnose [nothing returned] port outdated No installed ports are outdated. So, this still seems less than ideal. It seems to me that the right answer to rev-upgrade's "Continue?" prompt should always be "y" but I could be wrong. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
Re: ports that are outdated but cannot be upgraded.
HI;
I ran a selfupdate successfully today.
Then "sudo port -v -s upgrade outdated" seemed successful.
But then:
---> 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
~: port diagnose
[nothing returned]
port outdated
No installed ports are outdated.
So, this still seems less than ideal.
Thanks,
Ken
On Mon, Mar 27, 2023 at 8:49 PM Kenneth Wolcott
wrote:
>
> Hi Bill;
>
> Interestering. I ran 'sudo port -v -s upgrade `port outdated | grep
> -v following | awk '{print $1}'`
>
> I got the usual complaint "libtorrent-rasterbar @2.0.8+python311"
>
> 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
>
> port outdated
> No installed ports are outdated.
> ~: port diagnose
> [no output, which is good]
>
> Then I ran the selfudpate.
>
> Then
> port outdated
> No installed ports are outdated.
>
> So, does that mean it is all cleared up now?
>
> Thanks,
> Ken
>
> On Mon, Mar 27, 2023 at 8:02 PM Bill Cole
> wrote:
> >
> > On 2023-03-27 at 17:54:53 UTC-0400 (Mon, 27 Mar 2023 14:54:53 -0700)
> > Kenneth Wolcott
> > 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
> > > 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-pep5170.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?
>
Re: ports that are outdated but cannot be upgraded.
Hi Bill;
Interestering. I ran 'sudo port -v -s upgrade `port outdated | grep
-v following | awk '{print $1}'`
I got the usual complaint "libtorrent-rasterbar @2.0.8+python311"
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
port outdated
No installed ports are outdated.
~: port diagnose
[no output, which is good]
Then I ran the selfudpate.
Then
port outdated
No installed ports are outdated.
So, does that mean it is all cleared up now?
Thanks,
Ken
On Mon, Mar 27, 2023 at 8:02 PM Bill Cole
wrote:
>
> On 2023-03-27 at 17:54:53 UTC-0400 (Mon, 27 Mar 2023 14:54:53 -0700)
> Kenneth Wolcott
> 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
> > 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-pep5170.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
> >>
Re: ports that are outdated but cannot be upgraded.
On 2023-03-27 at 17:54:53 UTC-0400 (Mon, 27 Mar 2023 14:54:53 -0700) Kenneth Wolcott 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 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-pep5170.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
Re: ports that are outdated but cannot be upgraded.
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. On Mon, Mar 27, 2023 at 2:45 PM Kenneth Wolcott 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-pep5170.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
ports that are outdated but cannot be upgraded.
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-pep5170.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
