| 1 |
On 06/06/19 06:00, n952162@×××.de wrote: |
| 2 |
|
| 3 |
> The handbook is great information, but unfortunately, it uses concepts - specific gentoo concepts - that many readers doesn't know. They are then often cross-referenced to other pages, which likewise define things based on expected internal understanding of the mechanisms, goals, and potential scenarios. |
| 4 |
> |
| 5 |
> I have "read" the handbook - multiple times. But not really understood what it was saying - and I have decades of development experience. |
| 6 |
> |
| 7 |
> Consider slots. I'm sure I've read that slots are used to allow multiple ... versions? configurations? of the same package to be installed. It was gradually dawning on me, that it's the developer who specifies the slot. Now, I can't figure out what use case that benefits, but the ability to have slots react to realities at a particular installation see to me to make a lot of sense. So, there must be something basic that I don't understand. |
| 8 |
> |
| 9 |
> I think cases like my simple case would help new comers and I'm hoping to make a blog describing it, once I fully understand the implications. |
| 10 |
> |
| 11 |
> |
| 12 |
|
| 13 |
In trying to update portage (before I update my system), I have this: |
| 14 |
|
| 15 |
/!!! All ebuilds that could satisfy |
| 16 |
">=dev-python/setuptools-34[python_targets_pypy(-)?,pn_targets_python3_6(-)?,python_targets_python3_7(-)?,-python_single_target_pypy(-),-pyth-),-python_single_target_python3_6(-),-python_single_target_python3_7(-)]" |
| 17 |
have been mas// |
| 18 |
//!!! One of the following masked packages is required to complete |
| 19 |
your request:// |
| 20 |
//- dev-python/setuptools-9999::gentoo (masked by: EAPI 7)// |
| 21 |
//- dev-python/setuptools-41.0.1::gentoo (masked by: EAPI 7)// |
| 22 |
//- dev-python/setuptools-41.0.0::gentoo (masked by: EAPI 7)// |
| 23 |
//- dev-python/setuptools-40.9.0::gentoo (masked by: EAPI 7)// |
| 24 |
//- dev-python/setuptools-40.8.0::gentoo (masked by: EAPI 7)// |
| 25 |
//- dev-python/setuptools-40.7.3::gentoo (masked by: EAPI 7)// |
| 26 |
//- dev-python/setuptools-40.6.3::gentoo (masked by: backtracking: |
| 27 |
slot conflict)// |
| 28 |
//- dev-python/setuptools-36.7.2::gentoo (masked by: backtracking: |
| 29 |
slot conflict)/ |
| 30 |
|
| 31 |
|
| 32 |
|
| 33 |
Looking at https://packages.gentoo.org/packages/dev-python/setuptools |
| 34 |
shows that the only two versions stable for am64 are 40.6.3 and 36.7.2. |
| 35 |
|
| 36 |
What is *backtracking* and how can I have a *slot conflict *if it's the |
| 37 |
developers who determine what version sits in a slot? |
| 38 |
|
| 39 |
One might say, I have a package already dependent on /setuptools/ and |
| 40 |
it's not the right one, but how can it be that two different versions |
| 41 |
want to go into the same slot? |
| 42 |
|
| 43 |
Backtracking is something to do with dependency checking. I haven't |
| 44 |
seen any explanation of what goes on in dependency checking and why |
| 45 |
backtracking is necessary. Can someone point to an explanation? |
| 46 |
|
| 47 |
My emerge output goes on to say: |
| 48 |
|
| 49 |
/The current version of portage supports EAPI '6'. You must upgrade |
| 50 |
to a// |
| 51 |
//newer version of portage before EAPI masked packages can be |
| 52 |
installed.// |
| 53 |
//(dependency required by "app-portage/gemato-9999::gentoo" [ebuild])// |
| 54 |
//(dependency required by |
| 55 |
"sys-apps/portage-2.3.66-r1::gentoo[-build,rsync-verify]" [ebuil// |
| 56 |
//(dependency required by "portage" [argument])// |
| 57 |
//For more information, see the MASKED PACKAGES section in the emerge// |
| 58 |
//man page or refer to the Gentoo Handbook.// |
| 59 |
/ |
| 60 |
|
| 61 |
|
| 62 |
Is this telling me that I have to *first* update my system and *then* |
| 63 |
update portage? |
Archives