Arch Linux User Repository

Note on getting the git signing public key. Any of the following:

1) Get fresh copy of the package (on this page Package Actions Download Snapshot) Unpack tar file and the key will be in keys/pgp:

gpg --import < keys/pgp/*.asc

2) Available on github (same account as the package source): https://github.com/gene-git/blog/tree/master/git-keys

3) From authors website : https://www.sapience.com/tech

4) via WKD curl $(gpg-wks-client --print-wkd-url arch@sapience.com) | gpg --import

Note on getting the git signing public key. Any of the following:

1) Get fresh copy of the package (on this page Package Actions Download Snapshot) Unpack tar file and the key will be in keys/pgp:

gpg --import < keys/pgp/*.asc

2) Available on github (same account as the package source): https://github.com/gene-git/blog/tree/master/git-keys

3) From authors website : https://www.sapience.com/tech

4) via WKD curl $(gpg-wks-client --print-wkd-url arch@sapience.com) | gpg --import

Terrific!

Let me know if anything else isn't working for you.

solved with
curl $(gpg-wks-client --print-wkd-url arch@sapience.com) | gpg --import
thx.

Thanks - Expanding a bit on my comment in

https://aur.archlinux.org/packages/ssl-mgr#comment-1004774

the key is not uploaded to any pgp key servers as key servers have been replaced by WKD (web key directory).

There are 3 ways to get the key:

1) The simplest way is simply to import the key directly from the file provided with the package. gpg --import < keys/pgp/*.asc

2) It is also available from the author's website (www.sapience.com/tech). Download and import the key.

3) Using Web Key Directory ( WKD ).

Note that gpg is known to have trouble with some higher security website likely from a bug in gnutls library it uses for TLS negotiation with websites.

You can try it : gpg --auto-key-locate wkd --locate-key arch@sapience.com

If gpg has trouble with WKD then you can instead use:

curl $(gpg-wks-client --print-wkd-url arch@sapience.com) | gpg --import

where gpg-wks-client will simply print the url of the WKD entry for the provided email. Curl fetches it and gpg then imports it.

Let me know if you have any further trouble getting the public key into your keyring.

:: PGP keys need importing:
-> 7CCA1BA66669F3273DB52678E5B81343AB9809E1, required by: ssl-mgr kea_config process-mem lockmgr python-pynotify wg_tool
:: Importing keys with gpg...
gpg: ricezione dal keyserver fallita: Dati assenti

@TrialnError - yeh I agree - was hacky - removed.

thanks for pointing it out.

Hello GeneArch,
The changelog related changes are odd in more than one way from my viewpoint.
Either the changelog file exists beside the PKGBUILD or not. It is not intended to point to a file which may come with the sources. The use of touch is just a hack to work around that. See the entry in the PKGBUILD man-page.
And the original intend was to document packaging changes and not changes in the software. If the software provides a changelog it could be installed in the respective /usr/share/doc/wg_tools location. $startdir is one of the variables which shouldn't be used in a PKGBUILD. And please do not copy some file from the sources back into that location oO This could be whatever, which gets included with the package and if interpret could do whatever in the end. Theoretical worst case which I paint there, but just to bring the point home that this shouldn't be done as it tampers with files outside of $srcdir and $pkgdir.
Which brings me to the last point: the package() function isn't the place for such a thing. If a refresh would be necessary, prepare(), build() or even placing it in source would be more fitting. But why updating the changelog at all? This installs a fixed pkgver of the program. Refreshing the changelog from master contains changes which aren't available with the package.

Excellent - thanks!

solved... thaks :-)))

Hi @simona - as far as I know all the code is compatible with python 3.12 (and 3.13 best I can tell)

If you haven't already done so, please simply rebuild the package so that it installs itself in /usr/lib/python3.12/site-packages/wg_tool.

Let me know if you encounter any issues. If you have any problems, please file bug reports at my github source page:

https://github.com/gene-git/wg_tool/issues

FYI, you can see the Changelog using:

"pacman -Qc wg_tool"

Thank you!