-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andrew Reilly wrote:
Problem solved!
In case anyone is interested, or has encountered a similar
problem, I believe that my problem was that somehow my
/var/db/pkg directory had a whole pile of near-duplicate entries
corresponding to port
On Tue, Jul 28, 2009 at 09:23:03AM +0200, Václav Haisman wrote:
Andrew Reilly wrote:
Problem solved!
In case anyone is interested, or has encountered a similar
problem, I believe that my problem was that somehow my
/var/db/pkg directory had a whole pile of near-duplicate entries
On Mon, Jul 27, 2009 at 06:13:07PM -0700, Doug Barton wrote:
On Tue, 28 Jul 2009, Andrew Reilly wrote:
corresponding to port revisions. Portmaster was checking the
installed version against the MD5 hashes in the old version
+CONTENTS file, and they weren't matching.
FYI, portmaster doesn't
On Tue, 28 Jul 2009, Andrew Reilly wrote:
On Mon, Jul 27, 2009 at 06:13:07PM -0700, Doug Barton wrote:
On Tue, 28 Jul 2009, Andrew Reilly wrote:
corresponding to port revisions. Portmaster was checking the
installed version against the MD5 hashes in the old version
+CONTENTS file, and they
Problem solved!
In case anyone is interested, or has encountered a similar
problem, I believe that my problem was that somehow my
/var/db/pkg directory had a whole pile of near-duplicate entries
corresponding to port revisions. Portmaster was checking the
installed version against the MD5 hashes
On Tue, 28 Jul 2009, Andrew Reilly wrote:
Problem solved!
Well I'm glad to hear that in any case. :)
In case anyone is interested, or has encountered a similar
problem, I believe that my problem was that somehow my
/var/db/pkg directory had a whole pile of near-duplicate entries
Hi all,
I've spent the weekend doing a ports catch-up: there seems to
have been a lot of activity recently! It's taking a long time
at least partly because portmaster doesn't seem to be doing the
right thing all of a sudden: it will happily trace the
dependencies and build the first superceded
