quarto-dev / quarto-dev/quarto-cli

Installing extension from private Gitlab repository

Open
#5,827 18 comments 20 reactions 1 assignee View on GitHub

@cderv is already working on this.

Since May 2, 2025.

enhancement extensions
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Bug description

I am having troubles by adding extensions from a GitLab repo, which I am developing. The extension seems to be downloaded but it fails when unzipping the zip-file.

Steps to reproduce
quarto add https://gitlab.cc-asp.fraunhofer.de/quarto-extensions/mdz/-/archive/main/shorty-main.zip
Expected behavior

The installed extension.

Actual behavior

An error message is retrieved:

Quarto extensions may execute code when documents are rendered. If you do not 
trust the authors of the extension, we recommend that you do not install or 
use the extension.
 ? Do you trust the authors of this extension (Y/n) › Yes
[✓] Downloading
(|) Unzipping
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
[✓] Unzipping
ERROR: Failed to unzip extension.

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Your environment
  • IDE: VScode
  • OS: Ubuntu
Quarto check output
[✓] Checking Quarto installation......OK
      Version: 1.2.335
      Path: /opt/quarto/bin

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.10.6
      Path: /usr/bin/python3
      Jupyter: 5.1.5
      Kernels: ir, python3

[✓] Checking Jupyter engine render....OK

[✓] Checking R installation...........OK
      Version: 4.1.2
      Path: /usr/lib/R
      LibPaths:
        - /home/miguel/R/x86_64-pc-linux-gnu-library/4.1
        - /usr/local/lib/R/site-library
        - /usr/lib/R/site-library
        - /usr/lib/R/library
      rmarkdown: 2.20

[✓] Checking Knitr engine render......OK

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.