From owner-freebsd-ports@freebsd.org Sun Jan 7 20:36:33 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90DD0E5B8AC for ; Sun, 7 Jan 2018 20:36:33 +0000 (UTC) (envelope-from SRS0=I3Wg=EC=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 540BA77BA9 for ; Sun, 7 Jan 2018 20:36:32 +0000 (UTC) (envelope-from SRS0=I3Wg=EC=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 6E2272840C; Sun, 7 Jan 2018 21:36:29 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 622F728412; Sun, 7 Jan 2018 21:36:28 +0100 (CET) Subject: Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd To: Eugene Grosbein , Michael Grimm , freebsd-ports@freebsd.org References: <76627A89-D7E9-4010-910B-5F25886E7E7E@ellael.org> <5A523873.2050001@quip.cz> <5A524855.2040901@grosbein.net> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <5A5284CC.9050400@quip.cz> Date: Sun, 7 Jan 2018 21:36:28 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <5A524855.2040901@grosbein.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2018 20:36:33 -0000 Eugene Grosbein wrote on 2018/01/07 17:18: > 07.01.2018 22:10, Miroslav Lachman wrote: > >>> I am following 11-STABLE and therefore upgrading my system quite frequently. During that process I do recompile all ports installed by poudriere and upgrade all ports after reboot. >> There are no consensus about what services should do on deinstall or upgrade. That's why there is such a mess in ports / packages. >> Some did nothing (my preferred way), some stop (but did not start) the service, >> some modify user edited config files (removing / disabling modules in httpd.conf so Apache is broken on each upgrade of module(s)). > > There IS consensus on modifying config files while upgrade and it is written in our Porter's Handbook: > only unmodified files may be changes with upgrade. Any other behaviour is a bug that should be fixed. If it is that simple then tell me how it is possible that for many years there are repetitive discussions and many ports with many commits violating this "rule"? If it is written somewhere how any committer can allow ports with those problems? For example: "requesting policy for Apache module installation (LoadModule manipulation)" https://lists.freebsd.org/pipermail/freebsd-ports/2017-October/110725.html Miroslav Lachman