From nyall.dawson at gmail.com  Sun Nov  9 17:34:59 2025
From: nyall.dawson at gmail.com (Nyall Dawson)
Date: Mon, 10 Nov 2025 11:34:59 +1000
Subject: [Qgis-psc] 2025 Grant: Coverity Scan cleanup final report
Message-ID: <CAB28AsgdRfPWm7osA+u=HvavMsKJHy+PAHWdaQCpVFKZxjTUBA@mail.gmail.com>

Hi PSC,

I'd like to report the successful conclusion of the 2025 funding grant for
QEP 337: Coverity Scan
cleanup!

As detailed in the original proposal, this project has seen a massive
cleanup to the QGIS code base via hundreds of fixes to issues reported by
the Coverity Scan tool.

>From the original 1075 issues identified by Coverity Scan at the start of
the project, we are now down to 145 remaining outstanding issues. All false
positive issues have been marked accordingly, and many fixes submitted to
QGIS to remedy valid issues in the QGIS code.

The remaining issues are either non-trivial to fix (i.e. requiring large
architectural changes) or ambiguous (in that the original intention of the
code is not clear, and I'm unable to determine if the issues are valid or
working as expected). It is hoped that by clearing out the bulk of the
Coverity results, future bug fixing efforts will be able to focus attention
on these remaining issues and eventually lead to QGIS achieving "Coverity
Clean" status.

All applicable (and safe!) fixes have been backported to stable QGIS
releases too.

As part of this project, several downstream projects also saw fixes
submitted:

- The MDAL library is now completely "coverity clean", with no outstanding
issues remaining. Coverity Scan is now run on the MDAL codebase on a weekly
basis, in order to quickly identify and remedy any issues in any newly
introduced code.
- Fixes and performance improvements have been submitted to the laz-perf,
untwine, PDAL wrench and tinygltf libraries.

As detailed in the original proposal, an investigation was also conducted
to determine whether it is possible to automatically run the Coverity Scan
tool on a weekly basis as a GitHub action for QGIS. My finding was that
this is NOT possible to achieve via GitHub actions, as the compilation
using the coverity cov-build tool ends up exceeding the maximum available
space on the workflow runners. (see
https://github.com/nyalldawson/QGIS/tree/coverity_workflow for the
attempted workflow configuration).

While not part of the original proposal or grant, I will continue to run
Coverity Scan on an ad-hoc basis on the QGIS codebase in order to quickly
identify and resolve any newly introduced issues.

My thanks to the PSC and QGIS sponsors for making this work possible!

Kind regards,
Nyall
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20251110/16176bdf/attachment-0001.htm>

From regis at qgis.org  Mon Nov 10 06:02:10 2025
From: regis at qgis.org (=?ISO-8859-1?Q?R=E9gis_Haubourg?=)
Date: Mon, 10 Nov 2025 15:02:10 +0100
Subject: [Qgis-psc] 2025 Grant: Coverity Scan cleanup final report
In-Reply-To: <CAB28AsgdRfPWm7osA+u=HvavMsKJHy+PAHWdaQCpVFKZxjTUBA@mail.gmail.com>
References: <CAB28AsgdRfPWm7osA+u=HvavMsKJHy+PAHWdaQCpVFKZxjTUBA@mail.gmail.com>
Message-ID: <1CEB6EAB-1463-4B51-9881-8A7C0CB0AC8B@qgis.org>

Thanks a lot for this work Nyall. 
As regulations arise on cyber security increase, we will clearly need to find workarounds for the GitHub actions limitations. Those regulations will make it mandatory to prove we have automated scan running, on a regular basis or per continuous integration processes 
Some tests have already been made with dedicated machines to see if hosting our own runners would help.

With your insights we know that static analyzers will need resources. 
Do you have rough estimates of what specifications are required for disk space, memory and CPU so that we can run with comfort and maybe on a daily or weekly basis? 

Great work again. 
Cheers
R?gis 

Le 10 novembre 2025 02:34:59 GMT+01:00, Nyall Dawson via QGIS-PSC <qgis-psc at lists.osgeo.org> a ?crit?:
>Hi PSC,
>
>I'd like to report the successful conclusion of the 2025 funding grant for
>QEP 337: Coverity Scan
>cleanup!
>
>As detailed in the original proposal, this project has seen a massive
>cleanup to the QGIS code base via hundreds of fixes to issues reported by
>the Coverity Scan tool.
>
>From the original 1075 issues identified by Coverity Scan at the start of
>the project, we are now down to 145 remaining outstanding issues. All false
>positive issues have been marked accordingly, and many fixes submitted to
>QGIS to remedy valid issues in the QGIS code.
>
>The remaining issues are either non-trivial to fix (i.e. requiring large
>architectural changes) or ambiguous (in that the original intention of the
>code is not clear, and I'm unable to determine if the issues are valid or
>working as expected). It is hoped that by clearing out the bulk of the
>Coverity results, future bug fixing efforts will be able to focus attention
>on these remaining issues and eventually lead to QGIS achieving "Coverity
>Clean" status.
>
>All applicable (and safe!) fixes have been backported to stable QGIS
>releases too.
>
>As part of this project, several downstream projects also saw fixes
>submitted:
>
>- The MDAL library is now completely "coverity clean", with no outstanding
>issues remaining. Coverity Scan is now run on the MDAL codebase on a weekly
>basis, in order to quickly identify and remedy any issues in any newly
>introduced code.
>- Fixes and performance improvements have been submitted to the laz-perf,
>untwine, PDAL wrench and tinygltf libraries.
>
>As detailed in the original proposal, an investigation was also conducted
>to determine whether it is possible to automatically run the Coverity Scan
>tool on a weekly basis as a GitHub action for QGIS. My finding was that
>this is NOT possible to achieve via GitHub actions, as the compilation
>using the coverity cov-build tool ends up exceeding the maximum available
>space on the workflow runners. (see
>https://github.com/nyalldawson/QGIS/tree/coverity_workflow for the
>attempted workflow configuration).
>
>While not part of the original proposal or grant, I will continue to run
>Coverity Scan on an ad-hoc basis on the QGIS codebase in order to quickly
>identify and resolve any newly introduced issues.
>
>My thanks to the PSC and QGIS sponsors for making this work possible!
>
>Kind regards,
>Nyall
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20251110/0da8aeed/attachment.htm>

From nyall.dawson at gmail.com  Mon Nov 10 16:16:41 2025
From: nyall.dawson at gmail.com (Nyall Dawson)
Date: Tue, 11 Nov 2025 10:16:41 +1000
Subject: [Qgis-psc] 2025 Grant: Coverity Scan cleanup final report
In-Reply-To: <1CEB6EAB-1463-4B51-9881-8A7C0CB0AC8B@qgis.org>
References: <CAB28AsgdRfPWm7osA+u=HvavMsKJHy+PAHWdaQCpVFKZxjTUBA@mail.gmail.com>
 <1CEB6EAB-1463-4B51-9881-8A7C0CB0AC8B@qgis.org>
Message-ID: <CAB28AsjaHv6CEvw8KxGFfezmgWYW3jELHabkwwzd_3-9g+038w@mail.gmail.com>

On Tue, 11 Nov 2025 at 00:02, R?gis Haubourg <regis at qgis.org> wrote:
>
> Thanks a lot for this work Nyall.
> As regulations arise on cyber security increase, we will clearly need to
find workarounds for the GitHub actions limitations. Those regulations will
make it mandatory to prove we have automated scan running, on a regular
basis or per continuous integration processes
> Some tests have already been made with dedicated machines to see if
hosting our own runners would help.
>
> With your insights we know that static analyzers will need resources.
> Do you have rough estimates of what specifications are required for disk
space, memory and CPU so that we can run with comfort and maybe on a daily
or weekly basis?

Hmm, good question. As far as disk space goes:

- QGIS source is ~5gb
- The coverity build tool itself is ~2.5gb
- The build folder when building using coverity ends up around 30gb total
(including the cov-int internal database)
- The cov-int folder needs to be compressed before submission to coverity,
which ends up ~10gb

So we're looking for at least 50GB space on top of the base environment
(with all dependencies installed). I'd probably allow at least another 10gb
swap space there too, depending on the available memory.

