svn commit: r504590 - in head/net: samba46 samba47 samba48

[Niclas Zeising]

On 2019-07-02 14:28, Tijl Coosemans wrote:
> On Tue, 2 Jul 2019 13:16:47 +0200 Mathieu Arnold <mat at FreeBSD.org> wrote:
>> On Tue, Jul 02, 2019 at 12:31:35PM +0200, Torsten Zuehlsdorff wrote:
>>> On 02.07.19 12:23, Mathieu Arnold wrote:
>>>> On Mon, Jul 01, 2019 at 01:23:34AM +0200, Timur I. Bakeyev wrote:
>>>>> On Sat, 29 Jun 2019 at 22:50, Baptiste Daroussin <bapt at freebsd.org> wrote:
>>>>>> Le 29 juin 2019 20:40:53 GMT+02:00, "Timur I. Bakeyev" <timur at bat.ru> a
>>>>>> écrit :
>>>>>>> Tonight I hope to commit 4.10 port.
>>>>>>
>>>>>> It does not solve rhe pb, staying on the legacy libs is the solution, as I
>>>>>> said even fedora is on the legacy
>>>>>>
>>>>> I've committed net/samba410.
>>>>>
>>>>> My view on the situation is that all the ports, which use
>>>>> devel/{talloc,tevent}, databases/tdb should keep
>>>>> using them, unless they are broken by using them(but that shouldn't happen,
>>>>> API still should remain
>>>>> the same. The biggest difference is the drop of the dependency on Python27,
>>>>> as far as I can see.
>>>>
>>>> So, branching 2019Q2 is now a day late.
>>>> When are you going to fix the issue?
>>>
>>> Mat, is this the reason the branch is late? If so: have you considered
>>> branching from r504589?
>>
>> It is being considered, yes, as a last resort kind of thing. timur@ has
>> had 13 days to fix the problem, I hope he is getting close to fixing it
>> all.
> 
> It's probably time to introduce some sort of a soft freeze where no
> major changes are allowed (unless approved by portmgr) in the last two
> weeks or so of the quarter.  It's not just samba, x11@ moving the mesa
> ports to llvm80 on the last day of the quarter is also way too close.
> 

the mesa llvm80 one was asked for by portmgr.
Regards
-- 
Niclas Zeising