Arch Linux User Repository

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

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

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.

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).

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).

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)

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

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?

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.

Getting a dependency error when trying to install; dependency deno<1.23.0 leads yay to install deno-bin from AUR (version 1.20), but it appears that deno-bin doesn't actually fulfill the dependency:

==> Making package: quarto-cli 1.0.37-1 (Fri 05 Aug 2022 10:40:11 AM EDT) ==> Checking runtime dependencies... ==> Missing dependencies: -> deno<1.23.0 ==> Checking buildtime dependencies... ==> ERROR: Could not resolve all dependencies. -> error making: quarto-cli

Editing PKGBUILD to change the dependency to just "deno" and running makepkg manually gives a deno dependency issue concerning lodash, resulting i na build abort:

Creating Quarto Symlink Found 3 paths to try.

Trying /usr/local/bin/quarto Didn't create symlink at /usr/local/bin/quarto Trying ~/.local/bin/quarto Symlink created at /home/matt/.local/bin/quarto Success Download https://deno.land/x/cliffy@v0.24.2/command/mod.ts ... [many successful downloads] ... error: Import 'https://cdn.skypack.dev/-/lodash@v4.17.21-K6GEbP02mWFnLA45zAmi/dist=es2019,mode=imports/unoptimized/_setCacheAdd.js' failed: 500 Internal Server Error at https://cdn.skypack.dev/-/lodash@v4.17.21-K6GEbP02mWFnLA45zAmi/dist=es2019,mode=imports/unoptimized/_SetCache.js:2:26 ==> ERROR: A failure occurred in build(). Aborting...