-
Notifications
You must be signed in to change notification settings - Fork 169
Description
Checklist
- I added a descriptive title
- I searched open reports and couldn't find a duplicate
What happened?
After #991 was merged, @moorepants began building our Windows installers from the development version of constructor. The first builds worked and we confirmed that the permissions issue was fixed. This first release was built with the development version just after #991 was merged:
https://gitlab.ewi.tudelft.nl/bhmgerritsen/anaconda-dee-config/-/releases/v2025.02 (exe download)
We have successfully installed this version on Windows many times. I recently started testing new installers we are building and reported that the Windows installer no longer works, showing this:
I get an error "Failed to extract packages", during installation (after uninstall TU Delft conda, restart, reinstall):
@moorepants has made some changes to the installer build, namely removing the pytorch channel in the construct.yaml file and some minor version bumps. You can see the changes here:
@moorepants then wondered if the commits to constructor since #991 may have caused the installation failure, so he built an installer using constructor @ db1ea11 (#991) and get this result:
https://github.com/moorepants/anaconda-dee-config/actions/runs/16362487740 (download the exe installer artifact)
and that installed successfully on Windows on his machine. However, it didn't work for me, leading to the same issue
To summarize, it seems like commits post #991 may be causing this failure to extract packages error on some machines. An example exe that should demonstrate this failure is:
https://github.com/moorepants/anaconda-dee-config/actions/runs/16340399472
Additional Context
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status