Date: Thu, 6 Jul 2017 16:57:59 -0400 From: Stephen Black <sjblack.00.01@gmail.com> To: Baho Utot <baho-utot@columbus.rr.com> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD did it again (still) Message-ID: <CAJybOa7akBPY1E1He7QNmiyNxCYTqEckWDQPkOe4FW-vaXFe8Q@mail.gmail.com> In-Reply-To: <9c9b2c25-e65d-3489-e483-d99c2e746e56@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> <e2cab146-89c9-23b0-e6ac-6222d8747277@columbus.rr.com> <8c1bb853-5eb0-4fae-ee26-5ff4684c2b3a@saunalahti.fi> <1499345128.3276.2.camel@gmail.com> <3cbeca30-8801-d800-edcb-f64ea2f079e0@columbus.rr.com> <alpine.BSF.2.21.1707060743420.80012@wonkity.com> <9c9b2c25-e65d-3489-e483-d99c2e746e56@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 6, 2017 at 10:09 AM, Baho Utot <baho-utot@columbus.rr.com> wrote:
>
>
> 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.
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
I'm not familiar with the "synth" program that you're using, but it
appears you are using it to build a local repository, so I guess I
would start there. It looks like a newer project, there is a GIT page
started in January 2016. As I had said, wasn't trying to be an ass,
was just giving my opinion on trying to upgrade source packages on
that big of a leap between versions of FreeBSD. Yes, the base system
should upgrade without issue, but to expect the same from all ports, I
think is asking a lot. I know how to build software as well, and also
have built and used linux from scratch. But that doesn't really mean
anything other than we can both follow written instructions. If I were
to attempt something like this, I would completely wipe out everything
under /usr/local (of course you may want to back up /usr/local/etc)
and reinstall all packages. That way you are ensured there are no old
libraries laying around being linked to accidentally.
--
Stephen Black
sjblack.00.01@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJybOa7akBPY1E1He7QNmiyNxCYTqEckWDQPkOe4FW-vaXFe8Q>