On the github runner (4x CPU, 16 GB RAM) the coverity build aborts at
around the 6 hour mark, at around 75% completion. If the system had similar
CPU/memory then I'd estimate the workflow would take around 8-10 hours
total (for completion of the build, compression of the results, and
submission to Coverity). For reference, on my local machine (64GB RAM, AMD
Ryzen 9 5950X 16-Core Processor) a full Coverity build takes about 30
minutes (plus another 45 minutes to submit the 10gb compressed results to
Coverity, but that's likely just my slow internet connection! ?).

Hope that helps!
Nyall




>
> Great work again.
> Cheers
> R?gis
>
>
> Le 10 novembre 2025 02:34:59 GMT+01:00, Nyall Dawson via QGIS-PSC <
qgis-psc at lists.osgeo.org> a ?crit :
>>
>> Hi PSC,
>>
>> I'd like to report the successful conclusion of the 2025 funding grant
for QEP 337: Coverity Scan
>> cleanup!
>>
>> As detailed in the original proposal, this project has seen a massive
cleanup to the QGIS code base via hundreds of fixes to issues reported by
the Coverity Scan tool.
>>
>> From the original 1075 issues identified by Coverity Scan at the start
of the project, we are now down to 145 remaining outstanding issues. All
false positive issues have been marked accordingly, and many fixes
submitted to QGIS to remedy valid issues in the QGIS code.
>>
>> The remaining issues are either non-trivial to fix (i.e. requiring large
architectural changes) or ambiguous (in that the original intention of the
code is not clear, and I'm unable to determine if the issues are valid or
working as expected). It is hoped that by clearing out the bulk of the
Coverity results, future bug fixing efforts will be able to focus attention
on these remaining issues and eventually lead to QGIS achieving "Coverity
Clean" status.
>>
>> All applicable (and safe!) fixes have been backported to stable QGIS
releases too.
>>
>> As part of this project, several downstream projects also saw fixes
submitted:
>>
>> - The MDAL library is now completely "coverity clean", with no
outstanding issues remaining. Coverity Scan is now run on the MDAL codebase
on a weekly basis, in order to quickly identify and remedy any issues in
any newly introduced code.
>> - Fixes and performance improvements have been submitted to the
laz-perf, untwine, PDAL wrench and tinygltf libraries.
>>
>> As detailed in the original proposal, an investigation was also
conducted to determine whether it is possible to automatically run the
Coverity Scan tool on a weekly basis as a GitHub action for QGIS. My
finding was that this is NOT possible to achieve via GitHub actions, as the
compilation using the coverity cov-build tool ends up exceeding the maximum
available space on the workflow runners. (see
https://github.com/nyalldawson/QGIS/tree/coverity_workflow for the
attempted workflow configuration).
>>
>> While not part of the original proposal or grant, I will continue to run
Coverity Scan on an ad-hoc basis on the QGIS codebase in order to quickly
identify and resolve any newly introduced issues.
>>
>> My thanks to the PSC and QGIS sponsors for making this work possible!
>>
>> Kind regards,
>> Nyall
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20251111/bb2deca3/attachment.htm>

From regis.haubourg at gmail.com  Tue Nov 11 02:46:33 2025
From: regis.haubourg at gmail.com (=?UTF-8?Q?R=C3=A9gis_Haubourg?=)
Date: Tue, 11 Nov 2025 11:46:33 +0100
Subject: [Qgis-psc] 2025 Grant: Coverity Scan cleanup final report
In-Reply-To: <CAB28AsjaHv6CEvw8KxGFfezmgWYW3jELHabkwwzd_3-9g+038w@mail.gmail.com>
References: <CAB28AsgdRfPWm7osA+u=HvavMsKJHy+PAHWdaQCpVFKZxjTUBA@mail.gmail.com>
 <1CEB6EAB-1463-4B51-9881-8A7C0CB0AC8B@qgis.org>
 <CAB28AsjaHv6CEvw8KxGFfezmgWYW3jELHabkwwzd_3-9g+038w@mail.gmail.com>
Message-ID: <68330ade-628d-47a0-96ad-ef6f1cba7940@gmail.com>

On 11/11/25 01:16, Nyall Dawson via QGIS-PSC wrote:
> On the github runner (4x CPU, 16 GB RAM) the coverity build aborts at 
> around the 6 hour mark, at around 75% completion. If the system had 
> similar CPU/memory then I'd estimate the workflow would take around 
> 8-10 hours total (for completion of the build, compression of the 
> results, and submission to Coverity). For reference, on my local 
> machine (64GB RAM, AMD Ryzen 9 5950X 16-Core Processor) a full 
> Coverity build takes about 30 minutes (plus another 45 minutes to 
> submit the 10gb compressed results to Coverity, but that's likely just 
> my slow internet connection!??).

Thanks a lot Nyall. That confirms we would gain a lot using powerful 
machines for building QGIS and running those scans.

We'll discuss that

Cheers



From matthias at opengis.ch  Tue Nov 18 22:56:16 2025
From: matthias at opengis.ch (Matthias Kuhn)
Date: Wed, 19 Nov 2025 07:56:16 +0100
Subject: [Qgis-psc] QGIS macOS builds for 3.44
Message-ID: <CAC7zN95dVvgKjbT82e0UT-_oRORnO3LEm5H0mgcYHCFBM1se2g@mail.gmail.com>

Dear PSC,

I have worked on macOS builds for QGIS 3.44.

These builds include:

 - Recent dependencies (see below)
 - Native Intel and arm support (universal binaries)
 - Packaged as a dmg installer
 - Notarized with OSGeo certificates

The source code had to be heavily patched with backports from code that was
merged to master only after QGIS 3.44 had been branched.
The build pipeline
<https://github.com/m-kuhn/QGIS/tree/refs/heads/qt5-qgis-3-44> for QGIS
3.44 is therefore something I do not intend to merge into the release-3_44
branch and therefore have it on my own fork and the build can be downloaded
from there too:

QGIS 3.44.4 download:
https://github.com/m-kuhn/QGIS/releases/download/final-3_44_4/QGIS-final-3_44_4.dmg
.

Notarization is now done using an OSGeo certificate (big thanks to Michael
Smith for the support).

- The notarization for Qt6 nightly builds (and future QGIS 4 releases) is
done in github actions in this repository
https://github.com/qgis/qgis-notarize
- The notarization for Qt5 based QGIS 3.44 releases is done in this
repository https://github.com/m-kuhn/qgis-notarize

There are still a few limitations which have come up in our internal
testing, most notably UI translation isn't working yet.
Furthermore, there has been a request to bundle more python for data
science ().
I am still working on addressing these shortcomings, I expect more requests
to come up which I'll address as time permits.

Since there are no officially maintained macOS releases available at the
moment, I would like to publish these on the official QGIS download page.
To publish the packages to the download page, I'd be happy to get some
support (uploading to a server / changing download links). Who would be the
right person to talk to?

Thanks a lot for trusting me with this task.

Kind regards
Matthias

Qt version

5.15.18

Python version

3.12.11

GDAL version

3.11.4 ? Eganville

PROJ version

9.7.0

EPSG Registry database version

v12.022 (2025-08-30)

GEOS version

3.14.1-CAPI-1.20.5

SQLite version

3.50.4

PDAL version

2.9.2

PostgreSQL client version

16.9

SpatiaLite version

5.1.0

QWT version

6.2.1

QScintilla2 version

2.13.4

-- 
[image: OG]
<https://link.bulksignature.com/4054a10b-3c19-46a2-9e27-813335d7dbdc>

*Matthias Kuhn*
Mr. Noproblemo

CTO | Co-Founder
[image: email]
matthias at opengis.ch

[image: www]
opengis.ch

[image: linkedin] <https://www.linkedin.com/company/opengisch/> [image:
mastodon] <https://fosstodon.org/@opengisch> [image: github]
<https://github.com/opengisch/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20251119/6859ae5f/attachment-0001.htm>

