Conda(Docker)/AppImage Failure

[sgrogan]

Hello all FreeCADers
I am having trouble getting FreeCAD to build Linux on Conda using @looooo's feed-stock https://github.com/looooo/freecad-feedstock

The failing part of the Azure pipeline is here: https://dev.azure.com/sppedflyer/feedst ... 30fe1eb4e7

The build seems to fail because of package conflicts. The Win and OSX builds succeed that use the same dependencies. Does anybody see what package may be the culprit? The log shows many conflicts, but I don't believe that all of a sudden everything conflicts with everything. I suspect some low level package has changed and it cascades, but I really have no clue.

Anyway we use this Conda build to distribute the .AppImage, so it will not be updated until this is solved.

[looo]

I am not sure which package introduced the troubles, but we have a problem with vtk which was not pinned for occt. I am working on this currently also to simplify the netgen recipe. The idea is to create a vtk-independend package and a separate package containing the vtk- dependend libraries.

Also anaconda is prepering for a new release currently which is an indicator for issues But we will also profit from this work (qt5.15)...

In the end it's about getting all conda packages updated. There is a lot of work waiting again (vtk9, hdf5, new calculux, netgen, smesh...) Keep thing as updated as possible was always the strategy which worked best.

[sgrogan]

In the end it's about getting all conda packages updated. There is a lot of work waiting again (vtk9, hdf5, new calculux, netgen, smesh...)

Maybe you could assign me a task, the easier the better given my (lack of) skill level.
As you mentioned in another thread decoupling vtk-occt seems a good idea.

[looo]

In the end it's about getting all conda packages updated. There is a lot of work waiting again (vtk9, hdf5, new calculux, netgen, smesh...)

Maybe you could assign me a task, the easier the better given my (lack of) skill level.
As you mentioned in another thread decoupling vtk-occt seems a good idea.

In the past, I always created a TODO list in the forum which helped to keep track of the open stuff.

I guess we should try this way:
- [x] calculix 2.17
- [x] occt + vtk8 (with correct pinning)
- [c] remove unpinned occt +vtk8
- [x] update occt to vtk9
- [ ] netgen 6.2.2007 (or newer)
- [ ] smesh
- [ ] fix the freecad linux build (if not fixed by the previous tasks)
- [ ] split occt (vtk, non-vtk)

@adam-urbanczyk already tries to compile occt with vtk9:
https://github.com/conda-forge/occt-feedstock/pull/46

(if anyone already did the job of updating packages to vtk9 feel free to give some hints)

@sgrogan: Maybe you can try to check which library is leading to the netgen6.2.2007 windows issue using the dependency checker. You can build it this way:

Code: Select all

git clone https://github.com/conda-forge/netgen-feedstock
cd netgen-feedstock
git remote add bot https://github.com/regro-cf-autotick-bot/netgen-feedstock
git fetch --all
git checkout 6.2.2007_h6b7482
conda debug . -m .ci_support\win_python3.8.____cpython.yaml

and use the printed commands to build it. Once done you should be able to use the dependency checker on the installed .pyd . The files are stored in the _h_env (host environment). You can deactivate the build-environment (which is activated on top of the host-environment) by "conda deactivate".

[looo]

The failing part of the Azure pipeline is here: https://dev.azure.com/sppedflyer/feedst ... 30fe1eb4e7

testing locally I don't see a dependency issue. So maybe this issue is already resolved.

[sgrogan]

testing locally I don't see a dependency issue. So maybe this issue is already resolved.

No joy. Same issue, the errors are slightly different. I think it's more of a Docker problem than a Conda problem. I'll keep digging. I'm still not sure I'm interpreting the log correctly. https://dev.azure.com/sppedflyer/feedst ... b4e7&l=898

@sgrogan: Maybe you can try to check which library is leading to the netgen6.2.2007 windows issue using the dependency checker. You can build it this way:

I created a netgentest env, activated it and ran your commands. I get 'No command "conda debug"'
Do I need to add some channel(s) or packages to this env?
I guess conda-build, but do I install this in the base env or the recently created netgentest?

[looo]

No joy. Same issue, the errors are slightly different. I think it's more of a Docker problem than a Conda problem. I'll keep digging. I'm still not sure I'm interpreting the log correctly. https://dev.azure.com/sppedflyer/feedst ... b4e7&l=898

The output doesn't help a lot. I normally tried to reproduce such issues locally and if reproducible try to remove deps from the requirements-list to see which package introduces the troubles.

Anyway, I think we should see the failing build as a good opportunity to update all packages. Maybe this will also create some awareness of this task.

I created a netgentest env, activated it and ran your commands. I get 'No command "conda debug"'
Do I need to add some channel(s) or packages to this env?
I guess conda-build, but do I install this in the base env or the recently created netgentest?

I have conda-build installed in the base environment. Running conda debug from this base-env should create all the necessary environments. So no need to create the environments manually.

edit: I uploaded a package (Revision: 22198). Still not having any issues with docker locally.

[sgrogan]

I have conda-build installed in the base environment. Running conda debug from this base-env should create all the necessary environments. So no need to create the environments manually.

Thanks. I get some progress but I need VS2017 and I only have VS2019 installed locally. I will try installing VS2017.

The output doesn't help a lot. I normally tried to reproduce such issues locally and if reproducible try to remove deps from the requirements-list to see which package introduces the troubles.

remove from meta.yaml? This problem is Linux specific.

[looo]

remove from meta.yaml? This problem is Linux specific.

yes removing the deps from the meta.yaml is what I did in the past to check which of the deps causes the dependencies-issues... I currently try to rebuild netgen via ci's. Also here I see some strange behavior: not the latest available version of occt is used. I saw such things in the past and worked around by manual pinning.

I get some progress but I need VS2017 and I only have VS2019 installed locally. I will try installing VS2017.

I have vs2017 still installed, so maybe it's easier if I do the testing. But I am not quite sure how to use the dependency-walker.

[sgrogan]

I have vs2017 still installed, so maybe it's easier if I do the testing. But I am not quite sure how to use the dependency-walker.

I should be able to install vs2017 on the weekend. I'd really like to learn how to do this.
Dependency-Walker seems to have died. They don't claim compatibility for Win10, although I haven't tried since I upgraded to Win 10 http://dependencywalker.com/
This may be an alternative https://github.com/lucasg/Dependencies