Date: Mon, 17 Dec 2018 14:45:03 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-questions@freebsd.org Subject: Re: Problem with poudriere after updating to FreeBSD 12 Message-ID: <f90cd8a7-5436-0c86-36b3-e71029497740@infracaninophile.co.uk> In-Reply-To: <SN1PR20MB2109A84D49155C374FB47EFC80BC0@SN1PR20MB2109.namprd20.prod.outlook.com> References: <SN1PR20MB21092F6DBC8DD6E67A22E8BD80BC0@SN1PR20MB2109.namprd20.prod.outlook.com> <45ca0b0f-59f9-d169-1af7-fa09d99012ec@infracaninophile.co.uk> <SN1PR20MB2109A84D49155C374FB47EFC80BC0@SN1PR20MB2109.namprd20.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17/12/2018 14:24, Carmel NY wrote: > On Mon, 17 Dec 2018 14:12:31 +0000, Matthew Seaman stated: > >> On 17/12/2018 13:57, Carmel NY wrote: >>> So, I guess what I want to know is why is this error happening and how do I >>> correct it? I wanted to completely empty the repository but I don't know >>> how to do that safely. Other than that, how do I force poudriere to do a >>> complete rebuild of all the installed ports on this system using the >>> correct information? >> >> Update the poudriere jail to match your new OS version -- otherwise >> you'll end up building 11.x packages to install onto a 12.x system. It >> often turns out easiest/quickest to just delete the jail and re-install >> the new one. >> >> Poudriere will realise that the jail version has changed and will >> rebuild everything for you. However, to be super safe, use the '-c' >> option to your 'poudriere bulk' command, which cleans out the package >> repository before rebuilding it. This will rebuild _everything_ in your >> repo, so allow plenty of time. >> >> Cheers, >> >> Matthew > > My second approach was to delete the jail and then recreate it. That did > not seem to do the trick though. I will try the "-c" options to see if it will > rebuild everything. > > Thanks :) > Make sure that your .../pkg/repo/repo.conf file uses the $(ABI) token rather than spelling out your OS ABI explicitly -- or else don't have any version related parts to your repo path at all. Also, if your repo is served via a web server, check your webserver config to make sure your repo isn't pointed at an old set of packages. Cheers, Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f90cd8a7-5436-0c86-36b3-e71029497740>