pkg_add and 9.1RC3

[doug]

Doing pkg_add in the normal way:

pkg_add -r diffuse
Error: Unable to get
ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/diffuse.tbz:
File unavailable (e.g., file not found, no access)

To make it work:

setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/devel/
pkg_add -r diffuse-0.4.6_2

Is this just the way it is, or is there some magic to make it somewhat less
tedious?
_______________________________________________
freebsd-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"

[Polytropon]

On Mon, 12 Nov 2012 23:54:14 -0500 (EST), doug wrote:
> Doing pkg_add in the normal way:
>
> pkg_add -r diffuse
> Error: Unable to get
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/diffuse.tbz:
> File unavailable (e.g., file not found, no access)
>
> To make it work:
>
> setenv PACKAGESITE ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/devel/
> pkg_add -r diffuse-0.4.6_2
>
> Is this just the way it is, or is there some magic to make it somewhat less
> tedious?

I think this behaviour is "intended": RC3 is the 3rd release
candidate for 9.1-RELEASE. The candidate already reflects the
correct access path for the binary installs via pkg_add.

This path _will be_ correct as soon as 9.1 has been released.
But as it it's not _yet_, the files are not present at the
designated location.

As 9.1-RC3 is "on the path" of 9-STABLE, your approach of
accessing the STABLE-related access path looks valid.


--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...