Pkg repository is broken...

Michael Gmelin freebsd at grem.de
Sat Mar 7 23:12:18 UTC 2020



> On 8. Mar 2020, at 00:04, Greg 'groggy' Lehey <grog at freebsd.org> 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' Lehey <grog at freebsd.org> wrote:
>>>>> ???On Saturday,  7 March 2020 at 16:46:58 +0100, Michael Gmelin 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 file,
>>>>> but I ended up with a copy of /usr/src/usr.bin/pkg/FreeBSD.conf.latest
>>>>> with this revision string:
>>>>> # $FreeBSD: stable/11/etc/pkg/FreeBSD.conf 263937 2014-03-30 15:24:17Z bdrewery $
>>>>> Despite the age, this appears to identical to the current version,
>>>>> according to svn blame.  Arguably this should be the default anyway.
>> Installing 12.1 from install media gives you quarterly.
> 
> Yes, quite possibly.  But as I said, it's not always the case.

In the part you trimmed he wrote:

>>>>>> I installed 12.1 on a new laptop yesterday, I have not experienced
>>>>>> issues with pkg.

my comment

>>>>> 
>>>>> 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.
>>>>> 

was a direct response to that (fresh install of a 12.1 system). This obviously doesn’t necessarily apply to systems that have been updated from previous releases.

-m






More information about the freebsd-ports mailing list