Re: Pkg repository is broken...

2020-03-06 Thread sthaug
>>> Any workarounds in the meantime? This must affect a lot of people, >>> including those who use 12-: >>> >>> pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64 >>> pkg: repository FreeBSD contains packages with wrong ABI: >>> FreeBSD:12.0:amd64 >> >> Still broken for m

Re: Pkg repository is broken...

2020-03-06 Thread Theron
On 2020-03-06 20:02, Theron wrote: On 2020-03-06 19:42, k...@denninger.net wrote: Strange.  Mine cleared up automatically the following day. It's also strange how few replies I have received.  Two private messages (why?), yours, and that was it.  You'd think that people would be screaming. May

Re: Pkg repository is broken...

2020-03-06 Thread Theron
On 2020-03-06 19:42, k...@denninger.net wrote: Strange.  Mine cleared up automatically the following day. It's also strange how few replies I have received.  Two private messages (why?), yours, and that was it.  You'd think that people would be screaming. Maybe because not everyone knows this i

Re: Pkg repository is broken...

2020-03-06 Thread karl
Still effed here. -- Karl (on PDA)   Original Message   From: g...@freebsd.org Sent: March 6, 2020 18:38 To: lars.eng...@0x20.net; marco+freebsd-curr...@lordsith.net; freebsd-current@freebsd.org; freebsd-po...@freebsd.org Subject: Re: Pkg repository is broken... On Friday,  6 March 2020 a

Re: Pkg repository is broken...

2020-03-06 Thread Greg 'groggy' Lehey
On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: > On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote: >> >> Any workarounds in the meantime? This must affect a lot of people, >> including those who use 12-: >> >> pkg: wrong architecture: FreeBSD:12.0:amd64 instead

Re: Pkg repository is broken...

2020-03-06 Thread Lars Engels
On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote: > On Monday, 2 March 2020 at 17:58:01 +, marco wrote: > > On Sun, Mar 01, 2020 at 04:50:59PM -0500, you (Brennan Vincent) sent the > > following to [freebsd-current] : > >> Apparently something has its ABI erroneously listed