From andreas at qgis.org  Wed Nov 19 00:36:29 2025
From: andreas at qgis.org (Andreas Neumann)
Date: Wed, 19 Nov 2025 09:36:29 +0100
Subject: [Qgis-psc] QGIS macOS builds for 3.44
In-Reply-To: <CAC7zN95dVvgKjbT82e0UT-_oRORnO3LEm5H0mgcYHCFBM1se2g@mail.gmail.com>
References: <CAC7zN95dVvgKjbT82e0UT-_oRORnO3LEm5H0mgcYHCFBM1se2g@mail.gmail.com>
Message-ID: <CAB2Z92Bo-aggA3fCsnqmpj4AFgSE8uxHS89Tou5kRQ9xnHjX0A@mail.gmail.com>

Hi Matthias,

This is great news. Thanks for your efforts!

I have two questions:

- we still have a MacOS server at Untangled. Are you actively using this
server or could we cancel/shutdown this server?
- once you consider the notarized Qt5 QGIS 3.44 stable - could we
officially host it at the QGIS website?

Thank you very much,
Andreas


On Wed, 19 Nov 2025 at 07:56, Matthias Kuhn via QGIS-PSC <
qgis-psc at lists.osgeo.org> wrote:

> Dear PSC,
>
> I have worked on macOS builds for QGIS 3.44.
>
> These builds include:
>
>  - Recent dependencies (see below)
>  - Native Intel and arm support (universal binaries)
>  - Packaged as a dmg installer
>  - Notarized with OSGeo certificates
>
> The source code had to be heavily patched with backports from code that
> was merged to master only after QGIS 3.44 had been branched.
> The build pipeline
> <https://github.com/m-kuhn/QGIS/tree/refs/heads/qt5-qgis-3-44> for QGIS
> 3.44 is therefore something I do not intend to merge into the release-3_44
> branch and therefore have it on my own fork and the build can be downloaded
> from there too:
>
> QGIS 3.44.4 download:
> https://github.com/m-kuhn/QGIS/releases/download/final-3_44_4/QGIS-final-3_44_4.dmg
> .
>
> Notarization is now done using an OSGeo certificate (big thanks to Michael
> Smith for the support).
>
> - The notarization for Qt6 nightly builds (and future QGIS 4 releases) is
> done in github actions in this repository
> https://github.com/qgis/qgis-notarize
> - The notarization for Qt5 based QGIS 3.44 releases is done in this
> repository https://github.com/m-kuhn/qgis-notarize
>
> There are still a few limitations which have come up in our internal
> testing, most notably UI translation isn't working yet.
> Furthermore, there has been a request to bundle more python for data
> science ().
> I am still working on addressing these shortcomings, I expect more
> requests to come up which I'll address as time permits.
>
> Since there are no officially maintained macOS releases available at the
> moment, I would like to publish these on the official QGIS download page.
> To publish the packages to the download page, I'd be happy to get some
> support (uploading to a server / changing download links). Who would be the
> right person to talk to?
>
> Thanks a lot for trusting me with this task.
>
> Kind regards
> Matthias
>
> Qt version
>
> 5.15.18
>
> Python version
>
> 3.12.11
>
> GDAL version
>
> 3.11.4 ? Eganville
>
> PROJ version
>
> 9.7.0
>
> EPSG Registry database version
>
> v12.022 (2025-08-30)
>
> GEOS version
>
> 3.14.1-CAPI-1.20.5
>
> SQLite version
>
> 3.50.4
>
> PDAL version
>
> 2.9.2
>
> PostgreSQL client version
>
> 16.9
>
> SpatiaLite version
>
> 5.1.0
>
> QWT version
>
> 6.2.1
>
> QScintilla2 version
>
> 2.13.4
>
> --
> [image: OG]
> <https://link.bulksignature.com/4054a10b-3c19-46a2-9e27-813335d7dbdc>
>
> *Matthias Kuhn*
> Mr. Noproblemo
>
> CTO | Co-Founder
> [image: email]
> matthias at opengis.ch
>
> [image: www]
> opengis.ch
>
> [image: linkedin] <https://www.linkedin.com/company/opengisch/> [image:
> mastodon] <https://fosstodon.org/@opengisch> [image: github]
> <https://github.com/opengisch/>
> _______________________________________________
> QGIS-PSC mailing list
> QGIS-PSC at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>


