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.

Sign up for GitHub

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

Jump to bottom

Install poetry-plugin-export, as it will not be installed by default in future poetry versions #825

Closed
almet opened this issue May 30, 2024 · 1 comment · Fixed by #1043
Closed

Install poetry-plugin-export, as it will not be installed by default in future poetry versions #825

almet opened this issue May 30, 2024 · 1 comment · Fixed by #1043
Labels
development Development-focused changes tidying ✨

Comments

@almet
Copy link
Contributor

almet commented May 30, 2024

When generating the image with install/common/build-image.py, a warning is currently generated, telling us that the tool we currently use will not be included in future versions of poetry-export.

Warning: poetry-plugin-export will not be installed by default in a future version of Poetry.
In order to avoid a breaking change and make your automation forward-compatible, please install poetry-plugin-export explicitly. See > https://python-poetry.org/docs/plugins/#using-plugins for details on how to install a plugin.
To disable this warning run 'poetry config warnings.export false'

We want to make sure it's installed, (or to use a different mechanism if it makes more sense)
@almet almet added the development Development-focused changes label May 30, 2024
@almet almet changed the title poetry-plugin-export will not be installed by default in future versions of poetry Install poetry-plugin-export, as it will not be installed by default in future poetry versions May 30, 2024
@almet
Copy link
Contributor Author

almet commented Jan 6, 2025 •
edited
Loading

This has been now removed from poetry 2.0 and it's the reason why our build-deb and security scan targets are currently failing with The command "export" does not exist.

This was referenced Jan 6, 2025
Closed
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
development Development-focused changes tidying ✨
Projects
None yet
Milestone
No milestone
1 participant
@almet