On Thu, Feb 4, 2021 at 1:53 PM antlists <[email protected]> wrote: > > On 31/01/2021 19:20, Rich Freeman wrote: > > On Sat, Jan 30, 2021 at 11:01 PM Kusoneko <[email protected]> wrote: > >> > >> It states that starting the next xorg-server version, ... > >> > >> ... Doing the required update is currently impossible. > >> > >> I am definitely not gonna remember about this > >> in a week or 2 so I'd like to deal with whatever > >> this issue is asap. Is there any way to do this? > > > > You hit on the issue. You can either wait and not have to mess with > > much, or you can force things using keywords as Jacques suggested, and > > then if you want to go back to stable do more work later to transition > > back. > > > Is there a way to say "install this version from ~ if it's more recent > than stable"? That way, as stable catches up and overtakes ~, it reverts > back to stable without any further intervention?
When I'm in this sort of situation I tend to stick range atoms in package.accept_keywords. For example, if foo-1.2.3 is stable, and foo-1.3.1 is unstable and I need it for a while, I'll stick this in package.accept_keywords: <foo-1.4 That lets me get updates to the foo-1.3.x branch from unstable but will keep me from advancing to 1.4 until it is stable. Of course you need to look at the package versioning scheme and be somewhat familiar with how it is being maintained to do this. You don't want to lock yourself into something obsolete and miss critical fixes. I only do this selectively in any case so there is usually a good reason when I do. You can't just do this sort of thing blindly. -- Rich
