Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manual harfbuzz 10 migration #74

Merged
merged 14 commits into from
Jan 17, 2025
Merged

Conversation

Tobias-Fischer
Copy link
Contributor

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@Tobias-Fischer
Copy link
Contributor Author

@conda-forge-admin, please rerender

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Jan 7, 2025

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12649661804. Examine the logs at this URL for more detail.

@Tobias-Fischer
Copy link
Contributor Author

@traversaro - we need this for the ros-noetic rebuild. Do you have any idea about the Windows failure?

(%BUILD_PREFIX%) %SRC_DIR%>ninja -v -C builddir -j 2 
ninja: fatal: ReadFile: The handle is invalid.
ninja: Entering directory `builddir'

[1/1204] "D:\bld\glib-split_1729191053212\_build_env\python.exe" "D:/bld/gtk3-split_1736233127491/_h_env/Library/bin/glib-genmarshal" "--quiet" "--prefix" "_gdk_marshal" "--valist-marshallers" "--output" "gdk/gdkmarshalers.h" "--header" "../gdk/gdkmarshalers.list" "--pragma-once"

FAILED: gdk/gdkmarshalers.h 
"D:\bld\glib-split_1729191053212\_build_env\python.exe" "D:/bld/gtk3-split_1736233127491/_h_env/Library/bin/glib-genmarshal" "--quiet" "--prefix" "_gdk_marshal" "--valist-marshallers" "--output" "gdk/gdkmarshalers.h" "--header" "../gdk/gdkmarshalers.list" "--pragma-once"
CreateProcess failed: The system cannot find the file specified.

@traversaro
Copy link

My guess is that it may be related to:

2025-01-07T07:04:29.7261295Z Program D:/bld/gtk3-split_1736233127491/_h_env/Library/bin/glib-compile-schemas found: YES (D:/bld/gtk3-split_1736233127491/_h_env/Library/bin\glib-compile-schemas.EXE)
2025-01-07T07:04:29.7264583Z WARNING: Target "gsettings-compile-demos\gtk-demo" has a path separator in its name.
2025-01-07T07:04:29.7265825Z This is not supported, it can cause unexpected failures and will become
2025-01-07T07:04:29.7267138Z a hard error in the future.
2025-01-07T07:04:30.8227002Z C++ compiler for the host machine: cl.exe (msvc 19.29.30157 "Microsoft (R) C/C++ Optimizing Compiler Version 19.29.30157 for x64")
2025-01-07T07:04:30.8229441Z C++ linker for the host machine: link link 14.29.30157.0

However, I will try to build this locally to understand more (not before CET evening of the 7th, as I am going through some backlog).

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12649693750. Examine the logs at this URL for more detail.

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Jan 7, 2025

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12818349886. Examine the logs at this URL for more detail.

@ryanvolz
Copy link
Contributor

ryanvolz commented Jan 7, 2025

I think glib is a good lead. This is the error in the latest build:

2025-01-07T11:22:16.1497278Z (%BUILD_PREFIX%) %SRC_DIR%>ninja -v -C builddir -j 2 
2025-01-07T11:22:16.2089832Z ninja: fatal: ReadFile: The handle is invalid.
2025-01-07T11:22:16.2090431Z ninja: Entering directory `builddir'
2025-01-07T11:22:16.2105592Z 
2025-01-07T11:22:16.2106671Z [1/1204] "D:\bld\glib-split_1729191053212\_build_env\python.exe" "D:/bld/gtk3-split_1736248580980/_h_env/Library/bin/glib-genmarshal" "--quiet" "--prefix" "_gdk_marshal" "--valist-marshallers" "--output" "gdk/gdkmarshalers.h" "--header" "../gdk/gdkmarshalers.list" "--pragma-once"
2025-01-07T11:22:16.2120454Z 
2025-01-07T11:22:16.2121086Z FAILED: gdk/gdkmarshalers.h 
2025-01-07T11:22:16.2130546Z "D:\bld\glib-split_1729191053212\_build_env\python.exe" "D:/bld/gtk3-split_1736248580980/_h_env/Library/bin/glib-genmarshal" "--quiet" "--prefix" "_gdk_marshal" "--valist-marshallers" "--output" "gdk/gdkmarshalers.h" "--header" "../gdk/gdkmarshalers.list" "--pragma-once"
2025-01-07T11:22:16.2137280Z CreateProcess failed: The system cannot find the file specified.

