A question about adding a path to the sandbox profile and about `port upgrade outdated`

work. What does work is to disable the sandbox completely, which doesn't make sense. I've copied my syntax from portsandbox.tcl and see no errors when I print portsandbox_profile after appending to it. 2) Does `port upgrade outdated` do an explicit `port clean foo` before doing `port upgrade

Re: Port upgrade outdated

Hello Clemens, Thanks for your clarification. I will note this to automate upgrade. Bests Raoul rm...@orange.fr > On 6 Oct 2022, at 21:30, Clemens Lang wrote: > > On Thu, Oct 06, 2022 at 02:34:48PM +0200, Raoul MEGELAS wrote: >> You have understood well, I was

Re: Port upgrade outdated

On Thu, Oct 06, 2022 at 02:34:48PM +0200, Raoul MEGELAS wrote: > You have understood well, I was getting the message repeatedly. I believe this happens when you request installation of multiple ports on the command line, i.e. port install portA portB portC may ask up to three times. If you

Re: Port upgrade outdated

Hello, You have understood well, I was getting the message repeatedly. But I upgraded my machine with a new one and the ports was migrated. So I reinstalled completely macports, And I will report if appropriate. Thanks and Bests. Raoul > On 5 Oct 2022, at 20:12, Lenore Horner wrote: >

Re: Port upgrade outdated

On Wed, 5 Oct 2022, Lenore Horner wrote: > Maybe I misunderstood Raoul's post.   > What I see at the end of > port install blah > is a list of ports that will also have to be installed and the line > Continue? [Y/n]: > This suggests to me that the response is case sensitive. Nope; it's saying

Re: Port upgrade outdated

Maybe I misunderstood Raoul's post. What I see at the end of port install blah is a list of ports that will also have to be installed and the line Continue? [Y/n]: This suggests to me that the response is case sensitive. Neither upgrade outdated nor install blah every gives me a prompt of

Re: Port upgrade outdated

When I do upgrade outdated I get a list of things to be upgraded and then am asked at the end of the list whether I want to proceed or not. I haven't fiddled with any MacPorts default settings. Not sure why we're seeing different things. Lenore > On Oct 5, 2022, at 10:29, Raoul MEGELAS

Port upgrade outdated

Hi, Please can you add ALL to Install Y/N (yes/no) I get: Install y/n Install y/n Install y/n inInstall y/n Do I continue??? Thanks in advance. RMgsl

Re: port upgrade outdated hangs network

On Jan 16, 2022, at 13:28, phle...@cantab.net wrote: > Thanks for your brilliantly helpful response. > Yes.. the pings are indirectly to blame!! > No, I am not running a third party firewall. > But I read the notes and noticed the comments about > changing the max_hosts_to_ping: I had noticed >

Re: port upgrade outdated hangs network

in the usual way: sudo port upgrade outdated Everything goes along fine until the software reached gd2. I then see: --->  Fetching archive for gd2 --->  Attempting to fetch gd2-2.3.3_1+x11.darwin_19.x86_64.tbz2 from https://packages.macports.org/gd2 --->  Attempting to fetch gd2-2.

Re: port upgrade outdated hangs networking

This is extraordinary .. it presumably is a bug in MacOS. Running MacOS 10.15.7  on MacBook Pro 2016 I am updating various already installed packges in the usual way: sudo port upgrade outdated Everything goes along fine until the software reached gd2. I then see: --->  Fetching arch

Re: port upgrade outdated hangs networking

stalled packges in the usual way: > sudo port upgrade outdated > > Everything goes along fine until the software reached gd2. > I then see: > > ---> Fetching archive for gd2 > ---> Attempting to fetch gd2-2.3.3_1+x11.darwin_19.x86_64.tbz2 from > https://packages.macports.org/gd

port upgrade outdated hangs networking

This is extraordinary .. it presumably is a bug in MacOS. Running MacOS 10.15.7  on MacBook Pro 2016 I am updating various already installed packges in the usual way: sudo port upgrade outdated Everything goes along fine until the software reached gd2. I then see: --->  Fetching arch

Re: port upgrade outdated fails

On Tue, Aug 27, 2019 at 02:53:03PM +0100, Chris Jones wrote: > Ball is in your court to fix this. Serving suggestion: rather than rip-and-replace, it may be worth using "port upgrade --enforce-variants offending_port +gcc9 +other_variants" to change the variants in-place. We use that trick on a

Re: port upgrade outdated fails

gcc9 default the default when it was release, last year. Its up to you what you do here. either use gcc8, or gcc9. not a mixture of both. Chris If the port was built with the gcc8 variant, ‘port upgrade outdated’ shouldn’t change that. Doesn’t make sense. That is exactly the problem

Re: port upgrade outdated fails

first place? > > gcc9 default the default when it was release, last year. > > Its up to you what you do here. either use gcc8, or gcc9. not a mixture of > both. > > Chris > If the port was built with the gcc8 variant, ‘port upgrade outdated’ shouldn’t change that. Doesn’t make sense.

Re: port upgrade outdated fails

Do what it says. Install arpack and mpich-default with the same fortran variants. Most probably you have mpich-default installed with the older gcc8 variant active, so just uninstall it and then reinstall with the new default, which is gcc9. Chris It’s not that simple, there are several

Re: port upgrade outdated fails

Sent from my iPhone > On Aug 27, 2019, at 3:53 AM, Chris Jones wrote: > > > >> On 27/08/2019 12:36 am, Mark Brethen wrote: >> ---> Computing dependencies for arpack >> ---> Fetching distfiles for arpack >> Warning: Your DNS servers incorrectly claim to know the address of >> nonexistent

Re: port upgrade outdated fails

On 27/08/2019 12:36 am, Mark Brethen wrote: --->  Computing dependencies for arpack --->  Fetching distfiles for arpack Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports. See this page for more

port upgrade outdated fails

---> Computing dependencies for arpack ---> Fetching distfiles for arpack Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports. See this page for more information:

Re: Port Upgrade Outdated Failure

On 07/27/2018, at 11:13, Christopher Stone mailto:listmeis...@thestoneforge.com>> wrote: > Self-update seems to have run fine, but the upgrade outdated process is a > complete fail. __ Thanks to Christopher Jones and Ryan

Re: Port Upgrade Outdated Failure

> sudo port -f uninstall cctools >> sudo port install cctools > > cheers Chris > >> On 27 Jul 2018, at 5:13 pm, Christopher Stone >> wrote: >> >> Hey Folks, >> >> I just ran `port selfupdate` and then `port upgrade outdated`. >> >> S

Re: port upgrade outdated reports weird problems with deadline and poplar

> On Aug 6, 2017, at 14:59, Ryan Schmidt wrote: > > >> On Aug 4, 2017, at 20:36, Richard L. Hamilton wrote: >> >> Some notes of mine on /usr/local: I can't avoid /usr/local entirely, since >> VirtualBox and Parallels install their command line

Re: port upgrade outdated reports weird problems with deadline and poplar

Some notes of mine on /usr/local: I can't avoid /usr/local entirely, since VirtualBox and Parallels install their command line tools there. But I can move /usr/local out of the way, for the duration of MacPorts builds, as necessary. More precisely, with System Integrity Protection turned

Re: port upgrade outdated reports weird problems with deadline and poplar

d will not use readline. It has nothing to do with ports you install. > * I next ran $ sudo port upgrade outdated which resulted in: > > ---> Computing dependencies for poppler > ---> Fetching archive for poppler > ---> Attempting to fetch poppler-0.56.0_0.darwin_15.x86_64.