Sorry, I would like to clarify by "issue" I mean it not being updated, issues should be submitted on the arch issue tracker. -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev

Sorry, My communication skills suck, the point I was TRYING to make was that not many of us are capable of helping with this issue, and to email the maintainer directly to get their attention (works a lot better than hoping they come across the email in the mailing list). Found it to work quite well, some people use "list" emails so that their main email doesn't get filled up (probably by one username, "Polarian"). -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev

Hi again, (cc'ing also Mathieu in case he has input) I've managed to compile and install vtk 9.2.5 and Paraview 5.11 with the attached PKGBUILDs. In my testing so far today it looks to work fine, and is a whole lot faster than Paraview 5.10 on my OpenFOAM cases :) As you can see from PKGBUILDs, this is without any of the previously used patches since all the necessary changes look to be upstreamed. When compiling vtk I did have an issue with qmlplugindump failing. I gather from the various bug reports around that topic that I'm missing some Qt build dependency (which is not listed in makedepends), but I was not able to figure out which one, the error message does not specify it. So the attached "dontrun-qmlplugindump.patch" modifies one of the CMakeLists.txt files to skip running qmlplugindump and just use a static copy of the qml plugins list that is provided with vtk. The line to run this patch is included in the vtk PKGBUILD but commented out. It is not necessary if you have the correct Qt modules installed, I assume. Regarding the "verdict" package that is only available from AUR, is it preferrable to include that package in "Community", or to avoid compiling in the "verdict" support similar to how exprtk and ioss are omitted? Regards, Åsmund On Wed, Feb 22, 2023 at 11:50 AM Åsmund Ervik wrote:

Hi,

Thanks for the update Bruno. Sorry to hear about the difficult situation, you have my best wishes that it improves quickly!

I'm having a go at updating the VTK and Paraview packages myself. So far it seems many of the existing Arch-specific patches have been upstreamed, which is nice.

It also seems that VTK now requires the "verdict" package, which is only in AUR, so this is a complication. I assume "verdict" will have to be included into "Community" - fortunately it's an extremely simple PKGBUILD.

If I am able to to make VTK 9.2.6. and Paraview 5.11.0 compile from updated PKGBUILDs on my machine, I will get back to you.

Regards, Åsmund

On Mon, Feb 20, 2023 at 4:35 PM Archange wrote:

...

Hi,

Le 20 février 2023 18:35:45 GMT+04:00, "Åsmund Ervik" a écrit :

...

Hi,

The paraview package is at version 5.10 and has been flagged as out-of-date since October.

Are there any blockers for updating the package to 5.11?

Yes, me (this package is not trivial to upgrade, it requires some knowledge of what things to check upstream when there is a major upgrade). Plus some administrative issues regarding my internet connection (or lack of).

Basically I’ve been underwater with work for months, it started to get better but… I’ve been moving last month and my new home apparently does not exist (depends on which service you ask, but when it comes to network operators that’s basically it — I’ve been spending 1h per day by phone or in person every day of the past four weeks to try to get this solved). So I’m limited to my cellphone connection and huge packages like Paraview and VTK aren’t going to be a possibility/priority.

I don’t see any positive exit from this situation within the next three months, so the current ETA for me to return to active packaging is June (because I’m moving temporarily somewhere that does have internet).

Regards, Bruno/Archange