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