two crashes

[Matthias]

Thanks Matt for your explanation.

This also means that this ABI pkg problem always occurrs during release time for a short time period for RC versions and the master branch?

Regards
Matthias

Matthew Dillon <dillon at backplane.com> schrieb:

>The ABI for package purposes can be a little confusing during release time.  The release is 4.0 but the current 'master' (now 'after' the release) is 4.1.  For ABI purposes we round up to the nearest even number so the current 4.1 master will look for '4.2' packages.  6 months from now the current master will, in fact, become 4.2.  It's easier to manage the binary repo and the mirrors and allows us to do continuous package builds without having to juggle too many different names.  Each binary package set is ~60GB or so.
>
>Maybe I over-engineered it :-)
>
>
>-Matt
>
>
>On Fri, Nov 7, 2014 at 12:23 PM, Matthias <matthias_play at gmx.net> wrote:
>
>Thanks, that will also fix my Problem reported here:
>
>http://bugs.dragonflybsd.org/issues/2730#change-12268
>
>Regards
>Matthias
>
>John Marino <dragonflybsd at marino.st> schrieb:
>
>
>>On 11/7/2014 20:36, Pierre Abbat wrote:
>>> On Friday, November 07, 2014 11:27:26 Zachary Crownover wrote:
>>>> From my experience, the odd numbers are the current/testing versions, so
>>>> with 4.0RC being RELEASE, I'd say 4.1.
>>>
>>> Where do I change it? It's inside a variable called ABI.
>>>
>>> Pierre
>>>
>>
>>echo 'ABI = "dragonfly:4.0:x86:64";' > /usr/local/etc/pkg.conf
>>
>>or wait until Sunday when 4.2 packages are uploaded.
>>
>>
>>and "master" is supposed to report 4.2 by default.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20141107/de7a916a/attachment-0003.htm>