Alex Kavanagh

Hi there; yeah, we have quite a lot of legacy pinning to get around issues we had with pip when they were transitioning their resolver during the pip 21+ days....

> (If 3.11 is untested on your end, it might be good to enforce that with a `python_requires` cap in your `setup.py` slightly_smiling_face -- that would have caused Homebrew's package...

Hi, which version of juju are you using? The latest version deploys charms from the charmhub instead of the charmstore, and there is IIRC, a bug in juju that always...

I think #639 has solved this issue; please could you check again, and note here if it doesn't seem to be working? Thanks!

@mthaddon can you post a link to the problem charm (layer) - it would be good to see where the issue is. Thanks.

@mthaddon okay, so I got it to build by doing the following: 1. I changed the charmcraft.yaml to: ```yaml type: "charm" bases: - build-on: - name: "ubuntu" channel: "20.04" run-on:...

> wave It looks like there are release notes since 3.0.5, not sure if that is intentional, thanks!! :face_exhaling: it was an oversight, sorry. Is this breaking homebrew? In my...

I've done releases for 3.0.5, 3.0.6, 2.8.5 and 2.8.6 now; sorry I created some confusion. Hopefully, this will sort it out. Thanks for pointing it out! If this resolves the...

I'm curious, but what happens if you just `curl https://juju.github.io/layer-index/` on the same box? charm build uses `requests` which just uses the underlying python libs (urlib3, etc) to fetch the...

Oh, I feared as much; doing a quick web search yields things like: https://discuss.dizzycoding.com/force-requests-to-use-ipv4-ipv6/ i.e. it's a problem. Possible solutions are a `-4` flag to force ipv4 or reducing the...