From owner-freebsd-ports@freebsd.org Wed Dec 6 23:40:35 2017 Return-Path: <owner-freebsd-ports@freebsd.org> 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 641CBE90679 for <freebsd-ports@mailman.ysv.freebsd.org>; Wed, 6 Dec 2017 23:40:35 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (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 50AF468852 for <freebsd-ports@freebsd.org>; Wed, 6 Dec 2017 23:40:35 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (unknown [IPv6:2601:1c2:1402:1770:21c:c0ff:fe7f:96ee]) by echo.brtsvcs.net (Postfix) with ESMTPS id 86A1438D1B; Wed, 6 Dec 2017 15:40:29 -0800 (PST) Received: from [IPv6:fe80::dd2a:ba9e:2d4a:7c5f] (unknown [IPv6:fe80::dd2a:ba9e:2d4a:7c5f]) by chombo.houseloki.net (Postfix) with ESMTPSA id 1944AFD6; Wed, 6 Dec 2017 15:40:29 -0800 (PST) Subject: Re: Flavors *COMPLETELY* break the port system (synth and poudriere are useless) To: Baho Utot <baho-utot@columbus.rr.com>, freebsd-ports@freebsd.org References: <CAGBxaXmwzXqZXSKX4-_qe15L3Xa8bVx+sFnFrxoksY8Ka3gS3w@mail.gmail.com> <7a9a2753-6460-a2bf-5156-5eab92a0b2f8@FreeBSD.org> <0a06d3dd-10a7-fd87-9348-f520f3dfc175@columbus.rr.com> From: Mel Pilgrim <list_freebsd@bluerosetech.com> Message-ID: <830acccf-08e6-0bd2-d5a6-db267fc53fc5@bluerosetech.com> Date: Wed, 6 Dec 2017 15:40:27 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <0a06d3dd-10a7-fd87-9348-f520f3dfc175@columbus.rr.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/> List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 06 Dec 2017 23:40:35 -0000 On 12/5/2017 2:25 PM, Baho Utot wrote: > Thank you for taking a perfectly good system and breaking it as well as > making it unusable, unstable. You just don't know of all the countless > hours spent after running an update and taking a week to get it working > again. I manage (currently) 104 FreeBSD systems that are a mix of 10.x and 11.x, on-metal and VM. I use freebsd-update and poudriere. The biggest issue in two years was back before I used poudriere and it was when the default version postgresql change I had to upgrade databases (something for which postgresql doesn't have automated tools). The last time I had a major stability problem with FreeBSD was when I had a brand new Nocona Xeon system that would get interrupt storms running 5.x and had to run 6-CURRENT on it for a while because 6.x introduced MSI support. The closest thing to a FreeBSD failure after that was Perl upgrades exploding all over the place because there was a time when the Ports Tree didn't handle Perl upgrades gracefully. Looking back at two years of stats, all of the unplanned uptime resets are associated with hypervisor or power outages. Experiences will vary, and it's totally fine if FreeBSD is not your cup of tea, but you're out of line condemning the project as a whole because your individual experience differed. > It really helps motivate all of us users to continue to have to fix > broken systems due to broken ports system and then be told how great > things are, brings us so much joy and keeps our attitude positive. I really don't know what advice to offer you other than that, from my observations, there is a very high correlation between people who have chronic stability problems with FreeBSD and people who insist on not using the officially endorsed tools and methods. (Cue people utterly failing to understand statistics and citing single data points in 3, 2, 1...)