Re: Bug in curl Variant +http3?
On Jun 12, 2024, at 13:49, Eric Hoch wrote: > > Shall I file a bug report for this? Yes, you should file a bug report with the developers of curl.
Bug in curl Variant +http3?
Hey all,
for a current project I wanted to test my scripts with curl using http3.
The curl that ships with macOS 14.5 doesn't support http3, I installed
curl with the variant +htttp3.
The most basic command being something like
curl --http3 https://blog.cloudflare.com -I
works.
Other commands like
curl -Is -w '%header{location}' -o /dev/null
https://github.com/SAP/macOS-icon-generator/releases/latest
don't work. I get an empty output and an exit code 43.
During the build phase for the curl +http3 variant I get this warning:
Warning: Configuration logfiles contain indications of
-Wimplicit-function-declaration; check that features were not
accidentally disabled:
getpass_r: found in curl-8.8.0/config.log
_fseeki64: found in curl-8.8.0/config.log
IoctlSocket: found in curl-8.8.0/config.log
ioctlsocket: found in curl-8.8.0/config.log
memrchr: found in curl-8.8.0/config.log
CloseSocket: found in curl-8.8.0/config.log
closesocket: found in curl-8.8.0/config.log
Using the default macports curl +ssl variant the above command
curl -Is -w '%header{location}' -o /dev/null
https://github.com/SAP/macOS-icon-generator/releases/latest
gives me the expected output of
https://github.com/SAP/macOS-icon-generator/releases/tag/2.0.0
The difference for the two variants is the TLS library which is gnutls
for http3 and OpenSSL for the default curl.
On github there is this static curl
https://github.com/stunnel/static-curl for macOS which uses openssl,
supports http3 and works as expected.
I found this blog entry
https://daniel.haxx.se/blog/2024/06/10/http-3-in-curl-mid-2024/ which
explains to me that using openssl for http3 isn't easy and the best
choice for http3. Therefore I understand using gnutls for http3 what I
don't understand is that curl commands using the -w option break with
gnutls and http3. Shall I file a bug report for this?
As macOS curl doesn't support http3 I won't use http3 in my script as
this script needs to run on macs that don't have macports or brew
installed or download curl from the above github.
Eric
Re: Call for testing: port migrate
Damn, I just upgraded to Sequoia and did the old way - had some trouble so I might try again. —Mark On Wed, Jun 12, 2024, at 6:26 AM, Joshua Root wrote: > Hi Franco, > > Thanks for testing, and good to hear it went well. > > - Josh > > On 12/6/2024 19:41, Franco Vaccari wrote: > > Happy to report that the migration went smoothly. Just one port > > installation finished in error (grass, and looking at the port health that > > was expected, so also qgis3 +grass wasn’t migrated) but that didn’t prevent > > the migration to complete for all other ports (944 of them). > > > > All this on a MacBook Pro with M1 processor, macOS Sonoma 14.5, Xcode 15.4 > > and its CLT’s. > > > > So, all in all, a very positive experience. > > > > Thanks to the MacPorts team! > > > > Ciao > > > > Franco > > > >> On 12 Jun 2024, at 09:46, Franco Vaccari via macports-users > >> wrote: > >> > >> Dear Josh, > >> > >> since your mail caught me a few minutes after updating from Ventura to > >> Sonoma, and a few seconds before I started to play with MacPorts > >> migration, I felt obliged to give the migrate command a shot… > >> > >> Currently computing dependency order. Will let you know the outcome… > >> > >> Ciao > >> > >> Franco > >> > >>> On 12 Jun 2024, at 09:00, Joshua Root wrote: > >>> > >>> A 'migrate' action has been added to MacPorts base in git on the master > >>> branch. If you are comfortable with checking out the git repo, installing > >>> MacPorts from source, running potentially buggy pre-release code, and > >>> reporting any issues, we would greatly appreciate you giving it a try. > >>> > >>> The new action automates all parts of the existing Migration procedure > >>> apart from updating Xcode and the CLTs. After updating your OS to a new > >>> major version or transferring to a new machine with a different CPU > >>> architecture, you should be able to simply run: > >>> > >>> sudo port migrate > >>> > >>> and MacPorts base will first be rebuilt, and then all ports that need to > >>> be reinstalled to be compatible with your current system will be. Build > >>> failures should be handled as gracefully as possible and reported at the > >>> end. > >>> > >>> Thanks to Umesh Singla for doing the initial work on this feature, and to > >>> Clemens Lang for doing much of the work of completing and updating the > >>> code. > >>> > >>> - Josh > >> > > > >
Re: Call for testing: port migrate
Hi Franco, Thanks for testing, and good to hear it went well. - Josh On 12/6/2024 19:41, Franco Vaccari wrote: Happy to report that the migration went smoothly. Just one port installation finished in error (grass, and looking at the port health that was expected, so also qgis3 +grass wasn’t migrated) but that didn’t prevent the migration to complete for all other ports (944 of them). All this on a MacBook Pro with M1 processor, macOS Sonoma 14.5, Xcode 15.4 and its CLT’s. So, all in all, a very positive experience. Thanks to the MacPorts team! Ciao Franco On 12 Jun 2024, at 09:46, Franco Vaccari via macports-users wrote: Dear Josh, since your mail caught me a few minutes after updating from Ventura to Sonoma, and a few seconds before I started to play with MacPorts migration, I felt obliged to give the migrate command a shot… Currently computing dependency order. Will let you know the outcome… Ciao Franco On 12 Jun 2024, at 09:00, Joshua Root wrote: A 'migrate' action has been added to MacPorts base in git on the master branch. If you are comfortable with checking out the git repo, installing MacPorts from source, running potentially buggy pre-release code, and reporting any issues, we would greatly appreciate you giving it a try. The new action automates all parts of the existing Migration procedure apart from updating Xcode and the CLTs. After updating your OS to a new major version or transferring to a new machine with a different CPU architecture, you should be able to simply run: sudo port migrate and MacPorts base will first be rebuilt, and then all ports that need to be reinstalled to be compatible with your current system will be. Build failures should be handled as gracefully as possible and reported at the end. Thanks to Umesh Singla for doing the initial work on this feature, and to Clemens Lang for doing much of the work of completing and updating the code. - Josh
Re: Call for testing: port migrate
Happy to report that the migration went smoothly. Just one port installation finished in error (grass, and looking at the port health that was expected, so also qgis3 +grass wasn’t migrated) but that didn’t prevent the migration to complete for all other ports (944 of them). All this on a MacBook Pro with M1 processor, macOS Sonoma 14.5, Xcode 15.4 and its CLT’s. So, all in all, a very positive experience. Thanks to the MacPorts team! Ciao Franco > On 12 Jun 2024, at 09:46, Franco Vaccari via macports-users > wrote: > > Dear Josh, > > since your mail caught me a few minutes after updating from Ventura to > Sonoma, and a few seconds before I started to play with MacPorts migration, I > felt obliged to give the migrate command a shot… > > Currently computing dependency order. Will let you know the outcome… > > Ciao > > Franco > >> On 12 Jun 2024, at 09:00, Joshua Root wrote: >> >> A 'migrate' action has been added to MacPorts base in git on the master >> branch. If you are comfortable with checking out the git repo, installing >> MacPorts from source, running potentially buggy pre-release code, and >> reporting any issues, we would greatly appreciate you giving it a try. >> >> The new action automates all parts of the existing Migration procedure apart >> from updating Xcode and the CLTs. After updating your OS to a new major >> version or transferring to a new machine with a different CPU architecture, >> you should be able to simply run: >> >> sudo port migrate >> >> and MacPorts base will first be rebuilt, and then all ports that need to be >> reinstalled to be compatible with your current system will be. Build >> failures should be handled as gracefully as possible and reported at the end. >> >> Thanks to Umesh Singla for doing the initial work on this feature, and to >> Clemens Lang for doing much of the work of completing and updating the code. >> >> - Josh >
Re: Call for testing: port migrate
Dear Josh, since your mail caught me a few minutes after updating from Ventura to Sonoma, and a few seconds before I started to play with MacPorts migration, I felt obliged to give the migrate command a shot… Currently computing dependency order. Will let you know the outcome… Ciao Franco > On 12 Jun 2024, at 09:00, Joshua Root wrote: > > A 'migrate' action has been added to MacPorts base in git on the master > branch. If you are comfortable with checking out the git repo, installing > MacPorts from source, running potentially buggy pre-release code, and > reporting any issues, we would greatly appreciate you giving it a try. > > The new action automates all parts of the existing Migration procedure apart > from updating Xcode and the CLTs. After updating your OS to a new major > version or transferring to a new machine with a different CPU architecture, > you should be able to simply run: > > sudo port migrate > > and MacPorts base will first be rebuilt, and then all ports that need to be > reinstalled to be compatible with your current system will be. Build failures > should be handled as gracefully as possible and reported at the end. > > Thanks to Umesh Singla for doing the initial work on this feature, and to > Clemens Lang for doing much of the work of completing and updating the code. > > - Josh
Call for testing: port migrate
A 'migrate' action has been added to MacPorts base in git on the master branch. If you are comfortable with checking out the git repo, installing MacPorts from source, running potentially buggy pre-release code, and reporting any issues, we would greatly appreciate you giving it a try. The new action automates all parts of the existing Migration procedure apart from updating Xcode and the CLTs. After updating your OS to a new major version or transferring to a new machine with a different CPU architecture, you should be able to simply run: sudo port migrate and MacPorts base will first be rebuilt, and then all ports that need to be reinstalled to be compatible with your current system will be. Build failures should be handled as gracefully as possible and reported at the end. Thanks to Umesh Singla for doing the initial work on this feature, and to Clemens Lang for doing much of the work of completing and updating the code. - Josh
