Package Details: upscayl-git 2.15.1.r22.g5cf504f-1

Git Clone URL: https://aur.archlinux.org/upscayl-git.git (read-only, click to copy)
Package Base: upscayl-git
Description: Free and Open Source AI Image Upscaler.(Use system-wide electron)
Upstream URL: https://upscayl.org/
Keywords: ai electron esrgan gigapixel gigapixel-images image image-upscaling topaz upscale upscalerimage upscayl
Licenses: AGPL-3.0-only
Conflicts: upscayl
Provides: upscayl
Submitter: zxp19821005
Maintainer: zxp19821005
Last Packager: zxp19821005
Votes: 1
Popularity: 0.019237
First Submitted: 2023-11-29 09:13 (UTC)
Last Updated: 2025-02-10 07:43 (UTC)

Dependencies (12)

Required by (0)

Sources (2)

Latest Comments

1 2 Next › Last »

zxp19821005 commented on 2025-03-14 07:15 (UTC)

@xiota At present, there are only alarms in the namcap process, but the usage is completely normal.

xiota commented on 2025-03-07 03:55 (UTC)

@zxp19821005 Thanks for looking into it. I previously wasn't aware the program uses some prebuilt binaries. Perhaps this package could be revised to use aur/upscayl-ncnn.

zxp19821005 commented on 2025-03-03 07:44 (UTC)

@xiota The whole error log: upscayl-git E: Insecure RUNPATH '/home/runner/work/upscayl-ncnn/upscayl-ncnn/1.3.280.0/x86_64/lib' in file ('usr/lib/upscayl/bin/upscayl-bin') . The AI said : Modify the compilation settings or configuration file of upscayl bin to set RUNPATH to a secure and trusted path. For example, it can be modified to the system default library path or project specific security path: export LD_RUN_PATH=/usr/lib:/usr/local/lib. That file was provided by the upstream, so I think you should send an issue to the upstream.

xiota commented on 2025-03-02 03:36 (UTC)

@zxp19821005 namcap is reporting insecure-runpath on usr/lib/upscayl/bin/upscayl-bin. It's referencing a builder path that won't be available after install.

zxp19821005 commented on 2025-02-10 07:44 (UTC)

@dreieck The upstream seems to have fixed it yet. Can you try again?

dreieck commented on 2025-02-09 16:33 (UTC) (edited on 2025-02-09 23:00 (UTC) by dreieck)

Ahoj,

trying to build this, fails for me with

[...]
Errors in tr.json:
[...]
    message: "should have required property 'TITLE'"
[...]
Type error: Type '{ TITLE: string; INTRO: string; HEADER: { GITHUB_BUTTON_TITLE: string; DESCRIPTION: string; }; FOOTER: { NEWS_TITLE: string; COPYRIGHT: string; LINK_TITLE: string; }; SETTINGS: { TITLE: string; CHANGE_LANGUAGE: { ...; }; ... 19 more ...; SYSTEM_INFO: { ...; }; }; APP: { ...; }; ERRORS: { ...; }; UPSCAYL_CLOUD: { ......' is not assignable to type '{ TITLE: string; INTRO: string; HEADER: { GITHUB_BUTTON_TITLE: string; DESCRIPTION: string; }; FOOTER: { NEWS_TITLE: string; COPYRIGHT: string; TITLE: string; LINK_TITLE: string; }; SETTINGS: { TITLE: string; ... 20 more ...; SYSTEM_INFO: { ...; }; }; APP: { ...; }; ERRORS: { ...; }; UPSCAYL_CLOUD: { ...; }; ONBOARD...'.
  Types of property '"FOOTER"' are incompatible.
    Property '"TITLE"' is missing in type '{ NEWS_TITLE: string; COPYRIGHT: string; LINK_TITLE: string; }' but required in type '{ NEWS_TITLE: string; COPYRIGHT: string; TITLE: string; LINK_TITLE: string; }'.
[...]

↗ Upstream issue report with more context.


EDIT: ↗ This commit and ↗ this commit fix this issue.


Regards and thanks for the package!

aliu commented on 2025-01-03 04:03 (UTC)

Thanks! I also got an error for not locating musl (see below) and fixed it by installing musl, so that should probably be made a dependency.

 ⚠ Attempted to load @next/swc-linux-x64-gnu, but it was not installed
 ⚠ Attempted to load @next/swc-linux-x64-musl, but an error occurred: libc.musl-x86_64.so.1: cannot open shared object file: No such file or directory

This is all despite Upscayl using Babel instead of SWC. Node is weird.

and I got a JS out-of-memory error anyway. i guess that's not your problem, lol

zxp19821005 commented on 2025-01-03 03:29 (UTC)

@aliu Thanks for your feedback, fixed it.

aliu commented on 2025-01-02 21:27 (UTC)

build fails, ending in the following

npm error <string>:114: SyntaxWarning: invalid escape sequence '\/'
npm error gyp info spawn make
npm error gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
npm error ../common.cc:12:10: fatal error: napi.h: No such file or directory
npm error    12 | #include <napi.h>
npm error       |          ^~~~~~~~
npm error compilation terminated.
npm error make: *** [sharp-linuxglibc-x64.target.mk:142: Release/obj.target/sharp-linuxglibc-x64/common.o] Error 1
npm error gyp ERR! build error 
npm error gyp ERR! stack Error: `make` failed with exit code: 2
npm error gyp ERR! stack     at ChildProcess.onExit (/home/aliu/.cache/paru/clone/upscayl-git/src/upscayl.git/node_modules/node-gyp/lib/build.js:203:23)
npm error gyp ERR! stack     at ChildProcess.emit (node:events:517:28)
npm error gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:292:12)
npm error gyp ERR! System Linux 6.12.7-zen1-1.1-zen
npm error gyp ERR! command "/home/aliu/.cache/paru/clone/upscayl-git/src/.nvm/versions/node/v18.20.5/bin/node" "/home/aliu/.cache/paru/clone/upscayl-git/src/upscayl.git/node_modules/.bin/node-gyp" "rebuild" "--directory=src"
npm error gyp ERR! cwd /home/aliu/.cache/paru/clone/upscayl-git/src/upscayl.git/node_modules/sharp/src
npm error gyp ERR! node -v v18.20.5
npm error gyp ERR! node-gyp -v v9.4.1
npm error gyp ERR! not ok
npm error A complete log of this run can be found in: /home/aliu/.cache/paru/clone/upscayl-git/src/.npm_cache/_logs/2025-01-02T21_21_05_367Z-debug-0.log
==> ERROR: A failure occurred in prepare().
    Aborting...
error: failed to build 'upscayl-git-2.15.1.r3.g04db044-1': 
error: packages failed to build: upscayl-git-2.15.1.r3.g04db044-1

zxp19821005 commented on 2024-10-22 01:42 (UTC)

@tronicdude Thanks for your feedback, added it.