-- 

--
Andreas Neumann
QGIS.ORG board member (treasurer)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20251119/4a0562c0/attachment.htm>

From matthias at opengis.ch  Wed Nov 19 00:41:20 2025
From: matthias at opengis.ch (Matthias Kuhn)
Date: Wed, 19 Nov 2025 09:41:20 +0100
Subject: [Qgis-psc] QGIS macOS builds for 3.44
In-Reply-To: <CAB2Z92Bo-aggA3fCsnqmpj4AFgSE8uxHS89Tou5kRQ9xnHjX0A@mail.gmail.com>
References: <CAC7zN95dVvgKjbT82e0UT-_oRORnO3LEm5H0mgcYHCFBM1se2g@mail.gmail.com>
 <CAB2Z92Bo-aggA3fCsnqmpj4AFgSE8uxHS89Tou5kRQ9xnHjX0A@mail.gmail.com>
Message-ID: <CAC7zN97jGyn+amE0vRcE7-jrn=+-vrD9QxbnWCfPgpN0Rgf3aQ@mail.gmail.com>

Hi Andreas,

- I do not use the macOS server (and I do not have access to it),
everything is done on github hosted macOS runners so far. I would be
interested in getting access to a macOS machine for a self-hosted runner
(particularly because building qtwebengine might be too much for the github
hosted ones). Is that server an arm based one?
- We can host it at the QGIS website at any time, I'll need some
instructions on how the interface to that server works. Who should this be
discussed with?

