Package Details: quarto-cli 1.7.31-1

Git Clone URL: https://aur.archlinux.org/quarto-cli.git (read-only, click to copy)
Package Base: quarto-cli
Description: Quarto is an open-source scientific and technical publishing system built on [Pandoc](https://pandoc.org)
Upstream URL: https://quarto.org/
Licenses: MIT
Conflicts: quarto-cli-bin, quarto-cli-bin-pre-release, quarto-cli-git, quarto-cli-pre-release
Provides: quarto
Submitter: trap000d
Maintainer: harrietobrien
Last Packager: harrietobrien
Votes: 7
Popularity: 0.001495
First Submitted: 2022-03-06 08:39 (UTC)
Last Updated: 2025-06-04 22:47 (UTC)

Latest Comments

1 2 Next › Last »

bgme commented on 2025-06-22 09:48 (UTC) (edited on 2025-06-22 09:50 (UTC) by bgme) 

conflicts=("quarto-cli-bin"
           "quarto-cli-pre-release"
           "quarto-cli-bin-pre-release"
           "quarto-cli-git")
options=(!strip)
https://github.com/quarto-dev/quarto-cli/releases/download/v1.7.31/quarto-1.7.31-linux-amd64.tar.gz
source=("https://github.com/quarto-dev/$pkgname/releases/download/v$pkgver/$provides-$pkgver-linux-amd64.tar.gz"
        "https://archive.archlinux.org/packages/d/deno/deno-$_denover-x86_64.pkg.tar.zst"
        "https://github.com/b-fuze/deno-dom/archive/refs/tags/v$_denodomver.tar.gz"
        "000_pandoc_lua.diff")

The line 30 need to be removed. 

$ extra-x86_64-build
[sudo] password for build: 
:: Synchronizing package databases...
 core downloading...
 extra downloading...
:: Starting full system upgrade...
 there is nothing to do
==> Building in chroot for [extra] (x86_64)...
==> Synchronizing chroot copy [/var/lib/archbuild/extra-x86_64/root] -> [arch]...done
/tmp/quarto-cli/PKGBUILD: line 30: https://github.com/quarto-dev/quarto-cli/releases/download/v1.7.31/quarto-1.7.31-linux-amd64.tar.gz: No such file or directory
==> Making package: quarto-cli 1.7.31-1 (Sun Jun 22 17:49:55 2025)
==> Retrieving sources...
  -> Found quarto-1.7.31-linux-amd64.tar.gz
  -> Found deno-2.2.9-1-x86_64.pkg.tar.zst
  -> Found v0.1.41-alpha-artifacts.tar.gz
  -> Found 000_pandoc_lua.diff
==> Validating source files with sha256sums...
    quarto-1.7.31-linux-amd64.tar.gz ... Passed
    deno-2.2.9-1-x86_64.pkg.tar.zst ... Passed
    v0.1.41-alpha-artifacts.tar.gz ... Passed
    000_pandoc_lua.diff ... Passed
/startdir/PKGBUILD: line 30: https://github.com/quarto-dev/quarto-cli/releases/download/v1.7.31/quarto-1.7.31-linux-amd64.tar.gz: No such file or directory
==> Making package: quarto-cli 1.7.31-1 (Sun Jun 22 09:49:58 2025)
==> Checking runtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for conflicting packages...

phel commented on 2024-12-13 18:29 (UTC)

Same here - the package seems to be almost empty after the build.

kbipinkumar commented on 2024-12-10 18:10 (UTC) (edited on 2024-12-10 18:22 (UTC) by kbipinkumar)

as of version 1.6.39-1 this package has following critical errors

quarto-cli W: ELF file ('usr/lib/quarto-cli/bin/tools/x86_64/deno_dom/libplugin.so') lacks GNU_PROPERTY_X86_FEATURE_1_SHSTK.
quarto-cli W: Directory (usr/src/debug/quarto-cli) is empty
quarto-cli W: Directory (usr/lib/quarto-cli/share) is empty
quarto-cli E: Uncommon license identifiers such as 'MIT' require license files below /usr/share/licenses/quarto-cli/ or switching to common license identifiers. Found 0/1 required license files.
quarto-cli E: Symlink (usr/bin/quarto) points to non-existing /usr/lib/quarto-cli/bin/quarto
quarto-cli E: Symlink (usr/lib/quarto-cli/bin/tools/x86_64/dart-sass/sass) points to non-existing /usr/bin/sass
quarto-cli E: Symlink (usr/lib/quarto-cli/bin/tools/x86_64/deno) points to non-existing /usr/bin/deno
quarto-cli E: Symlink (usr/lib/quarto-cli/bin/tools/x86_64/esbuild) points to non-existing /usr/bin/esbuild
quarto-cli E: Symlink (usr/lib/quarto-cli/bin/tools/x86_64/typst) points to non-existing /usr/bin/typst

once installed executing quarto by calling '/usr/bin/quarto' gives following error

bash: /usr/bin/quarto: No such file or directory

checking ${pkgdir} also shows quarto executable not being present at the expected location

tree $CHROOT/<user>/build/quarto-cli/pkg/quarto-cli/usr/lib/quarto-cli/bin 
/home/<user>/chroot/<user>/build/quarto-cli/pkg/quarto-cli/usr/lib/quarto-cli/bin
└── tools
    ├── pandoc -> /usr/bin/pandoc
    └── x86_64
        ├── dart-sass
        │   └── sass -> /usr/bin/sass
        ├── deno -> /usr/bin/deno
        ├── deno_dom
        │   └── libplugin.so
        ├── esbuild -> /usr/bin/esbuild
        ├── pandoc -> /usr/bin/pandoc
        └── typst -> /usr/bin/typst

trap000d commented on 2024-09-24 00:54 (UTC)

I have to maintain all quarto packages only as dependencies of RStudio. Since I've retired from keeping rstudio-desktop, I would also drop quarto. Arch maintainers planned to move it from AUR to 'extra'. This might be a good occasion.

trap000d commented on 2024-06-06 07:53 (UTC)

Hi @cbrnr,

Indeed, quarto-cli looks quite stable and predictable. So I'd be happy to move it to extra (though I'm not aware of details of this process).

