From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 339F0158083 for ; Mon, 2 Sep 2024 09:17:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 86A03E29EC; Mon, 2 Sep 2024 09:17:44 +0000 (UTC) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 22B00E29AD for ; Mon, 2 Sep 2024 09:17:44 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1sl3Bs-0007Nn-Ei for gentoo-user@lists.gentoo.org; Mon, 02 Sep 2024 11:17:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Nuno Silva Subject: [gentoo-user] Re: emerge - Tips and Tricks Date: Mon, 02 Sep 2024 10:17:35 +0100 Message-ID: References: <9ce08b83-1bef-400c-b79a-e6415e4d9a17@gmail.com> <2340049.ElGaqSPkdT@rogueboard> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-Archives-Salt: d11f2aaf-7d66-4d9a-8fc5-f3ee3781da35 X-Archives-Hash: c1330d51e2caaffd6f66b875d25b0e4e On 2024-09-02, Michael wrote: > On Monday, 2 September 2024 07:59:20 BST Wols Lists wrote: >> On 02/09/2024 06:11, Dale wrote: >> > If you have a laptop where heat is a issue, you may want to do things >> > different but if you can, that will give you the most stable system for >> > updates. >> >> Another tip - if you run into any problems, try to emerge @system, not >> @world. >> >> If you know you've successfully emerged @system and you get loads of >> stuff blocking with an @world, I tend to just unmerge all the blockers >> until @world fires successfully. You need to be a bit careful, you could >> still unmerge something important, but it's unlikely. Although these >> problems also tend to be fixed by backtrack=100. >> >> Cheers, >> Wol > > You can remove blockers manually and I admit to do it occasionally, but it can > sometimes break your system if you don't pay particular attention and you > inadvertently remove some critical toolchain software - e.g. python, glibc, > gcc, et al. It is safer to run: > > emerge --depclean -v -p > > and check what dependencies of are complaining about your > attempt to remove it. Should you come across python or something portage > depends on, it's best to back off and ask before you decide how to proceed. > Soft blockers (b) are dealt with automatically by emerge, it is hard blockers > (B) you'd have to pay attention to. > > My typical update runs like this: > > eix-sync > emerge -uaNDv @world > dispatch-conf > emerge --depclean -a -v > eclean-dist > > If the emerge output asks me to, I also run: > > revdep-rebuild > > and when perl itself goes through a major update, I run: > > perl-cleaner --reallyall > > Enjoy your gentoo! Could --ignore-world be of use in cases where blockers are complicating things too much? Might make sense e.g. if an emerge upgrade is needed before other upgrades but python eclass changes are blocking things creating cyclic dependencies. (Requires a lot of careful analysis, of course...) -- Nuno Silva