Package Details: svgo 3.0.2-1

Git Clone URL: https://aur.archlinux.org/svgo.git (read-only, click to copy)
Package Base: svgo
Description: Tool for optimizing SVG files
Upstream URL: https://github.com/svg/svgo
Licenses: MIT
Conflicts: nodejs-svgo
Provides: nodejs-svgo
Replaces: nodejs-svgo
Submitter: flacks
Maintainer: alerque
Last Packager: alerque
Votes: 32
Popularity: 0.039954
First Submitted: 2018-07-24 18:35 (UTC)
Last Updated: 2022-12-20 17:44 (UTC)

Latest Comments

1 2 Next › Last »

alerque commented on 2021-08-18 05:13 (UTC)

@Tjuh That looks like something is wrong with your system, not this package. I compiled this the other day and just did it again now to check. In a clean chroot using makechrootpkg this builds just fine (if you want a really easy way to build that way install devtools then run extra-x86_64-build instead of makepkg to build). As for your system, perhaps reinstall npm / nodejs?

Tjuh commented on 2021-08-17 23:20 (UTC)

Won't build;

==> Starting package()...
/home/tjuh/Desktop/svgo/PKGBUILD: line 17: 20040 Segmentation fault      (core dumped) npm install -g --prefix "${pkgdir}/usr" "${srcdir}/${pkgname}-${pkgver}.tgz"
==> ERROR: A failure occurred in package().
    Aborting...
==> Removing installed dependencies...

simon04 commented on 2021-03-27 09:36 (UTC)

Thanks, fixed in 2.2.2-2 (what a lucky number) – https://aur.archlinux.org/cgit/aur.git/commit/?h=svgo&id=5c5bc629b2cd8662125731d1e1840c3008387431

eugene commented on 2021-03-23 16:16 (UTC)

npm install line should not have --user root as new guidelines suggest

flipflop97 commented on 2021-03-23 14:42 (UTC)

@1ace

Same issue with package semver

1ace commented on 2021-03-20 11:18 (UTC)

This package installs a bunch of files in /usr/lib/node_modules/root/ (as well as the normal /usr/lib/node_modules/svgo/), which conflicts with vscode-html-languageserver for instance as that package tries to do the same; I'm not sure if this "root" module is really a thing that should be installed ("root" may very well be a placeholder name), but I'm guessing neither packages should be doing this :)

PanisSupraOmnia commented on 2019-04-25 20:36 (UTC) (edited on 2019-04-25 20:44 (UTC) by PanisSupraOmnia)

Correct me if I'm wrong, but shouldn't the npm install line have --user root passed to it, per the Arch wiki? The current PKGBUILD causes the files to be owned by the installing user.

Edit: Also, you specify that the license is MIT; however, Arch takes MIT as a special case of a custom license, in that you need to install the license in the PKGBUILD because it has a copyright line. See the Arch wiki for details. I happened to notice these issues because I ran namcap on the package.

tensor5 commented on 2018-02-09 17:05 (UTC)

I've seen this issue in other npm packages, it didn't show up in my build though.

Calimero commented on 2018-02-09 14:35 (UTC) (edited on 2018-02-09 14:39 (UTC) by Calimero)

I wanted to ask for a fix of the permission issues: there are lots of files and directories with mode 777. But installing a second time fixes that, I'm not sure what's happening.

tensor5 commented on 2017-11-17 10:51 (UTC)

@Enverex, do you have that permission mismatch only on /usr/bin?

1 2 Next › Last »