where the file that it cannot find is D:\bld\glib-split_1729191053212\_build_env\python.exe, which doesn't exist because it's looking for a path from the glib build! I haven't looked at what has changed about the glib build yet but figured this was a helpful observation to put out there.

@ryanvolz
Copy link
Contributor

ryanvolz commented Jan 7, 2025

I think glib is a good lead. This is the error in the latest build:

2025-01-07T11:22:16.1497278Z (%BUILD_PREFIX%) %SRC_DIR%>ninja -v -C builddir -j 2 
2025-01-07T11:22:16.2089832Z ninja: fatal: ReadFile: The handle is invalid.
2025-01-07T11:22:16.2090431Z ninja: Entering directory `builddir'
2025-01-07T11:22:16.2105592Z 
2025-01-07T11:22:16.2106671Z [1/1204] "D:\bld\glib-split_1729191053212\_build_env\python.exe" "D:/bld/gtk3-split_1736248580980/_h_env/Library/bin/glib-genmarshal" "--quiet" "--prefix" "_gdk_marshal" "--valist-marshallers" "--output" "gdk/gdkmarshalers.h" "--header" "../gdk/gdkmarshalers.list" "--pragma-once"
2025-01-07T11:22:16.2120454Z 
2025-01-07T11:22:16.2121086Z FAILED: gdk/gdkmarshalers.h 
2025-01-07T11:22:16.2130546Z "D:\bld\glib-split_1729191053212\_build_env\python.exe" "D:/bld/gtk3-split_1736248580980/_h_env/Library/bin/glib-genmarshal" "--quiet" "--prefix" "_gdk_marshal" "--valist-marshallers" "--output" "gdk/gdkmarshalers.h" "--header" "../gdk/gdkmarshalers.list" "--pragma-once"
2025-01-07T11:22:16.2137280Z CreateProcess failed: The system cannot find the file specified.

where the file that it cannot find is D:\bld\glib-split_1729191053212\_build_env\python.exe, which doesn't exist because it's looking for a path from the glib build! I haven't looked at what has changed about the glib build yet but figured this was a helpful observation to put out there.

This has been observed and fixed a little while ago but for Unix builds: conda-forge/glib-feedstock#192. I created an issue at glib saying that this is still a problem on Windows.

@traversaro
Copy link

Fix attempted in conda-forge/glib-feedstock#199.

@hmaarrfk
Copy link
Contributor

@conda-forge-admin please rerender

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Jan 16, 2025

Nice. Fix windows and Linux osx breaks

@hmaarrfk
Copy link
Contributor

I think we hit: conda/conda-build#5594

@conda-forge-admin please rerender

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12816093156. Examine the logs at this URL for more detail.

@hmaarrfk
Copy link
Contributor

@conda-forge-admin please rerender

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12817940916. Examine the logs at this URL for more detail.

@Tobias-Fischer
Copy link
Contributor Author

Looks like this is good to go? Thanks @hmaarrfk @traversaro @ryanvolz!

@hmaarrfk
Copy link
Contributor

Yeah. I guess I forced a fix so merge away?

@Tobias-Fischer
Copy link
Contributor Author

Yes I think it's fine @hmaarrfk as it will disappear with the next rerender which will happen for the next PR anyhow (and by then hopefully the problem will have disappeared)

@hmaarrfk
Copy link
Contributor

Well it is in the hands of the maintainers now

@ryanvolz ryanvolz merged commit 6f42bd8 into conda-forge:main Jan 17, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants