-
Notifications
You must be signed in to change notification settings - Fork 343
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
Unable to install avocado-framework-plugin-varianter-yaml-to-mux:102 cleanly #5713
Comments
https://pypi.org/project/avocado-framework-plugin-varianter-yaml-to-mux/#history |
Hi @AYUSHJAIN951 , I can confirm the issue you are reporting is valid. The cause of the problem is that we moved the documentation to the plugin (in hope of giving them a better description). But in the specific case of the yaml-to-mux plugin, there's directives that are Sphinx-only, and not pure ResTructuredText (rst). We'll add checks so that it doesn't happen anymore, probably something like:
I'll check if there's anything we can do to mitigate this to version 102.0 without requiring a new release. |
Hi @AYUSHJAIN951 , I published a version of the plugins for 102.0 with just the long description modified. You can find it here. The installation should now proceed as expected. I won't close this issue for now, because like I said before, we have to make sure this doesn't happen again. Thanks! |
Thanks @clebergnu for the quick fix.
Sure let's keep the issue open for now until its having a proper fix.
Thanks!! |
With this small change, all the special tags will be removed from yaml_to_mux varianter README file which is used for long description of plugin. We have to do this because systems like pypi doesn't support sphinx only basic ResTructuredText. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
This commit adds twine check for each package, before publishing it. With this change, we will avoid problems with publishing the packages in the future. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
This commit adds twine check for each package, before publishing it. With this change, we will avoid problems with publishing the packages in the future. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
It copies short description to the long description of ansible plugin, because we don't have detailed description, but it is enforced by twine check. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
With this small change, all the special tags will be removed from yaml_to_mux and pict varianters README files which is used for long description of plugins. We have to do this because systems like pypi doesn't support sphinx, only basic ResTructuredText. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
This commit adds twine check for each package, before publishing it. With this change, we will avoid problems with publishing the packages in the future. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
This commit adds twine check for each package, before publishing it. With this change, we will avoid problems with publishing the packages in the future. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
This commit adds twine check for each package, before publishing it. With this change, we will avoid problems with publishing the packages in the future. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
This commit adds twine check for each package, before publishing it. With this change, we will avoid problems with publishing the packages in the future. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
This commit adds twine check for each package, before publishing it. With this change, we will avoid problems with publishing the packages in the future. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
This commit adds twine check for each package, before publishing it. With this change, we will avoid problems with publishing the packages in the future. Reference: avocado-framework#5713 Signed-off-by: Jan Richter <[email protected]>
While upgrading 101.0 ->102.0, avocado-framework-plugin-varianter-yaml-to-mux seems to be having version issues
Ideally it should be installing avocado and avocado-framework-plugin-varianter-yaml-to-mux with 102.0 release
But currently it seems pip is not able to fetch and install avocado-framework-plugin-varianter-yaml-to-mux:102.0 and instead installing 101.0 .
The text was updated successfully, but these errors were encountered: