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 98589158086 for ; Sun, 9 Jan 2022 14:16:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8CE1F2BC088; Sun, 9 Jan 2022 14:15:47 +0000 (UTC) Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (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 D0AAE2BC07B for ; Sun, 9 Jan 2022 14:15:38 +0000 (UTC) Received: by mail-pj1-x102c.google.com with SMTP id i8-20020a17090a138800b001b3936fb375so3903375pja.1 for ; Sun, 09 Jan 2022 06:15:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=tUI74w0ItHjE1qH/IyW7pQrOexSgrD1aymBiMyIFG6Q=; b=P7ErKC+3ISXzQ6FHxVXfFCyP4eLf1+71MtjizV+dS6X6r+3Y7VtyKhzlZ4GEeww+eu WdVv0BkZIhsAFBWycAA8m1K3PS+XxJo6IPq0cUSQgnIkCJrk6RXBHVujZLbLHO2C5W9B uAGTwa4vj9838jABWnIR4zDODcayQ4KUeFkS78wfl56gHbT5tmhawDWsG2jsL5SMXUk5 89aWfT5wUuC3vfNrq13ERU2/CIkAjG7C0cqSh0rtPu2zd1tvdaTx0I8u4n6AiZqVoroT 6gxqJ9uVhd/1A+cQlJpK6rZ4xte5D+ONWj1uaNXCuhCnyi3PxWeHvJduojiNBcj4mj/7 iMPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=tUI74w0ItHjE1qH/IyW7pQrOexSgrD1aymBiMyIFG6Q=; b=nsGLn7ywoiMyEq5NhGaXu5TTmAuPe4PEpoQDEQxSUZfzkUhVYO5oUNMGHbcW7C62+f 5XBRgZ5gJj0GrRr891vysg6znKgv9ZBwo4vNesv+oiVcRC4eK8VWBv9pJV62ggK8Tf8s ElkX+DtrsFH+xUF/Tg6+sxbIzGB7zAW2FjU8PK6duP2W8L0ROXRtcpap4oN/bCJIuA/a DYyon7DC97sMXURJ1ll9sWxdMkhO7CDGauwipMxySr4VfufKtnUjCFDoSQMl5Cs16JmL R1TEVqS1cqDCLvdSwSkGMatmgydSbuWFPQOqMeDt4zP6Hm0vKyoDGJSIeeL4/aLPcN69 N0rg== X-Gm-Message-State: AOAM530x1Aak7AGufxYAedxdOmD68F3SEibDGzeh5djM5j6AAIrmcFYK RPByJC6DGx8H0Sif+cnFi9xPOndfkPzmGEgZuToGp8Al X-Google-Smtp-Source: ABdhPJxTT6BEVizIMq5NEkBV3J+tG3UW1T7nBwuCk5RQQUYi67FOndeL80oBmQecInYEZkPhwgJhh3jk4X7jp+X8TRI= X-Received: by 2002:a17:90a:cc0d:: with SMTP id b13mr2057522pju.236.1641737737501; Sun, 09 Jan 2022 06:15:37 -0800 (PST) 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 References: <0520fc39-506a-340e-092c-05e671366862@gmail.com> In-Reply-To: <0520fc39-506a-340e-092c-05e671366862@gmail.com> From: gevisz Date: Sun, 9 Jan 2022 16:15:03 +0200 Message-ID: Subject: Re: [gentoo-user] How to degrade Gentoo system with webrsync method? To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 956a2336-6eeb-44c0-a1e6-381c37c9c912 X-Archives-Hash: 5d997343649844048835487d4cdd6005 =D0=B2=D1=81, 9 =D1=8F=D0=BD=D0=B2. 2022 =D0=B3. =D0=B2 15:40, Dale : > > gevisz wrote: > > =D0=B2=D1=81, 9 =D1=8F=D0=BD=D0=B2. 2022 =D0=B3. =D0=B2 14:43, Dale : > >> gevisz wrote: > >>> =D0=B2=D1=81, 9 =D1=8F=D0=BD=D0=B2. 2022 =D0=B3. =D0=B2 14:08, Arve B= arsnes : > >>>> On Sun, 9 Jan 2022 at 12:48, gevisz wrote: > >>>>> The problem is that I do not know how to sync my Gentoo repository > >>>>> to the state it was on 12-12-2021. > >>>>> > >>>>> I use webrsync sync method via "emaint -A sync" and would prefer > >>>>> to use the same sync method for degrading my Gentoo system. > >>>>> > >>>>> Can anybody, please, tell me how to do it using this sync method? > >>>> This is probably not possible at all using any of the tools availabl= e. > >>>> These tools only support downloading the latest snapshot to get you = up > >>>> to date. Additionally, most mirrors only keep snapshots of the last = 7 > >>>> days or so, so it would take some (possibly futile) effort to find a > >>>> snapshot of the date you need. > >>>> > >>>> The only option, as far as I can see, is to migrate your portage tre= e > >>>> to git, where you can specify a commit that you want to sync to from > >>>> the wanted day. > >>> It is a pity, but thank you for the answer. > >> I'm not sure if I'm understanding completely the problem here but > >> thought I'd suggest something. Can you not just mask newer versions o= f > >> the package so emerge won't update it until you are ready? I do that > >> sometimes here. I've did it with smplayer at one point because some > >> changes broke things for me. I kept it from upgrading for months unti= l > >> things got fixed. I then removed the mask, while keeping the old ebui= ld > >> and even a binary of the package, and allowed emerge to upgrade > >> smplayer. At that point, things worked for me that didn't before. > >> > >> The only downside to this, things your package depends on may go past > >> what your package supports and you run into issues. As the other pers= on > >> said, it's best to figure out why your package fails and fix that, the= n > >> you can worry about new problems. ;-) Masking the newer version may > >> work at least in the meantime though. Give you time to sort out the f= ailure. > > Thank you for your reply, Dale. > > > > Yes, masking some new package can work in this case. > > > > However, it is not so easy as it may seem because it is not the new > > version of tensorflow that I should mask in my case as on the day > > when the tensorflow recompilation failed its version remained the same > > and only some of its dependencies were supposed to be upgraded. > > > > Of course, I may try this approach. However, tensorflow is not > > considered stable in gentoo tree and it has a lot of dependencies > > that are also not considered stable and should be unmasked. > > > > All this leads to a large number of possible choices on > > which packages to mask/unmask. > > > > So, playing with this is like playing in a casino with about > > 4 hours of compilation for each bet. > > 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 an > easier way to do it. Someone else may have ideas thogh. Oh, don't forge= t > the ">=3D" signs and to specify versions. Can't recall if it matters > which symbol comes first. Thank you. I probably should also look into the emerge logs to see which of the tensorflow dependencies was updated the last time, when its recompilation failed.