Date: Sat, 22 Dec 2018 04:40:06 -0800 From: Mel Pilgrim <list_freebsd@bluerosetech.com> To: Kurt Jaeger <pi@freebsd.org> Cc: ports-secteam@freebsd.org, "Timur I. Bakeyev" <timur@freebsd.org>, FreeBSD Ports ML <freebsd-ports@freebsd.org>, portmgr@freebsd.org Subject: Re: Bug 233749 - net/samba47, net/samba48: Merge ports r486043 to 2018Q4 (Fixes several vulnerabilities) Message-ID: <4f1cc9fa-af6a-215e-2654-1d94127fa57a@bluerosetech.com> In-Reply-To: <20181222120252.GD84895@home.opsec.eu> References: <1b5e5e0a-f492-5ec0-a70c-dc34d1d26c01@bluerosetech.com> <e915ef82-02ce-0579-2649-5e16f6f34635@bluerosetech.com> <20181222120252.GD84895@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-12-22 4:02, Kurt Jaeger wrote: > Hi! > >> On 2018-12-12 19:19, Mel Pilgrim wrote: >>> Would someone work on ports/233749, please? The original security fix >>> was committed to head 15 days ago, but has yet to be merged to quarterly. >> >> I realize it's the holidays, but this is a security fix for a major port. >> Or is it the plan to let this go unfixed in 2018Q4? > > Hoping about a plan is unfortunatly expecting a bit too much right now, > with all the updates, holidays etc going on. I guess it's not easy to estimate > if the MFH would fit right in. > > After checking the commits to samba47, I guess something like this might work: > > /usr/ports/Tools/scripts/mfh 2018Q4 486043 I don't have a commit bit. Instead I create local copies of specific ports as a poor pleb's MFH (e.g., 2018Q4/local/net_samba48 copied from head/net/samba48). The ability to switch pkg origins makes it fairly painless for most ports.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4f1cc9fa-af6a-215e-2654-1d94127fa57a>