Gentoo Archives: gentoo-dev

From: Aaron Bauman <bman@g.o>
To: gentoo-dev@l.g.o
Cc: Rich Freeman <rich0@g.o>
Subject: Re: [gentoo-dev] You currently cannot smoothly upgrade a 4 months old Gentoo system
Date: Wed, 03 Nov 2021 18:42:40
Message-Id: YYLYFonkz6OHGvX5@Aarons-MBP.localdomain
In Reply to: Re: [gentoo-dev] You currently cannot smoothly upgrade a 4 months old Gentoo system by Ulrich Mueller
1 On Wed, Nov 03, 2021 at 05:34:16PM +0100, Ulrich Mueller wrote:
2 > >>>>> On Wed, 03 Nov 2021, Rich Freeman wrote:
3 >
4 > > On Wed, Nov 3, 2021 at 11:03 AM Thomas Deutschmann <whissi@g.o> wrote:
5 > >>
6 > >> This is not about finding solution to upgrade the system (in this case
7 > >> it was enough to force PYTHON_TARGETS=python3_8 for portage). This is
8 > >> about raising awareness that Gentoo is a rolling distribution and that
9 > >> we guarantee users to be able to upgrade their system when they do world
10 > >> upgrades just once a year (remember: in my case the last world upgrade
11 > >> is just 4 months old!). If they cannot upgrade their system without
12 > >> manual intervention, we failed to do our job.
13 >
14 > > Do we have this "guarantee" documented somewhere? I thought I've
15 > > heard six months tossed around. You say one year. It seems
16 > > reasonable to have some sort of guideline like this and try to stick
17 > > with it, at least for @system.
18 >
19 > We do. Summary of 2009-11-09 Council meeting:
20 >
21
22 I love digging through old council logs to find "policy"
23
24 Not sure why others don't feel the same way.
25
26 > | https://projects.gentoo.org/council/meeting-logs/20091109-summary.txt
27 > |
28 > | Upgrade path for old systems
29 > | ----------------------------
30 > | Vote (unanimous): The ebuild tree must provide an upgrade path to a
31 > | stable system that hasn't been updated for one year.
32 > |
33 > | Action: leio will start a discussion on gentoo-dev on if and how to
34 > | support upgrading systems that are outdated more than a year.

Replies