You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "DataStrategistTeam (via GitHub)" <gi...@apache.org> on 2025/10/11 06:51:00 UTC

[I] docker compose up --build fails on 5.0.0 with No matching distribution found for uv [superset]

DataStrategistTeam opened a new issue, #35607:
URL: https://github.com/apache/superset/issues/35607

   ### Bug description
   
   
   **Description:**
   When trying to build Superset from the 5.0.0 tag using Docker Compose, the build fails due to a missing dependency `uv`.
   
   **Steps to Reproduce:**
   1. Clone the repo and checkout the 5.0.0 tag:
      ```bash
      git clone https://github.com/apache/superset.git
      cd superset/
      git fetch origin --tags
      git checkout -b dev 5.0.0
      ```
   2. Run:
      ```bash
      docker compose up --build
      ```
   
   **Observed Behavior:**
   The build fails with the following error:
   ```
   ERROR: Could not find a version that satisfies the requirement uv (from versions: none)
   ERROR: No matching distribution found for uv
   ```
   
   **Expected Behavior:**
   The Docker image should build successfully without dependency resolution errors.
   
   **Environment:**
   - Superset version: 5.0.0 (tag)
   - Docker version 28.3.2, build 578ccf6
   - OS: Ubuntu 24.04
   
   **Additional Context:**
   It seems the `uv` package is not available on PyPI, which causes the build to fail. Possibly a missing or misconfigured dependency in `requirements` or `constraints`.
   
   
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   5.0.0
   
   ### Python version
   
   3.11
   
   ### Node version
   
   18 or greater
   
   ### Browser
   
   Not applicable
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
   - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
   - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] docker compose up --build fails on 5.0.0 with No matching distribution found for uv [superset]

Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #35607:
URL: https://github.com/apache/superset/issues/35607#issuecomment-3392996491

   <!-- Greeting -->
   Hi @DataStrategistTeam! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
   
   <!-- Answer -->
   The error happens because Superset's Docker build scripts for 5.0.0 expect the `uv` CLI tool to be available, but it's not a Python package on PyPI—it's installed via a shell script from [astral.sh](https://astral.sh/uv/install.sh) and not included in the 5.0.0 Docker setup by default. When the build tries to run `uv pip install ...`, it fails if `uv` isn't present, leading to the "No matching distribution found for uv" error [example](https://github.com/apache/superset/issues/31510).
   
   To work around this for 5.0.0, you can either:
   
   1. **Edit the Docker scripts** (`docker/docker-bootstrap.sh` and `docker/pip-install.sh`) and replace all instances of `uv pip` with just `pip` [details](https://github.com/apache/superset/issues/31510).
   2. **Manually install `uv`** in your Docker build environment before those commands run, by adding:
      ```bash
      curl -LsSf https://astral.sh/uv/install.sh | sh
      export PATH="$HOME/.cargo/bin:$PATH"
      ```
      to the relevant Dockerfile or script [reference](https://github.com/apache/superset/pull/34376).
   3. **Use a stable older version** like 4.1.1 if you don't need features from 5.0.0 [reference](https://github.com/apache/superset/issues/31600).
   
   Permanent fixes and fallbacks to `pip` have been merged after 5.0.0, but aren't present in that tag [reference](https://github.com/apache/superset/blob/master/CHANGELOG/5.0.0.md). If you want to stay on 5.0.0, the script edit is usually the quickest solution.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/c6455ee3-ab6c-453d-9b49-7089dc246547?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c6455ee3-ab6c-453d-9b49-7089dc246547?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c6455ee3-ab6c-453d-9b49-7089dc246547?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c6455ee3-ab6c-453d-9b49-7089dc246547?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c6455ee3-ab6c-453d-9b49-7089dc246547?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c6455ee3-ab6c-453d-9b49-7089dc246547?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c6455ee3-ab6c-453d-9b49-7089dc246547?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
 b)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/35607)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] docker compose up --build fails on 5.0.0 with No matching distribution found for uv [superset]

Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
dosubot[bot] commented on issue #35607:
URL: https://github.com/apache/superset/issues/35607#issuecomment-3393068000

   <!-- Answer -->
   Your build is failing because the superset-websocket Dockerfile uses Node.js 16, but many frontend dependencies now require Node.js 20 or higher. The npm WARN EBADENGINE messages confirm this mismatch, and it's a known blocker for Superset builds since 5.0.0. To fix this, update your Dockerfile to use a Node.js 20 base image (for example, change `FROM node:16-alpine` to `FROM node:20-alpine` or `node:20-bookworm-slim`) [reference](https://github.com/apache/superset/pull/29988).
   
   The npm ERR! FETCH_ERROR is likely a network issue. If you still see network timeouts after updating Node, try configuring npm to use a reliable registry mirror with:
   ```bash
   npm config set registry http://mirrors.ustc.edu.cn/
   ```
   [reference](https://github.com/apache/superset/issues/31714)
   
   Once you update the Node.js version and check your network, the build should proceed past the npm ci and npm run build steps. Let me know if you hit any other errors!
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/ddaead99-5b01-46ae-94d4-df68e8c13dc2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ddaead99-5b01-46ae-94d4-df68e8c13dc2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ddaead99-5b01-46ae-94d4-df68e8c13dc2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ddaead99-5b01-46ae-94d4-df68e8c13dc2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ddaead99-5b01-46ae-94d4-df68e8c13dc2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ddaead99-5b01-46ae-94d4-df68e8c13dc2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ddaead99-5b01-46ae-94d4-df68e8c13dc2?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
 b)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/35607)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] docker compose up --build fails on 5.0.0 with No matching distribution found for uv [superset]

