Date: Sat, 7 Mar 2020 07:23:32 -0500 From: Adam Jimerson <vendion@gmail.com> To: freebsd-ports@freebsd.org Subject: Re: Pkg repository is broken... Message-ID: <dd7b8b0d-05dd-e69d-ae1e-c6887a556009@gmail.com> In-Reply-To: <20200307125658.56d058da@bsd64.grem.de> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --wSRI5afE93J9jw64b2MLDBODNachUPQKX Content-Type: multipart/mixed; boundary="UHe7itDog9zZDpzdnCNJCSfXScmXhITWH" --UHe7itDog9zZDpzdnCNJCSfXScmXhITWH Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 3/7/20 6:56 AM, Michael Gmelin wrote: > > I worked around the situation locally by setting ALTABI > on `pkg update': > > # ALTABI=3DFreeBSD:12.0:amd64 pkg update -f > > This allowed me to run > > # pkg upgrade > > without any issues, so I assume none of the about 30 packages I updated= > contained a wrong ABI/architecture. > > I verified this by checking: > > # pkg query "%q" | sort | uniq -c > 112 FreeBSD:12:* > 219 FreeBSD:12:amd64 > > 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. > > 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. > > All of this should be really temporary anyway and hopefully be resolved= > soon. > > Cheers, > Michael > 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. --UHe7itDog9zZDpzdnCNJCSfXScmXhITWH-- --wSRI5afE93J9jw64b2MLDBODNachUPQKX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEELLlB4D3dJQL6YIqWtmZSyNpTGkkFAl5jklcACgkQtmZSyNpT GkneNggA1jDrXjsRTGthYmiQTeNJUdSE0bBHxfGsE5Ep+7YWZ3O5BtGC8OO06M6V /8fDQGNV9hIOwrXG1hY/WrGTV4EHyMHDgqLMx48aFXW8y6r3GTAo7rWyj5b9Dltx Mkmg0u1MQ6p0AK0rarGlhBPCiOGSeTUoJhbPTEv11pwEOaZ98Gh4HPFvDBGsmlEX V2ckcmTxTOKb9BnrXXxcikX2PaSIcg7EaNMo0p5dX7XfaygQofs1V+3w5lj1/4jy dy/NIbGduk2qw1+7/9CU0W8sC1tDaPlJI2rJ54XFPjZj/O+ZgZJ0CCCvBOMAYQb4 Htpx8vx1xhL15Js+gVYQVPsuSh5hNg== =M5t2 -----END PGP SIGNATURE----- --wSRI5afE93J9jw64b2MLDBODNachUPQKX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?dd7b8b0d-05dd-e69d-ae1e-c6887a556009>