Johan Euphrosine
Johan Euphrosine
The culprid seems to be https://github.com/docker/docker/commit/6a1ff022b0744213ed588d9c16dbb13ce055eda6 But I couldn't find the corresponding PR or issues where that change was discussed. @tiborvass any ideas?
@ewindisch on the other hand there is a lot of docker daemon already running, with registry container running on `localhost`. If literally all those users will need to pass `--insecure-registry...
@thocking: le assuming localhost is secure: please see https://github.com/docker/docker/issues/8898
looking at the log of the jobs there seems to be some authorization error: ``` Warning: It looks like you are trying to use an API token to authenticate in...
Not this could also be due to test pypi preventing a release for a given version to be overwritten. According to https://stackoverflow.com/a/63944201 it should be possible to workaround this by...
Apparently there is a `--build-number` option you can pass to `bdist_wheel` to override the build tag part of the wheel naming scheme and rev a pypi upload. I wonder if...
I think that would be fine for test pypi as long as you keep the production pypi for regular release.
Maybe @di could comment if it's fine to "spam" Test PyPI with continuous integration wheels.
@flaport fyi, we do have a klayout package in conda-eda now https://anaconda.org/LiteX-Hub/klayout/files (that does include the GUI).
> the conda build of klayout+GUI does not work on MacOs yet, @thomasdorch did the windows one and Floris made the linux one @xobs recently did some work around this...