From owner-freebsd-questions@freebsd.org Thu Jul 6 14:09:07 2017 Return-Path: Delivered-To: freebsd-questions@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 342DCDAED35 for ; Thu, 6 Jul 2017 14:09:07 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cdptpa-oedge", Issuer "cdptpa-oedge" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E9BE57147C for ; Thu, 6 Jul 2017 14:09:06 +0000 (UTC) (envelope-from baho-utot@columbus.rr.com) Received: from [65.186.81.207] ([65.186.81.207:51671] helo=raspberrypi.bildanet.com) by cdptpa-omsmta02 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id C4/E8-20123-1844E595; Thu, 06 Jul 2017 14:09:05 +0000 Received: from [192.168.1.143] (helo=desktop.example.com) by raspberrypi.bildanet.com with esmtp (Exim 4.84) (envelope-from ) id 1dT7Sq-0001uf-Sj; Thu, 06 Jul 2017 14:09:04 +0000 Subject: Re: FreeBSD did it again (still) To: Warren Block Cc: freebsd-questions@freebsd.org References: <27b3c757-1f00-a033-03f6-303a82ab65f2@columbus.rr.com> <3ce31ee2-5e35-d31c-71ca-dc95ece2dd61@intersonic.se> <020431a6-1a7d-d80e-0725-585c21f3ef27@columbus.rr.com> <563b14d5-ebfb-62b6-28ac-3ebbd663d067@intersonic.se> <8c1bb853-5eb0-4fae-ee26-5ff4684c2b3a@saunalahti.fi> <1499345128.3276.2.camel@gmail.com> <3cbeca30-8801-d800-edcb-f64ea2f079e0@columbus.rr.com> From: Baho Utot Message-ID: <7d594988-7432-6b2d-e932-30828d91d073@columbus.rr.com> Date: Thu, 6 Jul 2017 10:09:04 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.7:25 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jul 2017 14:09:07 -0000 On 07/06/17 09:46, Warren Block wrote: > On Thu, 6 Jul 2017, Baho Utot wrote: > >> Well FYI the upgrade base 10.1 to 11.0-p10 when as expected. Update >> the ports to the current quarterly was a tragic happening. I have >> done this before upgrade a desktop from 10.3 to 11.0-p0 then to >> 11.0-p9. Again the ports just did not work as it resulted in a broken >> desktop each time. I started using the quarterly ports branch >> thinking I get some stablilty. No stability to be found. Should I >> user be able to update without going thru a weeks worth of debugging? >> I think that is not too much to ask. > > It might or might not be obvious, but after going from FreeBSD 10 to 11 > all ports must be reinstalled. It is not possible to upgrade only some > ports without mysterious breakages. This was the process: 1. Checkout base 11.0 releng 2. Build and install 3. Reboot 4. checkout latest port quarterly branch 5. rsync --verbose --archive --recursive --delete ${source}/ /usr/ports/ 6. synth just-build ${home}/port.list 7. synth rebuild-repository 8. pkg update 9. pkg upgrade 10. fix/patch changes from UPDATING and the "spew" from pkg upgrade 11. reboot 12. login 13. startx ---> crash and burn Now what part of that is so broken to result in a useless/broken desktop system. I would expect that to result in a working desktop, at the least. Yes I understand if some app is broken that runs under lumina but I fully expect lumina to just run and not just crash.