Closed beliaev-maksim closed 1 year ago
It sounds like a reason for reverting/refactoring https://github.com/canonical/data-platform-libs/pull/35 CC: @deusebio Try to bump ops lib to 2+, we have migrated from 1.5 to 2.2.0 without any issues.
yes, I confirm that if we bump our charm to ops>2 then it works
maybe at least clear error if ops is of unsupported version? since now it fails very cryptic
Uhm, we specified this using charmlibs dependency (see here). We point this out in the README as well, actually. It would actually be good if - when one does charmcraft pack
- the consistency of these libraries are checked and errors are thrown otherwise
I can see that this can happen all the times that we have dependencies to comply with in our charmlibs unfortunately
@deusebio I mentioned to Sergio. However, in meantime we can also offer something from the library end
using the new PYDEPS feature and having the libraries declare ops > 2 (for this case) would solve this issue.
recall that PYDEPS is currently on charmcraft edge only.
@sergiusens that answers, then this ops dependency just got lost when we packed
@deusebio then I assume no action on the lib side
:+1: Closing the issue then!
When try to import the library we get an exception:
one of the potential issues might be that our charm requires ops<2 which we set in reqs.txt for our charm. While this lib requires ops>2. Not sure how charmcraft is going to resolve it. but the issue might different, worth to investigate