okay, i updated all versions to recent -current and now pkg_add works
like expected; the versions were too different, obviously.
sorry for the noise.
Marc Espie schrieb:
On Wed, Oct 12, 2005 at 05:04:56PM +0200, Marc Peters wrote:
hi all,
i wanted to install a package on an box, which i built out of the
portstree via "make package". everything goes fine and the package is
available in "/usr/ports/packages/i386/cdrom/" and "../ftp/". i copied
the .tgz to the machine, where i wanted to install it on, but it failed
with the following error:
# pkg_add nut-2.0.0p0.tgz
Unknown element: @pkgpath sysutils/nut,no_cgi
i looked untarred it and looked through +CONTENTS and found following
lines regarding @pkgpath:
@pkgpath sysutils/nut,no_cgi
@pkgpath sysutils/nut,snmp
@pkgpath sysutils/nut,no_cgi,snmp
in other packages' +CONTENT, e.g. wget from ftp.openbsd.org, there are
no lines referring to this pkgpath. am i missing something in the
buildprocess for a package? i read the man page of bsd.port.mk(5),
ports(7) and pkg_add(1) but didn't find anything regarding this element
and how to turn this of in the process of "make package" and i didn't
find anything in the archives of marc.theaimsgroup.com regarding this
problem.
@pkgpath is a fairly recent addition to the package tools. The stuff
on the machines you built packages on obviously knows about it, since
pkg_create was able to create the packages. The machines you try to add
the package on doesn't know about it.
-stable vs. -current looks like the more likely explanation.
You won't find a way to turn this off. The OpenBSD ports tree doesn't work
that way, you don't turn stuff off. @pkgpath is a very useful addition
for the update process...
