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 60921158086 for ; Sun, 9 Jan 2022 14:46:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2FE6D2BC088; Sun, 9 Jan 2022 14:46:24 +0000 (UTC) Received: from smtp.hosts.co.uk (smtp.hosts.co.uk [85.233.160.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4CE6E2BC018 for ; Sun, 9 Jan 2022 14:46:18 +0000 (UTC) Received: from host81-132-12-162.range81-132.btcentralplus.com ([81.132.12.162] helo=[192.168.1.65]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1n6ZSa-000CSX-BZ for gentoo-user@lists.gentoo.org; Sun, 09 Jan 2022 14:46:16 +0000 Message-ID: Date: Sun, 9 Jan 2022 14:46:17 +0000 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 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.4.1 Subject: Re: [gentoo-user] How to degrade Gentoo system with webrsync method? Content-Language: en-GB To: gentoo-user@lists.gentoo.org References: <0520fc39-506a-340e-092c-05e671366862@gmail.com> From: Wol In-Reply-To: <0520fc39-506a-340e-092c-05e671366862@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: d07d9de1-17b6-42fc-ae30-b4e91ecd9b8d X-Archives-Hash: 98098d4086341c0b484c70ec693e70d1 On 09/01/2022 13:39, Dale wrote: > As a starting point, check the ebuild and see what all packages are > listed there that it depends on.  Put the needed entries in package.mask > and then use your world upgrade command plus -p to see what emerge wants > to upgrade.  Keep adding until it is reporting nothing to upgrade.  The > packages in the ebuild should help save some time.  I can't think of a > easier way to do it.  Someone else may have ideas tho.  Oh, don't forget > the ">=" signs and to specify versions.  Can't recall if it matters > which symbol comes first. Or do you want to use package.accept_keywords I had a package that was in testing, so I've ended up creating a file in there called - I think the package was avidemux so that's what it's called ... But in there it has the line(s) =package.version ~amd64 I've deliberately used the "=" so for it, and every package it depends on, that version will be accepted. Aiui, if the stable version goes above that it will then upgrade to the stable version, so that my system will be pretty much just stable packages. I also made the mistake of doing ACCEPT_KEYWORDS="~amd64" emerge blah blah ... which upgraded glibc! So now I need to configure this to keep the current version of glibc and wait till the stable version goes past. Cheers, Wol