Date: Sun, 5 Jul 2020 09:49:25 +0200 From: Kurt Jaeger <pi@opsec.eu> To: Christoph Moench-Tegeder <cmt@burggraben.net> Cc: ports@freebsd.org Subject: Re: why does pkg try to install an older version of pkg ? Message-ID: <20200705074925.GJ39563@home.opsec.eu> In-Reply-To: <20200704132841.GG39563@home.opsec.eu> References: <20200704121238.GC39563@home.opsec.eu> <20200704123027.GB96403@elch.exwg.net> <20200704123652.GD39563@home.opsec.eu> <20200704125106.GC96403@elch.exwg.net> <20200704132841.GG39563@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > > You could grab packagesite.txz from your repo, untar that and then > > grep '"name":"pkg"' packagesite.yaml > > Any brokenness in /var/db/pkg/ ? > > How would I recognize brokenness ? The files that should be there > are there. > > > There's a per-repo sqlite3 database which you could query like this: > > select name, origin, version from packages where name = 'pkg'; > I've tried, and it showed pkg-1.14.6 as it should be. So, had a second system, same pkg-version before, and it has the same problem. sqlite> select name, origin, version from packages where name = 'pkg'; pkg|ports-mgmt/pkg|1.14.6 > Status-update: Our package builder (repo.nepustil.net) finished > build for a new pkg-repo, and now the upgrade went through without > regression to pkg-1.10.5_1 8-} Well, this did not help for the second system with that problem 8-( -- pi@opsec.eu +49 171 3101372 Now what ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200705074925.GJ39563>