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

Wrong yosys package is used #79

Closed
acomodi opened this issue Mar 6, 2020 · 1 comment · Fixed by #80
Closed

Wrong yosys package is used #79

acomodi opened this issue Mar 6, 2020 · 1 comment · Fixed by #80

Comments

@acomodi
Copy link

acomodi commented Mar 6, 2020

With the recent rework of conda build in #74, some packages cannot be found at install time (for symbiflow-arch-defs this happens during make all_conda).

In particular, the new yosys builds cannot be used within https://github.com/SymbiFlow/symbiflow-arch-defs as they cannot be fetched.

I suppose the issue lies in the new tagging mechanism, for which, if a tag is not compliant with a specific pattern, it gets set to v0.0.

The problem is that now, in conda channels there is a mix of two ways of tagging, probably causing the above mentioned errors: https://conda.anaconda.org/SymbiFlow/linux-64.
This happens for instance with Yosys, that, from a certain date, started to have a different tag convention.

There should be some more information in the README to understand how to correctly tag branches, so that there would be consistency across all packages (at least those under SymbiFlow control).

@acomodi
Copy link
Author

acomodi commented Mar 6, 2020

@mithro FYI

@acomodi acomodi changed the title Yosys package cannot be found Wrong yosys package is used Mar 6, 2020
@mithro mithro closed this as completed in #80 Mar 6, 2020
mithro added a commit that referenced this issue Mar 6, 2020
Fixes #79

Signed-off-by: Tim 'mithro' Ansell <me@mith.ro>
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.

1 participant