Date: Tue, 16 Oct 2012 12:02:29 -0400 (EDT) From: Darrel <levitch@iglou.com> To: Matthew Seaman <matthew@FreeBSD.org> Cc: current@freebsd.org Subject: [solved]: pkgng | portmaster Message-ID: <alpine.GSO.2.00.1210161159320.23421@shell1> In-Reply-To: <507C5292.4050604@FreeBSD.org> References: <alpine.GSO.2.00.1210151312020.14501@shell1> <507C5292.4050604@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Hello, >> >> Concerning the new pkg system, I reckon that my port updates can take a >> drought. >> >> Would it be best to deinstall portmaster for now? Portmaster typically >> updates itself, but this might be a special case. >> >> Currently, my postmaster run ends like this: >> >> ===>>> Cannot continue >> ===>>> Aborting update >> >> ===>>> No ORIGIN in /var/db/pkg/portmaster-3.14/+CONTENTS >> >> ===>>> No ORIGIN in /var/db/pkg/postgresql-client-9.2.1/+CONTENTS >> >> ===>>> No ORIGIN in /var/db/pkg/postgresql-docs-9.2.1/+CONTENTS >> >> ===>>> No ORIGIN in /var/db/pkg/postgresql-server-9.2.1/+CONTENTS >> >> Terminated >> (48) @ 12:58:40> > > Did you apply the pkgng compatibility patch to portmaster? It's > available in ports-mgmt/portmaster now if you select the option in the > config dialogue. > Yes, I found the patch. > Once patched, portmaster should interoperate with pkgng pretty smoothly. > Certainly it should be using pkgng's local.sqlite database to pull out > package contents rather than trying to parse +CONTENTS files. > Thanks, Matthew! Darrel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.2.00.1210161159320.23421>