Thanks for the work you put in this major feature.
Could we please get a full list of the issues which surfaced, quirks,
and other worth to mention notes ? I believe its important.
> On 19 May 2016, at 23:31, Glen Barber wrote:
>
> Despite the schedule adjustment for 11.0-RELEASE to allow ad
On Thu, May 19, 2016 at 1:31 PM, Glen Barber wrote:
> Dear FreeBSD community:
...
> Thank you to everyone who supported this effort, and we hope you will
> continue to support and test the forward development of packaging the
> base system with pkg(8).
Thank you too both bapt and gjb. This is a
> On 19 May 2016, at 23:29, jungle Boogie wrote:
>
>> On 19 May 2016 at 13:31, Glen Barber wrote:
>> Given the state of this highly-disruptive change to the base system, we
>> need to take the best interest of the FreeBSD community into primary
>> consideration, as a whole.
>>
>> We have arri
On 19 May 2016 at 13:31, Glen Barber wrote:
> Given the state of this highly-disruptive change to the base system, we
> need to take the best interest of the FreeBSD community into primary
> consideration, as a whole.
>
> We have arrived at the difficult decision to treat packaged base as
> a "bet
Glen,
I realize that you have put an enormous amount of effort into
getting the packaging of base with pkg(8) into the 11.0 release
and am sorry to hear that it needs to be delayed. But having
watched the mailing lists during these efforts I realize that
it is a much more difficult problem than it
Dear FreeBSD community:
Early this year, it was announced [1] that FreeBSD 11.0-RELEASE would
ship not only with the ability to package the base system with pkg(8),
but the intent to use pkg(8) as the primary binary upgrade mechanism for
the base system.
Despite the schedule adjustment for 11.0-R
On Thu, 19 May 2016 14:04:59 +0300
Andriy Gapon wrote:
> On 19/05/2016 13:50, Boris Samorodov wrote:
> > 19.05.16 09:28, K. Macy пишет:
> >> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just
> >> did an IFC to r300176 and boot will hang right ater printing out
> >> "setting ho
19.05.16 16:43, Andriy Gapon пишет:
> On 19/05/2016 16:40, Boris Samorodov wrote:
>> 19.05.16 14:04, Andriy Gapon пишет:
>>> On 19/05/2016 13:50, Boris Samorodov wrote:
19.05.16 09:28, K. Macy пишет:
> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just
> did an IFC to
On 19/05/2016 16:40, Boris Samorodov wrote:
> 19.05.16 14:04, Andriy Gapon пишет:
>> On 19/05/2016 13:50, Boris Samorodov wrote:
>>> 19.05.16 09:28, K. Macy пишет:
I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just
did an IFC to r300176 and boot will hang right ater print
19.05.16 14:04, Andriy Gapon пишет:
> On 19/05/2016 13:50, Boris Samorodov wrote:
>> 19.05.16 09:28, K. Macy пишет:
>>> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just
>>> did an IFC to r300176 and boot will hang right ater printing out
>>> "setting hostid: ". ^T just shows sh [
19.05.16 14:05, Konstantin Belousov пишет:
> On Thu, May 19, 2016 at 01:50:47PM +0300, Boris Samorodov wrote:
>> 19.05.16 09:28, K. Macy пишет:
>>> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just
>>> did an IFC to r300176 and boot will hang right ater printing out
>>> "setting h
On 19/05/2016 13:50, Boris Samorodov wrote:
> 19.05.16 09:28, K. Macy пишет:
>> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just
>> did an IFC to r300176 and boot will hang right ater printing out
>> "setting hostid: ". ^T just shows sh [piperd]. ddb just shows the
>> shell as ha
On Thu, May 19, 2016 at 01:50:47PM +0300, Boris Samorodov wrote:
> 19.05.16 09:28, K. Macy пишет:
> > I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just
> > did an IFC to r300176 and boot will hang right ater printing out
> > "setting hostid: ". ^T just shows sh [piperd]. ddb just
19.05.16 09:28, K. Macy пишет:
> I did an IFC on my drm-next-4.6 branch yesterday at r300069. I just
> did an IFC to r300176 and boot will hang right ater printing out
> "setting hostid: ". ^T just shows sh [piperd]. ddb just shows the
> shell as hanging in piperead. Diffing between those two revis
On 18 May, Conrad Meyer wrote:
> On Wed, May 18, 2016 at 5:19 PM, Don Lewis wrote:
>>
>> It looks to me like r299512 is changing the format of the client
>> identifier by inserting the struct hardware hlen field into it.
>
> Yes. The problem with r299512 is that it assumed the client_id was
> ac
On 18 May, Ian FREISLICH wrote:
> On 05/18/16 20:19, Don Lewis wrote
>> It looks to me like r299512 is changing the format of the client
>> identifier by inserting the struct hardware hlen field into it. That's
>> not valid if htype is non-zero the way I interpret RFC 2132. On the
>> other hand,
16 matches
Mail list logo
