Package Details: vesktop-git 1.5.3.r22.g5d675ef-1

Git Clone URL: https://aur.archlinux.org/vesktop-git.git (read-only, click to copy)
Package Base: vesktop-git
Description: A standalone Electron-based Discord app with Vencord & improved Linux support
Upstream URL: https://github.com/Vencord/Vesktop
Licenses: GPL-3.0-only
Conflicts: vesktop
Provides: vesktop
Submitter: xiota
Maintainer: xiota (zt64, Covkie)
Last Packager: xiota
Votes: 7
Popularity: 0.031916
First Submitted: 2024-01-23 02:15 (UTC)
Last Updated: 2024-11-07 20:49 (UTC)

Required by (3)

Sources (4)

Latest Comments

1 2 3 4 5 6 .. 8 Next › Last »

Covkie commented on 2025-01-26 22:41 (UTC)

A postInstall script was pushed upstream which causes pnpm to be run directly, escaping corepack :p for now use vesktop. If vee doesn't revert it I'll push a patch

ginnokami commented on 2025-01-26 14:39 (UTC)

Anyone else having an issue building now? Getting the following error

Lockfile is up to date, resolution step is skipped
Packages: +665
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 0, reused 0, downloaded 1, added 0

   ╭──────────────────────────────────────────────────────────────────╮
   │                                                                  │
   │                Update available! 9.1.0 → 9.15.4.                 │
   │   Changelog: https://github.com/pnpm/pnpm/releases/tag/v9.15.4   │
   │     Run "corepack prepare pnpm@9.15.4 --activate" to update.     │
   │                                                                  │
   │      Follow @pnpmjs for updates: https://twitter.com/pnpmjs      │
   │                                                                  │
   ╰──────────────────────────────────────────────────────────────────╯

Packages are hard linked from the content-addressable store to the virtual store.
  Content-addressable store is at: /build/.local/share/pnpm/store/v3
  Virtual store is at:             node_modules/.pnpm
Progress: resolved 0, reused 0, downloaded 468, added 483
Progress: resolved 0, reused 0, downloaded 640, added 664
Progress: resolved 0, reused 0, downloaded 641, added 665, done
node_modules/electron postinstall$ node install.js
node_modules/esbuild postinstall$ node install.js
node_modules/tsx/node_modules/esbuild postinstall$ node install.js
node_modules/@vencord/venmic install$ pkg-prebuilds-verify ./lib/options.js || cmake-js compile --CDvenmic_addon=ON
node_modules/esbuild postinstall: Done
node_modules/tsx/node_modules/esbuild postinstall: Done
node_modules/@vencord/venmic install: Done
node_modules/electron postinstall: Done


> vesktop@1.5.4 postinstall /build/vesktop-git/src/vesktop
> pnpm updateArrpcDB

sh: line 1: pnpm: command not found
 ELIFECYCLE  Command failed.
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Build failed, check /var/lib/aurbuild/x86_64/gin/build

ninetailedtori commented on 2025-01-23 19:50 (UTC)

@xiota why not just submit PRs? If you have fixes you can just PR it. It's not considered good form to use the same name and repo tag if you're going to edit the code, rather please fork it separately if you'd rather self-maintain, then rename your package. Please leave vesktop-git as raw vesktop-git pulled by PKGBUILD.

xiota commented on 2024-11-27 19:07 (UTC)

@zt64 My plan was to disown this package after new maintainers demonstrated ability to maintain it. However, defects were left unresolved for months after comment describing them. So I went ahead and pushed the changes. I currently plan to remain hands off as long as problems are addressed in a timely manner and my fixes are not reverted.

zt64 commented on 2024-11-27 18:21 (UTC)

@xiota Hello, we use aurpublish on the GitHub repository to simplify maintaining the other vesktop packages. And would prefer for changes to be made through there. Direct write permission is unneeded and can be done through PRs instead. I would also like to ask why not transfer over the package to one of us? It would make sense for the official vencord aur maintainers to actually maintain the packages fully.

xiota commented on 2024-11-27 18:02 (UTC) (edited on 2024-11-27 18:03 (UTC) by xiota)

@Covkie If I am given write permissions to the repo in question, I will consider making changes there. However, AUR is an independent entity and should be maintained as such.

I had pushed the changes only because defects were not addressed in a timely manner.

Covkie commented on 2024-11-27 17:27 (UTC)

@ChrisLane the -bin package is unrelated and maintained my a separate person.

@xiota Hi I noticed you pushed some changes directly to the aur. We are hosting these over at https://github.com/vencord/pkgbuilds so it'd be appreciated if changes were done through there then pushed up here with aurpublish. Thanks

ChrisLane commented on 2024-11-27 11:34 (UTC)

Is there a reason this package doesn't use a similar vesktop.sh file to the vesktop-bin package? I noticed my launch flags weren't working when I switched to this package due to the config file being in a different place.

svenstaro commented on 2024-11-05 17:21 (UTC)

Shouldn't this also conflict with vesktop?

xiota commented on 2024-10-09 01:51 (UTC)

@ginnokami zt64 fixed it.

1 2 3 4 5 6 .. 8 Next › Last »