| 1 |
On 8/3/21 7:20 AM, n952162 wrote: |
| 2 |
> On 8/2/21 10:10 PM, David Haller wrote: |
| 3 |
>> Hello, |
| 4 |
>> |
| 5 |
>> On Mon, 02 Aug 2021, n952162 wrote: |
| 6 |
>>> !!! All ebuilds that could satisfy |
| 7 |
>>> "dev-python/isodate[python_targets_python3_8(-)?,python_targets_python3_9(-)?]" |
| 8 |
>>> have been masked. |
| 9 |
>>> !!! One of the following masked packages is required to complete your |
| 10 |
>>> request: |
| 11 |
>>> - dev-python/isodate-0.6.0-r2::gentoo (masked by: EAPI 8) |
| 12 |
>>> |
| 13 |
>>> The current version of portage supports EAPI '7'. You must upgrade to a |
| 14 |
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^ |
| 15 |
>>> newer version of portage before EAPI masked packages can be installed. |
| 16 |
>> You should read a bit more carefully... It seems your sys-apps/portage |
| 17 |
>> is a bit dated. |
| 18 |
>> |
| 19 |
>> Upgrade sys-apps/portage first, then it should work. |
| 20 |
>> |
| 21 |
>> HTH, |
| 22 |
>> -dnh |
| 23 |
> |
| 24 |
> |
| 25 |
> I read that, but I last updated 2 months ago. So, this update breaks |
| 26 |
> because portage was updated and new ebuilds using that are already |
| 27 |
> being pushed out? Seems strict to me ... but /isodate/ being the only |
| 28 |
> one? I still have a EAPI 4 on my system (1). Plenty of EAPI 5. Was |
| 29 |
> there something in isodate that needed to be urgently updated - |
| 30 |
> utilizing the the cutting edge EAPI? |
| 31 |
> |
| 32 |
|
| 33 |
We just had to update portage not so long ago. I admittedly presumed at |
| 34 |
first that something else must be wrong, because it didn't occur to me |
| 35 |
that portage would be so volatile. |
| 36 |
|
| 37 |
Everything in gentoo is so nicely configurable, but I think another |
| 38 |
dimension should be add: configurable volatility - i.e. a configurable |
| 39 |
hysteresis for upstream updates. |
Archives