Deutsch English Français Italiano |
<l5gveoF5essU1@mid.individual.net> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: groenveld@acm.org (John D Groenveld) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Still No X (Re: Catastrophe Re: Proliferating LLVMs) Date: 14 Mar 2024 18:54:16 GMT Organization: Groenveld.US Lines: 11 Message-ID: <l5gveoF5essU1@mid.individual.net> References: <uqod44$bag$2@reader1.panix.com> <ust7p4$pia$1@reader1.panix.com> <usv10o$1sh$1@reader1.panix.com> <usvdns$1oga4$1@dont-email.me> X-Trace: individual.net dg9cqwNO/2YFmngyXgPpog9LyVVHjNNlzhAqwICoDbXf1gLuc3 Cancel-Lock: sha1:Q1xGY4PdMP/QOfuu5UGinkxZy1o= sha256:wlRkXsd9kH0mTGS13E8ndr8GfU55ssYMZf1OqJ9yzAc= Bytes: 1103 In article <usvdns$1oga4$1@dont-email.me>, Steven G. Kargl <sgk@REMOVEtroutmask.apl.washington.edu> wrote: >If I get in your situtation, I typically rebuild everything >from source. So, first created a backup, then do Forcibly reinstalling the packages might re-add whatever dependency the OP broke by deleting LLVMs. # pkg upgrade -f John groenveld@acm.org