>> 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 ETR. Maybe even with suggestions for
> workaroun
On 07/03/2020 22:38, Greg 'groggy' Lehey wrote:
>> This was only an issue on the "latest" branch. If you don't alter
>> "/etc/pkg/FreeBSD.conf", you'll get packages from the "quarterly"
>> branch, which fortunately wasn't affected.
> No, this isn't necessarily correct. I have never modified this
> On 7. Mar 2020, at 22:12, Andrey Fesenko wrote:
>
> On Sun, Mar 8, 2020 at 12:02 AM Michael Tuexen wrote:
>>
>>
>>
>>> On 7. Mar 2020, at 21:37, Michael Gmelin wrote:
>>>
>>>
>>>
On 7. Mar 2020, at 19:01, Michael Tuexen wrote:
>
>> On 7. Mar 2020, at 18:18,
> 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
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 experien
On Sun, Mar 8, 2020 at 12:02 AM Michael Tuexen wrote:
>
>
>
> > On 7. Mar 2020, at 21:37, Michael Gmelin wrote:
> >
> >
> >
> >> On 7. Mar 2020, at 19:01, Michael Tuexen wrote:
> >>
> >>
> >>>
> On 7. Mar 2020, at 18:18, Michael Gmelin wrote:
>
>
>
> > On 7. Mar 2020,
> On 7. Mar 2020, at 21:37, Michael Gmelin wrote:
>
>
>
>> On 7. Mar 2020, at 19:01, Michael Tuexen wrote:
>>
>>
>>>
On 7. Mar 2020, at 18:18, Michael Gmelin wrote:
> On 7. Mar 2020, at 18:08, Michael Tuexen wrote:
>
> On 7. Mar 2020, at
> On 7. Mar 2020, at 19:01, Michael Tuexen wrote:
>
>
>>
>>> On 7. Mar 2020, at 18:18, Michael Gmelin wrote:
>>>
>>>
>>>
On 7. Mar 2020, at 18:08, Michael Tuexen wrote:
>>>
>>>
On 7. Mar 2020, at 16:46, Michael Gmelin wrote:
> On Sat, 07 Mar 202
> On 7. Mar 2020, at 18:18, Michael Gmelin wrote:
>
>
>
>> On 7. Mar 2020, at 18:08, Michael Tuexen wrote:
>>
>>
>>>
>>> On 7. Mar 2020, at 16:46, Michael Gmelin wrote:
>>>
>>>
>>>
On Sat, 07 Mar 2020 11:30:58 -0400
Waitman Gobble wrote:
On 2020-03-07 05:10, Ronal
> On 7. Mar 2020, at 18:08, Michael Tuexen wrote:
>
>
>>
>> On 7. Mar 2020, at 16:46, Michael Gmelin wrote:
>>
>>
>>
>>> 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' L
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 +1100
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 +1100, Greg 'groggy' Lehey wrote:
Any workarounds in the meantime? This must affect a lot
On 3/7/2020 05:56, Michael Gmelin wrote:
>
> 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
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 w
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 ETR.
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 12-
>>> 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
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
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
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
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
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
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 pk
On 3/03/2020 4:58 am, 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 pkg update -f
Updating FreeBSD reposito
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 pkg update -f
> Updating FreeBSD repository catalogue...
> Fetching
Apparently something has its ABI erroneously listed as
FreeBSD:13.0:amd64 instead of FreeBSD:13:amd64.
```
$ sudo pkg update -f
Updating FreeBSD repository catalogue...
Fetching meta.conf: 100%163 B 0.2kB/s00:01
Fetching packagesite.txz: 100%6 MiB 6.4MB/s00:01
Processing entr
26 matches
Mail list logo
