maintainer-feedback requested: [Bug 206917] ports-mgmt/pkg: url: "file:///xxx" in repos.conf not working!

[bugzilla-noreply at freebsd.org]

ohartman at zedat.fu-berlin.de has reassigned Bugzilla Automation
<bugzilla at FreeBSD.org>'s request for maintainer-feedback to pkg at FreeBSD.org:
Bug 206917: ports-mgmt/pkg: url:    "file:///xxx" in repos.conf not working!
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206917



--- Description ---
Background:

Running CURRENT (FreeBSD 11.0-CURRENT #30 r295138: Tue Feb  2 09:32:43 CET 2016
amd64) with the lastes updates of ports tree (svn'ed) and using poudriere(8)
for local repository creation, I'm not capable of using a local repository via

url: "file:///xxxx"

in /usr/local/etc/pkg/repos/myrepo.conf

Ant try to install a package from that repository fails with the errors:

[...]
pkg:
file:///pool/poudriere/data/packages/head-amd64-head-default/.latest/meta.txz:
No such file or directory
repository myrepo has no meta file, using default settings
pkg:
file:///pool/poudriere/data/packages/head-amd64-head-default/.latest/packagesit
e.txz:
No such file or directory
Unable to update repository myrepo


The location provided is the package folder created by poudriere(8) and it
contains all the complained tarballs pkg needs, but they are symbolic links to
subfolder ".latest". The above shown error message is produced while delegatin
the url-target directly to subfolder ".latest" since I thought pkg wasn't
following symbolic links.

When simply exchanging the culprit url: tag in myrepo.conf with

url:		"pkg+http://pkg.FreeBSD.org/${ABI}/latest",

the very same remaining configuration setup works as expected!

I did not find any hints in the documentation about how to use local repos
situated in the local file systems or even the exclusion of the usage of those.

I can fetch(1) the files
ile:///pool/poudriere/data/packages/head-amd64-head-default/.latest/{meta.txz|p
ackagesite.txz}!

By simply exchanging the URL towards a remote repo as shown above, the
installation of packages works. This makes me suspect either a configuration
error (which is due to a very sparse documentation regarding file-based repos
then) or a bug. I assume latter.