Comment:
I am not sure if I am in the right place here. If not, feel free to close this issue.
I recently added my package remage to the ARM64 migrator in #8159. The bot picked that change up, which is reflected on the status dashboard.
Somehow the package is marked as a child of winpty/pywinpty. However, I do not understand that. I cannot observe this package being installed in the build or host dependencies of the remage package, neither on linux-x64 nor on osx-x64. I do also not understand how my package (skipped build on windows) can depend upon a package that is only built for windows... This apparently also happens with a lot of other packages?
Is the bots dependency tracking logic fine, or is there anything I can do to speed up getting the migration done? Thanks!
Comment:
I am not sure if I am in the right place here. If not, feel free to close this issue.
I recently added my package
remageto the ARM64 migrator in #8159. The bot picked that change up, which is reflected on the status dashboard.Somehow the package is marked as a child of
winpty/pywinpty. However, I do not understand that. I cannot observe this package being installed in the build or host dependencies of the remage package, neither on linux-x64 nor on osx-x64. I do also not understand how my package (skipped build on windows) can depend upon a package that is only built for windows... This apparently also happens with a lot of other packages?Is the bots dependency tracking logic fine, or is there anything I can do to speed up getting the migration done? Thanks!