Date: Mon, 26 Jan 2015 21:25:14 +0100 From: Marko =?UTF-8?B?Q3VwYcSH?= <marko.cupac@mimar.rs> To: freebsd-ports@freebsd.org Subject: Re: www/squid does not shutdown via rc Message-ID: <20150126212514.56c8f0866f1d63bb98089dd0@mimar.rs> In-Reply-To: <54C6695E.6010704@freebsd.org> References: <20150126152433.52f07277f377f9396b65c9a8@mimar.rs> <20150127.002919.335530336.yasu@utahime.org> <20150126163934.32f199d43d86a70b00dd7e4a@mimar.rs> <20150127.010539.230444205.yasu@utahime.org> <54C6695E.6010704@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 26 Jan 2015 16:20:46 +0000 Matthew Seaman <matthew@freebsd.org> wrote: > >> > Also, is there a chance they will be pushed to freebsd-update? >=20 > No. Unless these are either security fixes or fixes for a major > regression (which this is not) in 10.1-RELEASE, then they won't be > applied to that branch. >From OS point of view, this could be indeed seen as minor regression. But please consider server admin's point of view: - squid33 had latest release on 2014-08-27 - squid33 has been scheduled for expiration on 2015-01-31, but was extended to 2015-05-31 because of ntlm_auth issue in squid34 - squid34 does not run on 10.1-RELEASE-pX - 10.2-RELEASE is not likely to be before 2015-05-31 Which means that pkg installs of latest squid (www/squid34) will be useless on latest FreeBSD release (10.1-RELEASE) for a long time. > They will, however, be in the next release cut from stable/10, which > will be 10.2-RELEASE, and presumably in releases from other branches > from now on. >=20 > Your best recourse at the moment is to manually patch the kernel source= s > and build yourself a custom kernel on the affected machines. I was looking forward to avoid it. Perhaps I'm succumbing to conformism. --=20 Marko Cupa=C4=87 https://www.mimar.rs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150126212514.56c8f0866f1d63bb98089dd0>