upstream url is now dbgate.io

Can confirm @SoftExpert's solution works.

It points to the same place the files are stored in the prepare() step of PKGBUILD.

7.1.9-1 fails to build with the following error:

==> Starting package()...
cp: cannot stat '/var/tmp/pamac-build-marian/dbgate-bin/src/usr/lib/dbgate/resources/.': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

It requires a change in PKGBUILD at line 49: cp -a "${srcdir}/opt/${_pkgname}/resources/". "${pkgdir}/usr/lib/${pkgname%-bin}/"

@Dominiquini, please carefully check the latest version 6.7.1. It does not have a deb package released—only the premium version has an AppImage file available. Next time, could you first confirm whether the corresponding precompiled version exists before marking it as outdated?

I had the same issue with the 30Gb download for Electron 30. My new build Arch had V37. With a little ChatGPT help I got it installed:

PKGBUILD

1. Hardcoded electron30 removed.
2. Dependency changed to electron37.
3. sed now replaces @electronversion@ with 37 instead of 30.

dbgate.sh

1. electron@electronversion@ replaced with electron37.

SHA256SUM

I had to recreate for the dbgate.sh file.

Hope it helps someone.

I always have issues when trying to install dbgate-bin.
I assume it's because of the large size of the Electron package.
How can I fix this?

I have electron 34 and 35 installed, this pkgbuild still tries to install electron 30 from source, and for some reason tries to download in excess of 30GB

nodejs-lts-iron-20.18.3-1 and nodejs-23.9.0-1 are in conflict

Can be fixed by upgrading electron to 34

I noticed the change to the dbgate.bin script in the latest "fix errors" commit.

A section was added to read flags from a flags file, if it exists:

_FLAGS_FILE="${XDG_CONFIG_HOME}/@appname@-flags.conf"
declare -a flags
if [[ -f "${_FLAGS_FILE}" ]]; then
    mapfile -t < "${_FLAGS_FILE}"
fi
for line in "${MAPFILE[@]}"; do
    if [[ ! "${line}" =~ ^[[:space:]]*#.* ]] && [[ -n "${line}" ]]; then
        flags+=("${line}")
    fi
done

And then I assume the intent was to use those flags, however _USER_FLAGS was used instead of flags:

if [[ "${EUID}" -ne 0 ]] || [[ "${ELECTRON_RUN_AS_NODE}" ]]; then
    exec electron@electronversion@ "${_RUNNAME}" "${_OPTIONS}" "${_USER_FLAGS}" "$@" || exit $?
else
    exec electron@electronversion@ "${_RUNNAME}" "${_OPTIONS}" --no-sandbox "${_USER_FLAGS}" "$@" || exit $?
fi

So I'm guessing the declare -a flags and flags+= lines should be _USER_FLAGS instead.

Also, if you were intending these flags to be interpreted as separate command line arguments rather than just using the first line that was found, you need to change the usage of _USER_FLAGS to:

"${_USER_FLAGS[@]}"

Thus the last few lines should look like:

if [[ "${EUID}" -ne 0 ]] || [[ "${ELECTRON_RUN_AS_NODE}" ]]; then
    exec electron@electronversion@ "${_RUNNAME}" "${_OPTIONS}" "${_USER_FLAGS[@]}" "$@" || exit $?
else
    exec electron@electronversion@ "${_RUNNAME}" "${_OPTIONS}" --no-sandbox "${_USER_FLAGS[@]}" "$@" || exit $?
fi