Re: Pkg repository is broken...

2020-03-07 Thread Michael Gmelin
> On 8. Mar 2020, at 00:04, Greg 'groggy' Lehey wrote: > > On Saturday, 7 March 2020 at 23:55:33 +0100, Michael Gmelin wrote: > > [More irrelevant text deleted, also dropping current@] > > Is it really so difficult to trim your replies? > >> On 7. Mar 2020, at 23:39, Greg 'groggy'

Re: Pkg repository is broken...

2020-03-07 Thread Greg 'groggy' Lehey
On Saturday, 7 March 2020 at 23:55:33 +0100, Michael Gmelin wrote: [More irrelevant text deleted, also dropping current@] Is it really so difficult to trim your replies? >> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey wrote: >> >> ???On Saturday, 7 March 2020 at 16:46:58 +0100, Michael

Re: Pkg repository is broken...

2020-03-07 Thread Michael Gmelin
> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey wrote: > > On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote: > > [much irrelevant text deleted] > > People, please trim your replies. Only relevant text should remain > >>> On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble

Re: Pkg repository is broken...

2020-03-07 Thread Greg 'groggy' Lehey
On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote: [much irrelevant text deleted] People, please trim your replies. Only relevant text should remain > On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble wrote: >> >> I installed 12.1 on a new laptop yesterday, I have not

Re: Pkg repository is broken...

2020-03-07 Thread James Wright
> On 7 Mar 2020, at 12:23, Adam Jimerson wrote: > > > On 3/7/20 6:56 AM, Michael Gmelin wrote: >> >> I worked around the situation locally by setting ALTABI >> on `pkg update': >> >> # ALTABI=FreeBSD:12.0:amd64 pkg update -f >> >> This allowed me to run >> >> # pkg upgrade >> >>

Re: Pkg repository is broken...

2020-03-07 Thread Michael Gmelin
On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble wrote: > On 2020-03-07 05:10, Ronald Klop wrote: > > On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey > > wrote: > > > >> On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: > >>> On Wed, Mar 04, 2020 at 03:16:14PM

Re: Pkg repository is broken...

2020-03-07 Thread Adam Jimerson
On 3/7/20 6:56 AM, Michael Gmelin wrote: > > I worked around the situation locally by setting ALTABI > on `pkg update': > > # ALTABI=FreeBSD: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 >

Re: Pkg repository is broken...

2020-03-07 Thread Michael Gmelin
On Sat, 07 Mar 2020 10:10:43 +0100 "Ronald Klop" wrote: > On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey > wrote: > > > 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

Re: Pkg repository is broken...

2020-03-07 Thread Stefan Bethke
Am 07.03.2020 um 08:50 schrieb sth...@nethelp.no: > > I think a lot of people are waiting for some kind of guidance on how > to fix these problems, if the repos are supposed to be okay now. It would be really great if someone in the know would send something to -announce or similar, with an

Re: Pkg repository is broken...

2020-03-07 Thread Thierry Thomas
Le sam. 7 mars 20 à 1:38:55 +0100, Greg 'groggy' Lehey écrivait : > > Still broken for me on 12.1. Still broken for me on 12.1-STABLE, but with a different error: "size mismatch, fetching from remote" and then "size mismatch, cannot continue" for the first package being fetched. Same after

Re: Pkg repository is broken...

2020-03-07 Thread Ronald Klop
On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey wrote: 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

Re: Pkg repository is broken...

2020-03-06 Thread Janky Jay, III
On 3/6/20 7:41 PM, Marcin Cieslak wrote: > On Sat, 7 Mar 2020, Janky Jay, III wrote: > >> Still broken for me as well. I just figured I'd look into it when I >> got a chance. Also using FBSD 12.1 RELEASE. > > Maybe it depends on the mirror being used? Perhaps. I'm not really sure what's going

Re: Pkg repository is broken...

2020-03-06 Thread Marcin Cieslak
On Sat, 7 Mar 2020, Janky Jay, III wrote: Still broken for me as well. I just figured I'd look into it when I got a chance. Also using FBSD 12.1 RELEASE. Maybe it depends on the mirror being used? smime.p7s Description: S/MIME Cryptographic Signature

Re: Pkg repository is broken...

2020-03-06 Thread Janky Jay, III
Still broken for me as well. I just figured I'd look into it when I got a chance. Also using FBSD 12.1 RELEASE. Regards, Janky Jay, III On March 7, 2020 12:38:55 AM UTC, Greg 'groggy' Lehey wrote: >On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote: >> On Wed, Mar 04, 2020 at

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-curr...@freebsd.org; freebsd-ports@freebsd.org Subject: Re: Pkg repository is broken... On Friday,  6 March 2020

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

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

Re: Pkg repository is broken...

2020-03-03 Thread Greg 'groggy' Lehey
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 as FreeBSD:13.0:amd64 >> instead of FreeBSD:13:amd64. >> >> ``` >> $ sudo