Posted by "DataStrategistTeam (via GitHub)" <gi...@apache.org>.
DataStrategistTeam commented on issue #35607:
URL: https://github.com/apache/superset/issues/35607#issuecomment-3393066833

    
   
   After swapping out  
   
   ```dockerfile
   RUN pip install --no-cache-dir --upgrade uv
   ```  
   
   for  
   
   ```dockerfile
   RUN apt-get update && apt-get install -y --no-install-recommends \
       curl ca-certificates \
    && rm -rf /var/lib/apt/lists/*
   ```  
   
   the build process halted at:  
   
    
   
   ```
    => [superset-websocket build 1/4] FROM docker.io/library/node:16-alpine                                                                                           0.0s
    => CACHED [superset-worker superset-node-ci 2/8] COPY docker/ /app/docker/                                                                                        0.0s
    => CANCELED [superset-init superset-node-ci 3/8] RUN /app/docker/apt-install.sh build-essential python3 zstd                                                    556.9s
    => CACHED [superset-websocket build 2/4] WORKDIR /home/superset-websocket                                                                                         0.0s
    => CACHED [superset-websocket build 3/4] COPY . ./                                                                                                                0.0s
    => ERROR [superset-websocket build 4/4] RUN npm ci &&   npm run build                                                                                           556.4s
    => CACHED [superset-worker python-base 2/6] RUN mkdir -p /app/superset_home                                                                                       0.0s
    => CACHED [superset-worker python-base 3/6] RUN useradd --user-group -d /app/superset_home -m --no-log-init --shell /bin/bash superset     && chmod -R 1777 /app  0.0s
    => CACHED [superset python-base 4/6] COPY --chmod=755 docker/*.sh /app/docker/                                                                                    0.0s
    => CANCELED [superset-init python-base 5/6] RUN apt-get update && apt-get install -y --no-install-recommends       curl ca-certificates     && rm -rf /var/lib  556.6s
   ------
    > [superset-websocket build 4/4] RUN npm ci &&   npm run build:
   0.672 npm WARN EBADENGINE Unsupported engine {
   0.673 npm WARN EBADENGINE   package: '@eslint/config-array@0.19.1',
   0.673 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.673 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.673 npm WARN EBADENGINE }
   0.673 npm WARN EBADENGINE Unsupported engine {
   0.673 npm WARN EBADENGINE   package: '@eslint/core@0.9.1',
   0.673 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.673 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.673 npm WARN EBADENGINE }
   0.674 npm WARN EBADENGINE Unsupported engine {
   0.674 npm WARN EBADENGINE   package: '@eslint/eslintrc@3.2.0',
   0.674 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.674 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.674 npm WARN EBADENGINE }
   0.674 npm WARN EBADENGINE Unsupported engine {
   0.674 npm WARN EBADENGINE   package: 'globals@14.0.0',
   0.674 npm WARN EBADENGINE   required: { node: '>=18' },
   0.674 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.674 npm WARN EBADENGINE }
   0.674 npm WARN EBADENGINE Unsupported engine {
   0.674 npm WARN EBADENGINE   package: '@eslint/js@9.17.0',
   0.674 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.674 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.674 npm WARN EBADENGINE }
   0.674 npm WARN EBADENGINE Unsupported engine {
   0.674 npm WARN EBADENGINE   package: '@eslint/object-schema@2.1.5',
   0.674 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.674 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.674 npm WARN EBADENGINE }
   0.675 npm WARN EBADENGINE Unsupported engine {
   0.675 npm WARN EBADENGINE   package: '@eslint/plugin-kit@0.2.4',
   0.675 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.675 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.675 npm WARN EBADENGINE }
   0.675 npm WARN EBADENGINE Unsupported engine {
   0.675 npm WARN EBADENGINE   package: '@humanfs/core@0.19.1',
   0.675 npm WARN EBADENGINE   required: { node: '>=18.18.0' },
   0.675 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.675 npm WARN EBADENGINE }
   0.675 npm WARN EBADENGINE Unsupported engine {
   0.675 npm WARN EBADENGINE   package: '@humanfs/node@0.16.6',
   0.675 npm WARN EBADENGINE   required: { node: '>=18.18.0' },
   0.675 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.675 npm WARN EBADENGINE }
   0.675 npm WARN EBADENGINE Unsupported engine {
   0.675 npm WARN EBADENGINE   package: '@humanwhocodes/retry@0.3.1',
   0.675 npm WARN EBADENGINE   required: { node: '>=18.18' },
   0.675 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.675 npm WARN EBADENGINE }
   0.676 npm WARN EBADENGINE Unsupported engine {
   0.676 npm WARN EBADENGINE   package: '@humanwhocodes/retry@0.4.1',
   0.676 npm WARN EBADENGINE   required: { node: '>=18.18' },
   0.676 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.676 npm WARN EBADENGINE }
   0.676 npm WARN EBADENGINE Unsupported engine {
   0.676 npm WARN EBADENGINE   package: '@typescript-eslint/eslint-plugin@8.19.0',
   0.676 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.676 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.676 npm WARN EBADENGINE }
   0.676 npm WARN EBADENGINE Unsupported engine {
   0.676 npm WARN EBADENGINE   package: '@typescript-eslint/parser@8.19.0',
   0.676 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.676 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.676 npm WARN EBADENGINE }
   0.676 npm WARN EBADENGINE Unsupported engine {
   0.676 npm WARN EBADENGINE   package: '@typescript-eslint/scope-manager@8.19.0',
   0.676 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.677 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.677 npm WARN EBADENGINE }
   0.677 npm WARN EBADENGINE Unsupported engine {
   0.677 npm WARN EBADENGINE   package: '@typescript-eslint/type-utils@8.19.0',
   0.677 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.677 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.677 npm WARN EBADENGINE }
   0.677 npm WARN EBADENGINE Unsupported engine {
   0.677 npm WARN EBADENGINE   package: '@typescript-eslint/types@8.19.0',
   0.677 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.677 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.677 npm WARN EBADENGINE }
   0.677 npm WARN EBADENGINE Unsupported engine {
   0.677 npm WARN EBADENGINE   package: '@typescript-eslint/typescript-estree@8.19.0',
   0.677 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.677 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.677 npm WARN EBADENGINE }
   0.677 npm WARN EBADENGINE Unsupported engine {
   0.677 npm WARN EBADENGINE   package: '@typescript-eslint/utils@8.19.0',
   0.677 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.677 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.677 npm WARN EBADENGINE }
   0.677 npm WARN EBADENGINE Unsupported engine {
   0.677 npm WARN EBADENGINE   package: '@typescript-eslint/visitor-keys@8.19.0',
   0.677 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.677 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.677 npm WARN EBADENGINE }
   0.678 npm WARN EBADENGINE Unsupported engine {
   0.678 npm WARN EBADENGINE   package: 'eslint-visitor-keys@4.2.0',
   0.678 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.678 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.678 npm WARN EBADENGINE }
   0.678 npm WARN EBADENGINE Unsupported engine {
   0.678 npm WARN EBADENGINE   package: 'eslint@9.17.0',
   0.678 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.678 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.678 npm WARN EBADENGINE }
   0.678 npm WARN EBADENGINE Unsupported engine {
   0.678 npm WARN EBADENGINE   package: 'eslint-scope@8.2.0',
   0.678 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.678 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.678 npm WARN EBADENGINE }
   0.680 npm WARN EBADENGINE Unsupported engine {
   0.680 npm WARN EBADENGINE   package: 'eslint-visitor-keys@4.2.0',
   0.680 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.680 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.680 npm WARN EBADENGINE }
   0.680 npm WARN EBADENGINE Unsupported engine {
   0.680 npm WARN EBADENGINE   package: 'espree@10.3.0',
   0.680 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.680 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.680 npm WARN EBADENGINE }
   0.680 npm WARN EBADENGINE Unsupported engine {
   0.680 npm WARN EBADENGINE   package: 'eslint-visitor-keys@4.2.0',
   0.680 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.680 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.680 npm WARN EBADENGINE }
   0.681 npm WARN EBADENGINE Unsupported engine {
   0.681 npm WARN EBADENGINE   package: 'globals@15.9.0',
   0.681 npm WARN EBADENGINE   required: { node: '>=18' },
   0.681 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.681 npm WARN EBADENGINE }
   0.682 npm WARN EBADENGINE Unsupported engine {
   0.682 npm WARN EBADENGINE   package: 'typescript-eslint@8.19.0',
   0.682 npm WARN EBADENGINE   required: { node: '^18.18.0 || ^20.9.0 || >=21.1.0' },
   0.682 npm WARN EBADENGINE   current: { node: 'v16.20.2', npm: '8.19.4' }
   0.682 npm WARN EBADENGINE }
   555.6 npm ERR! code FETCH_ERROR
   555.6 npm ERR! errno FETCH_ERROR
   555.6 npm ERR! network timeout at: https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz
   555.6 
   555.6 npm ERR! A complete log of this run can be found in:
   555.6 npm ERR!     /root/.npm/_logs/2025-10-11T08_19_19_138Z-debug-0.log
   ------
   Dockerfile:21
   
   --------------------
   
     20 |     
   
     21 | >>> RUN npm ci && \
   
     22 | >>>   npm run build
   
     23 |     
   
   --------------------
   
   target superset-websocket: failed to solve: process "/bin/sh -c npm ci &&   npm run build" did not complete successfully: exit code: 1
   ```
   
   
   Any thoughts? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] docker compose up --build fails on 5.0.0 with No matching distribution found for uv [superset]

Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas commented on issue #35607:
URL: https://github.com/apache/superset/issues/35607#issuecomment-4748305447

   This is a build/toolchain issue against the older 5.0.0 source tag. Closing as the Docker build has moved on since — please try building from a current release tag or master and open a fresh issue if you still hit a build failure.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org


Re: [I] docker compose up --build fails on 5.0.0 with No matching distribution found for uv [superset]

Posted by "rusackas (via GitHub)" <gi...@apache.org>.
rusackas closed issue #35607: docker compose up --build fails on 5.0.0 with No matching distribution found for uv
URL: https://github.com/apache/superset/issues/35607


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org