On 8/3/21 8:29 AM, cal wrote:
On 8/2/21 11:03 PM, n952162 wrote:
On 8/3/21 7:37 AM, cal wrote:
On 8/2/21 10:26 PM, n952162 wrote:
On 8/3/21 7:20 AM, n952162 wrote:
On 8/2/21 10:10 PM, David Haller wrote:
Hello,
On Mon, 02 Aug 2021, n952162 wrote:
!!! All ebuilds that could satisfy
"dev-python/isodate[python_targets_python3_8(-)?,python_targets_python3_9(-)?]"
have been masked.
!!! One of the following masked packages is required to complete your
request:
- dev-python/isodate-0.6.0-r2::gentoo (masked by: EAPI 8)
The current version of portage supports EAPI '7'. You must upgrade
to a
^^^^^^^^^^^^^^^^^^^^^^^^^^
newer version of portage before EAPI masked packages can be
installed.
You should read a bit more carefully... It seems your sys-apps/portage
is a bit dated.
Upgrade sys-apps/portage first, then it should work.
HTH,
-dnh
I read that, but I last updated 2 months ago. So, this update breaks
because portage was updated and new ebuilds using that are already
being pushed out? Seems strict to me ... but /isodate/ being the only
one? I still have a EAPI 4 on my system (1). Plenty of EAPI 5. Was
there something in isodate that needed to be urgently updated -
utilizing the the cutting edge EAPI?
We just had to update portage not so long ago. I admittedly presumed at
first that something else must be wrong, because it didn't occur to me
that portage would be so volatile.
Everything in gentoo is so nicely configurable, but I think another
dimension should be add: configurable volatility - i.e. a configurable
hysteresis for upstream updates.
It sounds like you would be more satisfied with a distribution that has
releases. You are fighting a losing battle to use a rolling-release
distribution on a machine you intend to update infrequently.
Keeping old software working in a rolling release ecosystem is a pain,
doubly so if you have to maintain the newer version in parallel. What
you ask for is more difficult than you think.
Well, what you say is likely true, but does "old software" really need
to be kept working? Couldn't problems necessarily only be dealt with
in the newest versions?
Old software does not exist in a vacuum. Old software has old
dependencies; those dependencies get updated in ways that are
incompatible, or stop working, or a new version of Python is released
with which the old version of the software is incompatible; etc. Or as
you've noticed with Portage, the old version of the software may not
work compatibly with newer packages, so now you have to maintain older
versions of those packages as well...
Intuitively, i.e. from vague experience, I know you're right, but I
can't think it through ... a release would be a snapshot of a working
configuration at a point in time.
Ah, perhaps the problem is ... in my case, I could make a distribution
out of what I emerge every month and distibute that - an intermediate
level of hysteresis. But that's just the system as I require it. A
Ubuntu makes all those decisions for all supported packages, an effort
that doesn't interest me...