Best regards
Matthias

On Wed, Nov 19, 2025 at 9:36?AM Andreas Neumann <andreas at qgis.org> wrote:

> Hi Matthias,
>
> This is great news. Thanks for your efforts!
>
> I have two questions:
>
> - we still have a MacOS server at Untangled. Are you actively using this
> server or could we cancel/shutdown this server?
> - once you consider the notarized Qt5 QGIS 3.44 stable - could we
> officially host it at the QGIS website?
>
> Thank you very much,
> Andreas
>
>
> On Wed, 19 Nov 2025 at 07:56, Matthias Kuhn via QGIS-PSC <
> qgis-psc at lists.osgeo.org> wrote:
>
>> Dear PSC,
>>
>> I have worked on macOS builds for QGIS 3.44.
>>
>> These builds include:
>>
>>  - Recent dependencies (see below)
>>  - Native Intel and arm support (universal binaries)
>>  - Packaged as a dmg installer
>>  - Notarized with OSGeo certificates
>>
>> The source code had to be heavily patched with backports from code that
>> was merged to master only after QGIS 3.44 had been branched.
>> The build pipeline
>> <https://github.com/m-kuhn/QGIS/tree/refs/heads/qt5-qgis-3-44> for QGIS
>> 3.44 is therefore something I do not intend to merge into the release-3_44
>> branch and therefore have it on my own fork and the build can be downloaded
>> from there too:
>>
>> QGIS 3.44.4 download:
>> https://github.com/m-kuhn/QGIS/releases/download/final-3_44_4/QGIS-final-3_44_4.dmg
>> .
>>
>> Notarization is now done using an OSGeo certificate (big thanks to
>> Michael Smith for the support).
>>
>> - The notarization for Qt6 nightly builds (and future QGIS 4 releases) is
>> done in github actions in this repository
>> https://github.com/qgis/qgis-notarize
>> - The notarization for Qt5 based QGIS 3.44 releases is done in this
>> repository https://github.com/m-kuhn/qgis-notarize
>>
>> There are still a few limitations which have come up in our internal
>> testing, most notably UI translation isn't working yet.
>> Furthermore, there has been a request to bundle more python for data
>> science ().
>> I am still working on addressing these shortcomings, I expect more
>> requests to come up which I'll address as time permits.
>>
>> Since there are no officially maintained macOS releases available at the
>> moment, I would like to publish these on the official QGIS download page.
>> To publish the packages to the download page, I'd be happy to get some
>> support (uploading to a server / changing download links). Who would be the
>> right person to talk to?
>>
>> Thanks a lot for trusting me with this task.
>>
>> Kind regards
>> Matthias
>>
>> Qt version
>>
>> 5.15.18
>>
>> Python version
>>
>> 3.12.11
>>
>> GDAL version
>>
>> 3.11.4 ? Eganville
>>
>> PROJ version
>>
>> 9.7.0
>>
>> EPSG Registry database version
>>
>> v12.022 (2025-08-30)
>>
>> GEOS version
>>
>> 3.14.1-CAPI-1.20.5
>>
>> SQLite version
>>
>> 3.50.4
>>
>> PDAL version
>>
>> 2.9.2
>>
>> PostgreSQL client version
>>
>> 16.9
>>
>> SpatiaLite version
>>
>> 5.1.0
>>
>> QWT version
>>
>> 6.2.1
>>
>> QScintilla2 version
>>
>> 2.13.4
>>
>> --
>> [image: OG]
>> <https://link.bulksignature.com/4054a10b-3c19-46a2-9e27-813335d7dbdc>
>>
>> *Matthias Kuhn*
>> Mr. Noproblemo
>>
>> CTO | Co-Founder
>> [image: email]
>> matthias at opengis.ch
>>
>> [image: www]
>> opengis.ch
>>
>> [image: linkedin] <https://www.linkedin.com/company/opengisch/> [image:
>> mastodon] <https://fosstodon.org/@opengisch> [image: github]
>> <https://github.com/opengisch/>
>> _______________________________________________
>> QGIS-PSC mailing list
>> QGIS-PSC at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>
>
>
> --
>
> --
> Andreas Neumann
> QGIS.ORG board member (treasurer)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20251119/3766b452/attachment-0001.htm>

From andreas at qgis.org  Wed Nov 19 00:47:53 2025
From: andreas at qgis.org (Andreas Neumann)
Date: Wed, 19 Nov 2025 09:47:53 +0100
Subject: [Qgis-psc] QGIS macOS builds for 3.44
In-Reply-To: <CAC7zN97jGyn+amE0vRcE7-jrn=+-vrD9QxbnWCfPgpN0Rgf3aQ@mail.gmail.com>
References: <CAC7zN95dVvgKjbT82e0UT-_oRORnO3LEm5H0mgcYHCFBM1se2g@mail.gmail.com>
 <CAB2Z92Bo-aggA3fCsnqmpj4AFgSE8uxHS89Tou5kRQ9xnHjX0A@mail.gmail.com>
 <CAC7zN97jGyn+amE0vRcE7-jrn=+-vrD9QxbnWCfPgpN0Rgf3aQ@mail.gmail.com>
Message-ID: <CAB2Z92A5jO9rD+D6E8F-4ZonePQo48no2VKFWV-Pj92yfOv7BQ@mail.gmail.com>

Hi Matthias,

The Mac machine at Untangled was rented back when LutraConsulting was
active with Mac packaging - that was quite some years ago - so probably not
an arm machine. I think J?rgen would also have access to that server. So I
guess this server can be canceled.

If you have a good idea for a new provider for Mac servers / machines let
me know and we can rent one. Preferably a location in Europe / Germany.
Unfortunately, our main provider that we use in Germany (Hetzner) does not
offer Mac machines anymore.

For deploying the Mac download packages at qgis.org you can discuss it with
Lova / Tim / J?rgen. It would be great to make the notarized version
available "officially".

Thanks,
Andreas


On Wed, 19 Nov 2025 at 09:41, Matthias Kuhn <matthias at opengis.ch> wrote:

> Hi Andreas,
>
> - I do not use the macOS server (and I do not have access to it),
> everything is done on github hosted macOS runners so far. I would be
> interested in getting access to a macOS machine for a self-hosted runner
> (particularly because building qtwebengine might be too much for the github
> hosted ones). Is that server an arm based one?
> - We can host it at the QGIS website at any time, I'll need some
> instructions on how the interface to that server works. Who should this be
> discussed with?
>
> Best regards
> Matthias
>
> On Wed, Nov 19, 2025 at 9:36?AM Andreas Neumann <andreas at qgis.org> wrote:
>
>> Hi Matthias,
>>
>> This is great news. Thanks for your efforts!
>>
>> I have two questions:
>>
>> - we still have a MacOS server at Untangled. Are you actively using this
>> server or could we cancel/shutdown this server?
>> - once you consider the notarized Qt5 QGIS 3.44 stable - could we
>> officially host it at the QGIS website?
>>
>> Thank you very much,
>> Andreas
>>
>>
>> On Wed, 19 Nov 2025 at 07:56, Matthias Kuhn via QGIS-PSC <
>> qgis-psc at lists.osgeo.org> wrote:
>>
>>> Dear PSC,
>>>
>>> I have worked on macOS builds for QGIS 3.44.
>>>
>>> These builds include:
>>>
>>>  - Recent dependencies (see below)
>>>  - Native Intel and arm support (universal binaries)
>>>  - Packaged as a dmg installer
>>>  - Notarized with OSGeo certificates
>>>
>>> The source code had to be heavily patched with backports from code that
>>> was merged to master only after QGIS 3.44 had been branched.
>>> The build pipeline
>>> <https://github.com/m-kuhn/QGIS/tree/refs/heads/qt5-qgis-3-44> for QGIS
>>> 3.44 is therefore something I do not intend to merge into the release-3_44
>>> branch and therefore have it on my own fork and the build can be downloaded
>>> from there too:
>>>
>>> QGIS 3.44.4 download:
>>> https://github.com/m-kuhn/QGIS/releases/download/final-3_44_4/QGIS-final-3_44_4.dmg
>>> .
>>>
>>> Notarization is now done using an OSGeo certificate (big thanks to
>>> Michael Smith for the support).
>>>
>>> - The notarization for Qt6 nightly builds (and future QGIS 4 releases)
>>> is done in github actions in this repository
>>> https://github.com/qgis/qgis-notarize
>>> - The notarization for Qt5 based QGIS 3.44 releases is done in this
>>> repository https://github.com/m-kuhn/qgis-notarize
>>>
>>> There are still a few limitations which have come up in our internal
>>> testing, most notably UI translation isn't working yet.
>>> Furthermore, there has been a request to bundle more python for data
>>> science ().
>>> I am still working on addressing these shortcomings, I expect more
>>> requests to come up which I'll address as time permits.
>>>
>>> Since there are no officially maintained macOS releases available at the
>>> moment, I would like to publish these on the official QGIS download page.
>>> To publish the packages to the download page, I'd be happy to get some
>>> support (uploading to a server / changing download links). Who would be the
>>> right person to talk to?
>>>
>>> Thanks a lot for trusting me with this task.
>>>
>>> Kind regards
>>> Matthias
>>>
>>> Qt version
>>>
>>> 5.15.18
>>>
>>> Python version
>>>
>>> 3.12.11
>>>
>>> GDAL version
>>>
>>> 3.11.4 ? Eganville
>>>
>>> PROJ version
>>>
>>> 9.7.0
>>>
>>> EPSG Registry database version
>>>
>>> v12.022 (2025-08-30)
>>>
>>> GEOS version
>>>
>>> 3.14.1-CAPI-1.20.5
>>>
>>> SQLite version
>>>
>>> 3.50.4
>>>
>>> PDAL version
>>>
>>> 2.9.2
>>>
>>> PostgreSQL client version
>>>
>>> 16.9
>>>
>>> SpatiaLite version
>>>
>>> 5.1.0
>>>
>>> QWT version
>>>
>>> 6.2.1
>>>
>>> QScintilla2 version
>>>
>>> 2.13.4
>>>
>>> --
>>> [image: OG]
>>> <https://link.bulksignature.com/4054a10b-3c19-46a2-9e27-813335d7dbdc>
>>>
>>> *Matthias Kuhn*
>>> Mr. Noproblemo
>>>
>>> CTO | Co-Founder
>>> [image: email]
>>> matthias at opengis.ch
>>>
>>> [image: www]
>>> opengis.ch
>>>
>>> [image: linkedin] <https://www.linkedin.com/company/opengisch/> [image:
>>> mastodon] <https://fosstodon.org/@opengisch> [image: github]
>>> <https://github.com/opengisch/>
>>> _______________________________________________
>>> QGIS-PSC mailing list
>>> QGIS-PSC at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/qgis-psc
>>>
>>
>>
>> --
>>
>> --
>> Andreas Neumann
>> QGIS.ORG board member (treasurer)
>>
>

-- 

--
Andreas Neumann
QGIS.ORG board member (treasurer)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-psc/attachments/20251119/104070ab/attachment.htm>