@michaa7 Step 1: Don't do it, installing the deb file will take care of it.
It will also configure the repository.
Any user doing it the manual/old way got into trouble due to outdated keyring material added during this long forgotten step.
If you think you want to be paranoid: Avoid installing the deb package.
It will add an additional (unrestricted) repository entry and drop a cron script to keep it active.
To deploy new versions of the deb package content manually:
keep the keyring file up to date with
the repo version
download the deb file when a new release drops
extract the relevant parts of the package and place them wherever
#!/bin/sh
# extract vivaldi debian package content
arch="${1}"
dest="${2}"
# distributor signature source
keyring="/etc/apt/keyrings/vivaldi-browser.gpg"
# verify archive content
(ar p "${arch}" _gpgbuilder | gpg --verify "--keyring=${keyring}" -) || exit 1
sum=`ar p "${arch}" data.tar.xz | sha1sum | cut -d' ' -f1`
echo "${sum}"
(ar p "${arch}" _gpgbuilder | grep "${sum}" | cut -d' ' -f2,4) || exit 2
# extract '/opt' content
[ -n "${dest}" ] || dest='.'
ar p "${arch}" data.tar.xz | tar -C "${dest}" -xJf- --strip 2 ./opt
