I use Manjaro and just wanted to update my packages this week on two computers and it seems like the package keeps failing because there is a folder being created which already exists.
I get this message
==> Making package: gnome-shell-extension-material-shell 44-1 (Fri 05 Apr 2024 08:50:32 CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found gnome-shell-extension-material-shell-44.tar.gz
==> Validating source files with b2sums...
gnome-shell-extension-material-shell-44.tar.gz ... Passed
==> Extracting sources...
-> Extracting gnome-shell-extension-material-shell-44.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
up to date, audited 223 packages in 840ms
30 packages are looking for funding
run `npm fund` for details
2 moderate severity vulnerabilities
To address all issues, run:
npm audit fix
Run `npm audit` for details.
rm -rf dist
cp -r schemas dist
mkdir dist
glib-compile-schemas dist/schemas/
mkdir: cannot create directory ‘dist’: File exists
make: *** [Makefile:23: dist] Error 1
make: *** Waiting for unfinished jobs....
Error opening directory “dist/schemas/”: No such file or directory
make: *** [Makefile:8: schemas] Error 1
==> ERROR: A failure occurred in build().
Aborting...
Is there a lack of a check in the making process of the package? or is this something I can fix myself? I get this on all computers using the package
I use Manjaro and just wanted to update my packages this week on two computers and it seems like the package keeps failing because there is a folder being created which already exists.
I get this message
Is there a lack of a check in the making process of the package? or is this something I can fix myself? I get this on all computers using the package