PKG_PATH change in Current

[shep]

This morning I attempted to update my amd64-current system and my usual update sequence revealed a change.

Heffalump$ cat .profile
# $OpenBSD: dot.profile,v 1.4 2005/02/16 06:56:57 matthieu Exp $
#
# sh/ksh initialization

PATH=$HOME/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/games:.
PKG_PATH=http://ftp.fr.openbsd.org/pub/OpenBSD/snapshots/packages/amd64
#PKG_PATH=/home/jsh/Downloads
PS1='\h\$ '
TERM="rxvt-256color"
MPD_HOST=${HOME}/.mpd/socket
ulimit -d 4096000

# pkg_add -u
Error from http://ftp.fr.openbsd.org/pub/OpenBSD/5.9/packages/amd64/
ftp: Error retrieving file: 404 Not Found
http://ftp.fr.openbsd.org/pub/OpenBSD/5.9/packages/amd64/ is empty

I think I can work around this by exporting the path as set in my .profile but I am wondering what changes have been implemented and if there are any recommendations about package updating during the beta phase.

[jggimi]

The change is the usual release engineering step as the transition to 5.9-release begins. Yes, you can edit pkg.conf(5) or use a PKG_PATH variable temporarily. Once the new release is tagged, and development picks up again, you won't have this issue. Until 6.0 release engineering begins.

[shep]

I should have been more specific. I had the snapshot PKG_PATH defined in my user profile. An xterm opened as user -> su -> pkg_add -u returned the 5.9 package path. My past recollection is that my xterm has always respected my profile settings.

Heffalump$ echo $PKG_PATH
http://ftp.fr.openbsd.org/pub/OpenBSD/snapshots/packages/amd64
Heffalump$ su
Password:
# pkg_add -u
Error from http://ftp.fr.openbsd.org/pub/OpenBSD/5.9/packages/amd64/
ftp: Error retrieving file: 404 Not Found
http://ftp.fr.openbsd.org/pub/OpenBSD/5.9/packages/amd64/ is empty

Never Mind - there was a mangled "export" line in my .profile