> It would be good to have Go 1.18 make release - if we're not able
> to do that, then we should update to 1.17.8.
Be very careful, the user testing time for such large software is becoming
exceedingly short, and quickly.
On 22-03-24 16:43:28, Christian Weisgerber wrote:
> It's time to start slowing down for the upcoming 7.1 release.
>
> There are no restrictions on the types of ports commits yet, but I
> would like to ask everybody to keep the approaching release in mind
> and to slowly wind down large ports
On Thu, Mar 24, 2022 at 04:43:28PM +0100, Christian Weisgerber wrote:
> It's time to start slowing down for the upcoming 7.1 release.
>
> There are no restrictions on the types of ports commits yet, but I
> would like to ask everybody to keep the approaching release in mind
> and to slowly wind
On Thu, Mar 24, 2022 at 04:43:28PM +0100, Christian Weisgerber wrote:
> It's time to start slowing down for the upcoming 7.1 release.
>
> There are no restrictions on the types of ports commits yet, but I
> would like to ask everybody to keep the approaching release in mind
> and to slowly wind
Christian Weisgerber wrote:
> We also need to finish the %n cleanup. It looks like Theo wants
> to ship 7.0 with %n triggering abort(3). Without testing, we will
> not find all application uses.
It can miss release if it needs to.
But I urge users to install new ports, and test, and not
On 2016/07/11 22:03, Rafael Sadowski wrote:
> Looks like mc works fine with _shadow (maybe without too).
The only time getpw*_shadow functions are needed are when the password
field (pw_passwd) are used. These don't need just a search-and-replace
for getpw*->getpw*_shadow, they need a small
On Mon Jul 11, 2016 at 11:40:56AM +0100, Stuart Henderson wrote:
> On 2016/07/06 21:41, Christian Weisgerber wrote:
> > The next release, 6.0, is approaching fast. It's time to wind down
> > the ports churn, focus on fixing problems and stop introducing them.
> >
> > Over the next few days,
On Mon, Jul 11, 2016 at 11:40:56AM +0100, Stuart Henderson wrote:
> On 2016/07/06 21:41, Christian Weisgerber wrote:
> > The next release, 6.0, is approaching fast. It's time to wind down
> > the ports churn, focus on fixing problems and stop introducing them.
> >
> > Over the next few days,
On Mon, Jul 11, 2016 at 12:40 PM, Stuart Henderson wrote:
> On 2016/07/06 21:41, Christian Weisgerber wrote:
>> The next release, 6.0, is approaching fast. It's time to wind down
>> the ports churn, focus on fixing problems and stop introducing them.
>>
>> Over the next few
> sysutils/openpoppassd
This one is done.
--
Antoine
> Am 11.07.2016 um 12:40 schrieb Stuart Henderson :
>
>> On 2016/07/06 21:41, Christian Weisgerber wrote:
>> The next release, 6.0, is approaching fast. It's time to wind down
>> the ports churn, focus on fixing problems and stop introducing them.
>>
>> Over the next few
On 2016/07/06 21:41, Christian Weisgerber wrote:
> The next release, 6.0, is approaching fast. It's time to wind down
> the ports churn, focus on fixing problems and stop introducing them.
>
> Over the next few days, please stop importing new ports and regular
> updates. If you're in the middle
Stuart Henderson writes:
> On 2016/07/07 18:43, Jeremie Courreges-Anglas wrote:
>> Theo de Raadt writes:
>>
>> >> I don't think that getpwnam_shadow is a big concern. Fixes can be
>> >> applied to -stable with relatively minor churn, if needed.
On 2016/07/07 18:43, Jeremie Courreges-Anglas wrote:
> Theo de Raadt writes:
>
> >> I don't think that getpwnam_shadow is a big concern. Fixes can be
> >> applied to -stable with relatively minor churn, if needed.
> >
> > They are being discovered slower than I
> I don't think that getpwnam_shadow is a big concern. Fixes can be
> applied to -stable with relatively minor churn, if needed.
They are being discovered slower than I expected. Maybe there are only
a handful left.
> I don't think that 6.0 can ship with wxneeded enforced. There's just
> too
Christian Weisgerber writes:
> The next release, 6.0, is approaching fast. It's time to wind down
> the ports churn, focus on fixing problems and stop introducing them.
fwiw I have a security update coming for samba.
> Over the next few days, please stop importing new
16 matches
Mail list logo