From owner-freebsd-ports@FreeBSD.ORG Mon Jan 26 20:25:21 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3BF87A2C for ; Mon, 26 Jan 2015 20:25:21 +0000 (UTC) Received: from mail.mimar.rs (mail.mimar.rs [193.53.106.129]) by mx1.freebsd.org (Postfix) with ESMTP id D86DF8D3 for ; Mon, 26 Jan 2015 20:25:20 +0000 (UTC) Received: from mail.mimar.rs (localhost [127.0.0.1]) by mail.mimar.rs (Postfix) with ESMTP id 12C411AF3B8 for ; Mon, 26 Jan 2015 21:25:18 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mimar.rs; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:references:in-reply-to:message-id:subject:subject:from :from:date:date:received:received; s=mimar-0901; t=1422303914; x=1424118315; bh=ThSMfkZt0fBqYtoLzEYUd0sE5UT0WqfXVEcWM2o7PvU=; b= 0fLtPGPeZgOppxZvW0mgT3EIs3fiJGT2ctmzgaj9D1bv5lFh+z0woX4H7+bwE6bP O6+7cmIbO4ivWl+biqCgYtkJoHiNi1H+j20jTF/0XYMaqpFAXipKBldUmfcpJIpp lJpCCVDT2JpgNo8+ldZ/z3NiDkOV3e25wRDpZCFLAr4= X-Virus-Scanned: amavisd-new at mimar.rs Received: from mail.mimar.rs ([127.0.0.1]) by mail.mimar.rs (mail.mimar.rs [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Pszc2AKb8Ku0 for ; Mon, 26 Jan 2015 21:25:14 +0100 (CET) Received: from efreet (93-86-94-117.dynamic.isp.telekom.rs [93.86.94.117]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: marko.cupac@mimar.rs) by mail.mimar.rs (Postfix) with ESMTPSA id 9BEA21AF394 for ; Mon, 26 Jan 2015 21:25:14 +0100 (CET) Date: Mon, 26 Jan 2015 21:25:14 +0100 From: Marko =?UTF-8?B?Q3VwYcSH?= 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> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2015 20:25:21 -0000 On Mon, 26 Jan 2015 16:20:46 +0000 Matthew Seaman 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