El mié, 03-11-2021 a las 21:15 -0500, John Helmert III escribió:
> On Thu, Nov 04, 2021 at 12:09:28AM +, Sam James wrote:
> > On 4 Nov 2021, at 00:02, Sam James wrote:
> > > > On 3 Nov 2021, at 23:53, Aaron Bauman wrote:
> > > > Is that where the policy belongs?
> > > > If so, shouldn't the c
On Thu, Nov 04, 2021 at 12:09:28AM +, Sam James wrote:
> On 4 Nov 2021, at 00:02, Sam James wrote:
> >> On 3 Nov 2021, at 23:53, Aaron Bauman wrote:
> >> Is that where the policy belongs?
> >> If so, shouldn't the council update it based on their decisions?
> >> "patches are welcome" doesn't
On 4 Nov 2021, at 00:02, Sam James wrote:
>> On 3 Nov 2021, at 23:53, Aaron Bauman wrote:
>> Is that where the policy belongs?
>> If so, shouldn't the council update it based on their decisions?
>> "patches are welcome" doesn't fit every scenario.
> Got to agree here. If there's a gap in the docu
> On 3 Nov 2021, at 23:53, Aaron Bauman wrote:
> Is that where the policy belongs?
> If so, shouldn't the council update it based on their decisions?
> "patches are welcome" doesn't fit every scenario.
Got to agree here. If there's a gap in the documentation,
let's file a bug -- irrespective of
On Wed, Nov 03, 2021 at 10:32:34PM +0100, Ulrich Mueller wrote:
> > On Wed, 03 Nov 2021, Aaron Bauman wrote:
>
> > I love digging through old council logs to find "policy"
>
> > Not sure why others don't feel the same way.
>
> Patches for the devmanual are welcome.
Is that where the policy
> On 3 Nov 2021, at 20:16, Rich Freeman wrote:
> It probably would be good to get these policies documented someplace
> OTHER than the council decision logs. I do remember the discussion
> from the distant past but it is worth having it in a more prominent
> place, especially since a one year st
> On 3 Nov 2021, at 22:15, Joshua Kinard wrote:
> Actually, it is possible to manage dependency errors like those. It just
> takes a *lot* of elbow grease, and and long, long time time. Especially if
> you have museum-grade hardware that these errors are happening on.
>
> For Perl, I've usuall
> On 3 Nov 2021, at 15:03, Thomas Deutschmann wrote:
>
> Hi,
>
> it is currently not possible to smoothly run a world upgrade on a 4 months
> old system which doesn't even have a complicated package list:
> [snip]
>
> This is not about finding solution to upgrade the system (in this case it was
On Wed, Nov 3, 2021 at 2:50 PM Andreas K. Huettel wrote:
>
> Am Mittwoch, 3. November 2021, 22:39:41 CET schrieb Ulrich Mueller:
> > > On Wed, 03 Nov 2021, Andreas K Huettel wrote:
> >
> > > The mistake was to allow the use of EAPI=8 too early. In the future,
> > > we should have a new EAPI su
Am Mittwoch, 3. November 2021, 22:39:41 CET schrieb Ulrich Mueller:
> > On Wed, 03 Nov 2021, Andreas K Huettel wrote:
>
> > The mistake was to allow the use of EAPI=8 too early. In the future,
> > we should have a new EAPI supported by portage for at least some
> > months before the EAPI is ev
> On Wed, 03 Nov 2021, Andreas K Huettel wrote:
> The mistake was to allow the use of EAPI=8 too early. In the future,
> we should have a new EAPI supported by portage for at least some
> months before the EAPI is even used in the main tree. Not even
> speaking about stable here.
I tend to di
> On Wed, 03 Nov 2021, Aaron Bauman wrote:
> I love digging through old council logs to find "policy"
> Not sure why others don't feel the same way.
Patches for the devmanual are welcome.
signature.asc
Description: PGP signature
On Wed, Nov 3, 2021 at 1:14 PM Ulrich Mueller wrote:
>
> > On Wed, 03 Nov 2021, John Helmert wrote:
>
> >> | https://projects.gentoo.org/council/meeting-logs/20091109-summary.txt
> >> |
> >> | Upgrade path for old systems
> >> |
> >> | Vote (unanimous): The ebuild
Am Mittwoch, 3. November 2021, 16:03:37 CET schrieb Thomas Deutschmann:
> Hi,
>
> it is currently not possible to smoothly run a world upgrade on a 4
> months old system which doesn't even have a complicated package list:
>
[snip]
Yup. We know. It's actually way worse than you describe [*] and
211103 John Helmert III wrote:
> An "upgrade path" to me sounds like not just a world update,
> but also includes other stuff
> that might be necessary to get a system fully updated,
> like temporarily setting PYTHON_TARGETS to upgrade a package.
> A system without an upgrade path would seem to be
On Wed, Nov 03, 2021 at 05:34:16PM +0100, Ulrich Mueller wrote:
> > On Wed, 03 Nov 2021, Rich Freeman wrote:
>
> > On Wed, Nov 3, 2021 at 11:03 AM Thomas Deutschmann
> > wrote:
> >>
> >> This is not about finding solution to upgrade the system (in this case
> >> it was enough to force PYTHO
> On Wed, 03 Nov 2021, John Helmert wrote:
>> | https://projects.gentoo.org/council/meeting-logs/20091109-summary.txt
>> |
>> | Upgrade path for old systems
>> |
>> | Vote (unanimous): The ebuild tree must provide an upgrade path to a
>> | stable system that hasn't
On Wed, Nov 03, 2021 at 05:51:49PM +0100, Thomas Deutschmann wrote:
> On 2021-11-03 17:44, John Helmert III wrote:
> >> | Upgrade path for old systems
> >> |
> >> | Vote (unanimous): The ebuild tree must provide an upgrade path to a
> >> | stable system that hasn't been
On 2021-11-03 17:44, John Helmert III wrote:
| Upgrade path for old systems
|
| Vote (unanimous): The ebuild tree must provide an upgrade path to a
| stable system that hasn't been updated for one year.
Does "upgrade path" imply a simple world upgrade is all that sho
On Wed, Nov 03, 2021 at 05:34:16PM +0100, Ulrich Mueller wrote:
> > On Wed, 03 Nov 2021, Rich Freeman wrote:
>
> > On Wed, Nov 3, 2021 at 11:03 AM Thomas Deutschmann
> > wrote:
> >>
> >> This is not about finding solution to upgrade the system (in this case
> >> it was enough to force PYTHO
> On Wed, 03 Nov 2021, Rich Freeman wrote:
> On Wed, Nov 3, 2021 at 11:03 AM Thomas Deutschmann wrote:
>>
>> This is not about finding solution to upgrade the system (in this case
>> it was enough to force PYTHON_TARGETS=python3_8 for portage). This is
>> about raising awareness that Gentoo
On Wed, Nov 3, 2021 at 11:03 AM Thomas Deutschmann wrote:
>
> This is not about finding solution to upgrade the system (in this case
> it was enough to force PYTHON_TARGETS=python3_8 for portage). This is
> about raising awareness that Gentoo is a rolling distribution and that
> we guarantee users
Hi,
it is currently not possible to smoothly run a world upgrade on a 4
months old system which doesn't even have a complicated package list:
# cat /var/lib/portage/world
app-admin/eclean-kernel
app-admin/logrotate
app-admin/rsyslog
app-editors/nano
app-misc/ca-certificates
app-misc/colordiff
23 matches
Mail list logo
