Date: Sat, 7 Mar 2020 17:24:01 +0000 From: James Wright <james.wright@jigsawdezign.com> To: freebsd-ports@freebsd.org Subject: Re: Pkg repository is broken... Message-ID: <B598FDC5-CCEA-4FD2-A4E0-A8A75D1FAF07@jigsawdezign.com> In-Reply-To: <dd7b8b0d-05dd-e69d-ae1e-c6887a556009@gmail.com> References: <966320bd-cf2a-6168-9615-16ffd7e98555@umanwizard.com> <20200302175801.GA48484@lordsith.net> <20200304041614.GA92692@eureka.lemis.com> <20200306112944.GQ33086@e.0x20.net> <20200307003855.GG85938@eureka.lemis.com> <op.0g3qf5dikndu52@sjakie> <20200307125658.56d058da@bsd64.grem.de> <dd7b8b0d-05dd-e69d-ae1e-c6887a556009@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 7 Mar 2020, at 12:23, Adam Jimerson <vendion@gmail.com> wrote: >=20 >=20 > On 3/7/20 6:56 AM, Michael Gmelin wrote: >>=20 >> I worked around the situation locally by setting ALTABI >> on `pkg update': >>=20 >> # ALTABI=3DFreeBSD:12.0:amd64 pkg update -f >>=20 >> This allowed me to run >>=20 >> # pkg upgrade >>=20 >> without any issues, so I assume none of the about 30 packages I = updated >> contained a wrong ABI/architecture. >>=20 >> I verified this by checking: >>=20 >> # pkg query "%q" | sort | uniq -c >> 112 FreeBSD:12:* >> 219 FreeBSD:12:amd64 >>=20 >> Note that you could also export ALTABI to the environment or set it >> in /usr/local/etc/pkg.conf, but I figured that I might forget it in >> there. >>=20 >> Also, it seems like none of my packages were affected and not setting >> it on `pkg upgrade' meant that pkg checks for that (at least that's >> what I assume it does) and therefore I won't have to deal with >> different ABIs in my installed packages later. >>=20 >> All of this should be really temporary anyway and hopefully be = resolved >> soon. >>=20 >> Cheers, >> Michael >>=20 >=20 > I'm not screaming either, figured it wouldn't really help speed up > fixing things and that the right people were already working on fixing > it. I am also still getting this on 12.1-RELEASE, but the ALTABI work > around worked for me. >=20 I also figured it will get fixed eventually, and it was my decision to = switch=20 from the default quarterly repo to the latest repo, so have to expect = some=20 problems from time to time. It would be nice to have some sort of indicator as to the progress the=20= process though, it was a little confusing to see the package build = server for 121amd64 had finished a day or two before the repo actually got = updated, I guess it either has to wait for all builds to be finished and sync = with mirrors?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B598FDC5-CCEA-4FD2-A4E0-A8A75D1FAF07>