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

Packaging fails with "Large file option has not been set" #1034

Closed
najose opened this issue Aug 30, 2024 · 5 comments · Fixed by conda/rattler#838
Closed

Packaging fails with "Large file option has not been set" #1034

najose opened this issue Aug 30, 2024 · 5 comments · Fixed by conda/rattler#838

Comments

@najose
Copy link

najose commented Aug 30, 2024

rattler-build fails to package certain recipes if the package size is large.

When running rattler-build on such large packages we run into:

 ╰─────────────────── (took 2 minutes)
 × error Error building package: Could not open or create, or write to file
Error:   × Could not open or create, or write to file
  ╰─▶ Large file option has not been set

Did some initial investigation into this:

@najose
Copy link
Author

najose commented Aug 30, 2024

Thinking about this again, this might not be the right repo for this issue, since this is handled by rattler-package-streaming in conda/rattler repo, but I just filed it here as it affects rattler-build.

@wolfv
Copy link
Member

wolfv commented Aug 30, 2024

Thanks for filing this issue! Do you have a notion of "how large"? We should definitely fix this asap.

@wolfv
Copy link
Member

wolfv commented Aug 30, 2024

OK, it's 4 GB apparently. I'll have a look if we should set this always, or if we should try to figure out the file size beforehand.

@najose
Copy link
Author

najose commented Aug 30, 2024

Thanks for the quick fix!

@najose
Copy link
Author

najose commented Oct 30, 2024

@wolfv, I wonder if #1147 is somehow related to this bug too.

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 a pull request may close this issue.

2 participants