The problem was between the chair and the monitor: I use sudo, but
TRUSTED_PKG_PATH was not in the env_keep list in /etc/sudoers. Now that
I've added TRUSTED_PKG_PATH to env_keep, I can export TRUSTED_PKG_PATH
in my ~/.bash and everything works as expected. I'm really sorry for the
noise.
None of these in my ~/.bashrc work:
export
TRUSTED_PKG_PATH=https://bruno%3AMyPassword%40gnuser.ddns.net/openbsd-bruno/6.4/packages/amd64
export
TRUSTED_PKG_PATH='https://bruno%3AMyPassword%40gnuser.ddns.net/openbsd-bruno/6.4/packages/amd64'
export
TRUSTED_PKG_PATH='https://bruno:mypassw...@gnus
I'm running 6.4-stable amd64 on my laptop. I have a repository on my
webserver where I keep custom packages (pardon the "gnuser" in url--the
domain predates my openbsd conversion). Accessing the repository
requires https, username, and password. Setting TRUSTED_PKG_PATH to my
repository has no effe
Thanks, Peter. On the one hand I'm sad not to have discovered a
previously unknown bug, on the other hand I'm happy that it's been fixed.
I'm on 6.4-stable so will try the workaround. Looking forward to 6.5!
-Bruno
>Synopsis: after booting, laptop connects to neighbor's open wifi
hotspot, which is not listed in my /etc/hostname.if
>Category: not sure, sorry (networking?)
>Environment:
System : OpenBSD 6.4
Details : OpenBSD 6.4 (GENERIC.MP) #6: Sat Jan 26 20:37:44 CET 2019
