public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to degrade Gentoo system with webrsync method?
Date: Sun, 9 Jan 2022 06:42:41 -0600	[thread overview]
Message-ID: <c4a1ddcf-2871-509b-94ee-85be5ac1f934@gmail.com> (raw)
In-Reply-To: <CA+t6X7dsRDPqCdf0YoF6oTLUvK9PAERo52-1G5DZuU=6E8NF5A@mail.gmail.com>

gevisz wrote:
> вс, 9 янв. 2022 г. в 14:08, Arve Barsnes <arve.barsnes@gmail.com>:
>> On Sun, 9 Jan 2022 at 12:48, gevisz <gevisz@gmail.com> 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 available.
>> 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 tree
>> 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 of
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 until
things got fixed.  I then removed the mask, while keeping the old ebuild
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 person
said, it's best to figure out why your package fails and fix that, then
you can worry about new problems.  ;-)  Masking the newer version may
work at least in the meantime tho.  Give you time to sort out the failure. 

Just a thought. 

Dale

:-)  :-) 


  reply	other threads:[~2022-01-09 12:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 11:47 [gentoo-user] How to degrade Gentoo system with webrsync method? gevisz
2022-01-09 12:07 ` Arve Barsnes
2022-01-09 12:16   ` gevisz
2022-01-09 12:42     ` Dale [this message]
2022-01-09 13:13       ` gevisz
2022-01-09 13:39         ` Dale
2022-01-09 14:15           ` gevisz
2022-01-09 14:46           ` Wol
2022-01-09 17:08             ` Neil Bothwick
2022-01-11  1:48         ` Daniel Frey
2022-01-19 12:51 ` Robert David

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c4a1ddcf-2871-509b-94ee-85be5ac1f934@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox