From b...@freebsd.org Tue Jul 31 15:36:34 2012
>=20
> And can you tgz and send me your /var/db/pkg directory?
>=20
> http://seis.bris.ac.uk/~mexas/var_db_pkg.tar.xz
>=20
You can't mix both pkgng and pkg_install, and looking at your
/var/db/pkg, =
you
have mixed it for a while and you now have both the pkgng version and
the
pkg_install version half migrated to pkgconf and inconsistent.
As I don't the the manipulation you have exactly done, and the exact
state =
of
your system, it is hard for me to tell you how to recover.
In any case this as nothing to do with portmaster.
if you decide to fully go the pkgng way what I do suggest is:
remove all the directories from /var/db/pkg (keeping only the
local.sqlite =
file)
then run=20
echo "delete from deps where origin=3D'devel/pkg-config'; update deps
set o=
rigin=3D'devel/pkgconf', name=3D'pkgconf', version=3D'0.8.4' where
origin=
=3D'devel/pkg-config';" | pkg shell
I tested with your database this seems to work.
after that you can upgrade safely everything.
Remember, do not mix pkg_install and pkgng, if you decide to go pkgng
this =
is a
one shot migration.
I'll look at this later, but..
I've *never* once used pkg_install,
not even before pkgng. I switched
to pkgng quite early, and since
then I used exclusively pkg and
portmaster, nothing else.
So pkg_install must've been called
by either pkg or portmaster.
One possibility is that I didn't always
apply the pkgng portmaster patch correctly.
Thanks
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