cbrnr commented on 2024-06-06 07:15 (UTC)

Now that 1.4 has been out for quite a while, I wanted to ask about the plan to migrate this package to [extra] – still any major blockers? It seems like they now use a fairly recent Deno version (for quarto 1.5 they use 1.41, not entirely sure about 1.4).

trap000d commented on 2024-01-23 19:54 (UTC)

Hi @damir,

Correct, 'stable' quarto-cli can be built only against pretty old deno version (<1.29). In the future if/when Quarto developers will announce new stable release (1.4.xyz) it should become buildable again.

You have several options to override it: 1) Binary packages quarto-cli-bin and quarto-cli-bin-pre-release have all components bundled

2) source packages quarto-cli-pre-release and quarto-cli-git are built with the most recent deno.

3) Install old deno 1.28.x from repo archives (not the best idea, though)

damir commented on 2024-01-23 15:55 (UTC) (edited on 2024-01-23 15:56 (UTC) by damir)

cannot build against an existing deno: 

==> Finished making: deno-git 1.9.2.r10614.g137f1a0c6836-1 (Tue 23 Jan 2024 16:49:37)
==> Cleaning up...


loading packages...
resolving dependencies...
looking for conflicting packages...
:: deno-git and deno are in conflict. Remove deno? [y/N] y

Packages (2) deno-1.39.4-1 [removal]  deno-git-1.9.2.r10614.g137f1a0c6836-1

Total Installed Size:  90.20 MiB
Net Upgrade Size:       3.87 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                                          [########################################################################] 100%
(1/1) checking package integrity                                                                                        [########################################################################] 100%
(1/1) loading package files                                                                                             [########################################################################] 100%
(1/1) checking for file conflicts                                                                                       [########################################################################] 100%
(2/2) checking available disk space                                                                                     [########################################################################] 100%
:: Processing package changes...
(1/1) removing deno                                                                                                     [########################################################################] 100%
(1/1) installing deno-git                                                                                               [########################################################################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Log Orphan Packages
The following packages are installed but not required (anymore):
dart-sass
esbuild
lua-lpeg
soci
yarn
You can mark them as explicitly installed with 'pacman -D --asexplicit <pkg>' or remove them all using 'pacman -Qtdq | pacman -Rns -'
==> Making package: quarto-cli 1.3.450-1 (Tue 23 Jan 2024 16:52:27)
==> Checking runtime dependencies...
==> Missing dependencies:
  -> deno>=1.28
  -> deno<1.29
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
 -> error making: quarto-cli-exit status 8
 -> Failed to install the following packages. Manual intervention is required:
quarto-cli - exit status 8

alerque commented on 2023-12-05 09:40 (UTC)

I'd like to get this migrated to [extra] someday and am evaluating where it is at now. The build is pretty messy, but obviously a lot of that is the result of a messy upstream build process. I think we'll have to get it cleaned up a bit tighter before I migrate though. For example rather than removing junk in package() after the fact, I think we'll need to patch the build to not produce the junk in the first place. Before I get two far down that road though can you comment on the current situation with deno? Are version bumps to that package going to be a problem for this one down the road?

trap000d commented on 2022-08-05 21:33 (UTC) (edited on 2022-08-05 21:41 (UTC) by trap000d)

Hi @titaniumbones,

https://github.com/quarto-dev/quarto-cli/issues/1174

https://github.com/quarto-dev/quarto-cli/pull/1518

There is no solution for this yet, until quarto devs manage to move to latest Deno. Either downgrade deno to 22.3...

...or patch quarto sources. Here is my experimental PKGBUILD for that:

https://github.com/trap000d/aur/tree/master/quarto-cli

Alternatively, remove quarto-cli, remove deno version check in PKGBUILD, then build rstudio-desktop without quarto.

1 2 Next › Last »