Re: Help with testing of PR 12705 (macOS 10.13 High Sierra)

2021-10-30 Thread Vadim-Valdis Yudaev
I tested this in a virtual machine (macOS 10.13.6), it works well.

> On Oct 29, 2021, at 17:57, Vadim-Valdis Yudaev  wrote:
> 
> Help check if lua-language-server builds successfully for macOS 10.13.
> 
> In terms of what's needed:
> * Update the Portfile for lua-language-server, per the PR on macOS 10.13
> * Runt `sudo port build lua-language-server`
> * Wait for the build
> 
> PR: https://github.com/macports/macports-ports/pull/12705
> Portfile: 
> https://github.com/macports/macports-ports/blob/56a4d1caee70a6650359992a6a6f30c17d6176ea/lua/lua-language-server/Portfile
> 
> - Vadim-Valdis Yudaev



Re: Warning: The macOS 12 SDK does not appear to be installed. Ports may not build correctly.

2021-10-30 Thread Joshua Root

On 2021-10-31 10:04 , Daniel J. Luke wrote:

On Oct 30, 2021, at 5:25 PM, Nils Breunese  wrote:

But I indeed don’t seem to have an SDK for macOS 12:

So far I haven’t had any ports not building correctly. Is this a known issue? 
Does it have a known solution?


Yes - you can fix it by re-installing the command line tools:

https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt

(this happened to me on upgrade to macOS 12 as well).



I'd encourage everyone affected by this issue to use Feedback Assistant 
to let Apple know that you would like it fixed.


- Josh


Re: Warning: The macOS 12 SDK does not appear to be installed. Ports may not build correctly.

2021-10-30 Thread Daniel J. Luke
On Oct 30, 2021, at 5:25 PM, Nils Breunese  wrote:
> But I indeed don’t seem to have an SDK for macOS 12:
> 
> So far I haven’t had any ports not building correctly. Is this a known issue? 
> Does it have a known solution?

Yes - you can fix it by re-installing the command line tools:

https://trac.macports.org/wiki/ProblemHotlist#reinstall-clt

(this happened to me on upgrade to macOS 12 as well).

-- 
Daniel J. Luke



Warning: The macOS 12 SDK does not appear to be installed. Ports may not build correctly.

2021-10-30 Thread Nils Breunese
Hello all,

Today I upgraded my personal machine from macOS Big Sur to Monterey and I 
installed the Monterey version of MacPorts, and upgraded all my installed 
ports, which reinstalled them for Darwin 21.

I also see get this message very frequently when running `port` commands:


Warning: The macOS 12 SDK does not appear to be installed. Ports may not build 
correctly.
Warning: You can install it as part of the Xcode Command Line Tools package by 
running `xcode-select --install’.


When I run `xcode-select --install` I get:


xcode-select: error: command line tools are already installed, use "Software 
Update" to install updates


But I indeed don’t seem to have an SDK for macOS 12:


~ ❯ ls -l /Library/Developer/CommandLineTools/SDKs 
total 0
lrwxr-xr-x  1 root  wheel   14 12 mei 18:37 MacOSX.sdk -> MacOSX11.3.sdk
drwxr-xr-x  7 root  wheel  224 17 aug  2020 MacOSX10.14.sdk
drwxr-xr-x  8 root  wheel  256  1 feb  2021 MacOSX10.15.sdk
drwxr-xr-x  7 root  wheel  224 16 mrt  2021 MacOSX11.3.sdk
lrwxr-xr-x  1 root  wheel   14 12 mei 18:35 MacOSX11.sdk -> MacOSX11.3.sdk


So far I haven’t had any ports not building correctly. Is this a known issue? 
Does it have a known solution?

Nils.

Re: Problems with configure on revived HandBrake port

2021-10-30 Thread Joshua Root

On 2021-10-30 20:54 , Janosch Peters via macports-dev wrote:
I am trying to revive the HandBrake port: 
https://github.com/Janosch/macports-ports/blob/handbrake-update/multimedia/HandBrake/Portfile


It currently fails while trying to probe for xcodebuild:

version probe: xcodebuild 10.3.0...(fail) 0.0.0
     Command failed: cd 
"/opt/local/var/macports/build/_Users_janosch_Dev_macports-ports_multimedia_HandBrake/HandBrake/work/HandBrake-1.4.2-source" 
&& ./configure --prefix=/opt/local


The strange thing is, if I run this command manually, it works:

     cd 
"/opt/local/var/macports/build/_Users_janosch_Dev_macports-ports_multimedia_HandBrake/HandBrake/work/HandBrake-1.4.2-source" 
&& ./configure --prefix=/opt/local

     version probe: xcodebuild 10.3.0...(pass) 12.4


I don't know what could be the cause of this behavior. The configure 
script is a bash script calling a python script. I also don't know how I 
can debug this, as running the command manually works.


Any ideas?


If it uses xcodebuild, you would need to set 'use_xcode yes'.

- Josh


Problems with configure on revived HandBrake port

2021-10-30 Thread Janosch Peters via macports-dev
I am trying to revive the HandBrake port: 
https://github.com/Janosch/macports-ports/blob/handbrake-update/multimedia/HandBrake/Portfile


It currently fails while trying to probe for xcodebuild:

version probe: xcodebuild 10.3.0...(fail) 0.0.0
    Command failed: cd 
"/opt/local/var/macports/build/_Users_janosch_Dev_macports-ports_multimedia_HandBrake/HandBrake/work/HandBrake-1.4.2-source" 
&& ./configure --prefix=/opt/local


The strange thing is, if I run this command manually, it works:

    cd 
"/opt/local/var/macports/build/_Users_janosch_Dev_macports-ports_multimedia_HandBrake/HandBrake/work/HandBrake-1.4.2-source" 
&& ./configure --prefix=/opt/local

    version probe: xcodebuild 10.3.0...(pass) 12.4


I don't know what could be the cause of this behavior. The configure 
script is a bash script calling a python script. I also don't know how I 
can debug this, as running the command manually works.


Any ideas?


- Janosch


Re: ports.macports.org - sync broken?

2021-10-30 Thread Arjun Salyan



> On 27-Oct-2021, at 5:32 PM, Christopher Nielsen  
> wrote:
> 
> Thanks Arjun, looking much better now.
> 
> One other observation though: Prior to this, the “Maintained by Me” and 
> “Watched by Me” pages were incredibly responsive, and would refresh/update 
> almost instantly. Now, however, it seems to take up to 10 seconds on a 
> refresh.
> 
> Initially I chalked it up to the site warming up, after the fix was initially 
> released. But a few days later, that’s still the case. Has something changed, 
> to cause a slowdown?

Right, it went too slow. The builds table is becoming very large and I believe 
after the `ALTER` we did to fix the syncing might have had increased the 
obsolete data. Doing a VACUUM ANALYZE of the builds table has brought back 
performance to normal.

I will setup aggressive auto-vacuum for this table.

Thanks