OK, what python settings do we need? [SOLVED]

Message

Tony0945 · Post by **Tony0945** » Thu Jan 24, 2019 4:56 am

So sick of g.d. python -3 and "exactly one of python-single-targets"

Been wasting days afyer last sync on thos (previous was about two weeks before:

What are we supposed to have for PYTHON_TARGETS and PYTHON_SINGLE_TARGET ?

Not putting anything in make.conf isn't working. profile 17.0 (desktop)

Code: Select all

 emerge -auvND world --exclude meld --exclude glib-utils

These are the packages that would be merged, in order:

Calculating dependencies... done!

emerge: there are no ebuilds built with USE flags to satisfy ">=sys-libs/talloc-2.1.14[python?,
    python_targets_python2_7(-)?,-python_single_target_jython2_7(-),
    -python_single_target_pypy(-),-python_single_target_pypy3(-),
    -python_single_target_python3_4(-),-python_single_target_python3_5(-),
    -python_single_target_python3_6(-),-python_single_target_python3_7(-),
    python_single_target_python2_7(+),abi_x86_32(-)?,abi_x86_64(-)?,
    abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,
    abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]".
!!! One of the following packages is required to complete your request:
- net-fs/samba-4.9.4::gentoo (Change USE: -python_targets_python2_7, this change violates use flag constraints defined by net-fs/samba-4.9.4: 'addc? ( python gnutls json winbind ) addns? ( python ) ads? ( acl gnutls ldap winbind ) cluster? ( ads ) gpg? ( addc ) test? ( python ) at-most-one-of ( system-heimdal system-mitkrb5 ) python_targets_python2_7')

Wrapped a long line to make the forum layout behave. —[profile=215889]Chiitoo[/profile]

sao98021 · Post by **sao98021** » Thu Jan 24, 2019 5:07 am

im at no means an expert doing things the 'right way' when i was faced with that months back

but for me to make things budge when it was stuck on that i put PYTHON_SINGLE_TARGET="python3_6"

and PYTHON_TARGETS="python2_7 python3_6"

im guessing im an idiot for doing so or somehow wrong(or not and it's actually what your supposed to do.. dunno)... but works for me, honestly couldn't tell you a difference from prior (thats noticeable)

(also 17.0 desktop), been months n months now and all is (or seemingly) good

Post by **fedeliallalinea** » Thu Jan 24, 2019 6:03 am

As sao98021 tells the profile enable these

Code: Select all

PYTHON_TARGETS="python2_7 python3_6"
PYTHON_SINGLE_TARGET="python3_6"

You have set somethings in make.conf? You can post your emerge --info?

Ant P. · Post by **Ant P.** » Thu Jan 24, 2019 11:26 am

Samba is one of those stupid packages that have a singular PYTHON_TARGETS=python2_7 flag for the sole purpose of causing a blocking error and wasting your time if it's disabled.

Here's my list of similarly broken packages, maybe it'll save you some time:

Code: Select all

app-emulation/qemu PYTHON_TARGETS: python2_7
app-text/asciidoc PYTHON_TARGETS: python2_7 PYTHON_SINGLE_TARGET: python2_7
dev-java/javatoolkit PYTHON_TARGETS: python2_7
dev-util/scons PYTHON_TARGETS: python2_7
dev-util/systemtap PYTHON_TARGETS: python2_7
dev-vcs/mercurial PYTHON_TARGETS: python2_7
gnome-base/gconf PYTHON_TARGETS: python2_7
media-libs/aubio PYTHON_TARGETS: python2_7
net-proxy/http-replicator PYTHON_TARGETS: python2_7
sys-devel/clang PYTHON_TARGETS: python2_7

sao98021 · Post by **sao98021** » Thu Jan 24, 2019 12:05 pm

Ant P. wrote:Samba is one of those stupid packages that have a singular PYTHON_TARGETS=python2_7 flag for the sole purpose of causing a blocking error and wasting your time if it's disabled.

Here's my list of similarly broken packages, maybe it'll save you some time:
Code: Select all
app-emulation/qemu PYTHON_TARGETS: python2_7
app-text/asciidoc PYTHON_TARGETS: python2_7 PYTHON_SINGLE_TARGET: python2_7
dev-java/javatoolkit PYTHON_TARGETS: python2_7
dev-util/scons PYTHON_TARGETS: python2_7
dev-util/systemtap PYTHON_TARGETS: python2_7
dev-vcs/mercurial PYTHON_TARGETS: python2_7
gnome-base/gconf PYTHON_TARGETS: python2_7
media-libs/aubio PYTHON_TARGETS: python2_7
net-proxy/http-replicator PYTHON_TARGETS: python2_7
sys-devel/clang PYTHON_TARGETS: python2_7

qemu has both targets now

Post by **asturm** » Thu Jan 24, 2019 12:07 pm

You shouldn't need any manual setting actually. Defaults should work, as soon as you set your own python targets you will run into these issues with some packages only supporting particular versions.

Ant P. · Post by **Ant P.** » Thu Jan 24, 2019 12:15 pm

sao98021 wrote:qemu has both targets now

This is exactly the problem with ebuild authors doing this… turns out several of those have been fixed, but there's no way to find out and revert the setting except by manual auditing.

Tony0945 · Post by **Tony0945** » Thu Jan 24, 2019 1:52 pm

Thank you all. I don't have any targets set, relying on the profile.

Code: Select all

PYTHON_TARGETS="python2_7 python3_6"
PYTHON_SINGLE_TARGET="python3_6"

I'll try these, although "eselect python list" suggests that is how the profile is setting them. If that doesn't work, I'll try surgery on the samba ebuild.

In m y make.conf I have set use flags "-python" and "-perl" because of those update problems. Never have a gcc problem unless it's a C++ version change. Don't have to set "GCC_TARGETS" ad "GCC_SNGLE_TARGET" nor run "gcc-cleaner really all". A pox on people who change an existing interface and don't change the application name.

Tony0945 · Post by **Tony0945** » Thu Jan 24, 2019 3:25 pm

Yes, PYTHON_TARGETS was the problem. Both tevent and talloc no longer support python 2.7.
I had to mask the latest version of each. portage is now building 99 packages, mostly because of switching from python 3.6 to python 3.7

My daughter programs python. I hate it like poison.

EDIT:
To recap the answer to my original question:

Samba 4.5 (still in the tree) requires python 2.7
Samba depends of tevent and talloc
Latest tevent and talloc on ~amd no longer support python 2.7

Solution: mask the tips of tevent and talloc to emerge versions that do support 2.7

This did not show up on my server which is stable amd64. The workstations are ~amd

Eventually I will have to update samba which I have been avoiding because my existing configuration files are no longer valid on later samba's.
I suspect the changes in later samba's are to support windows 8/10, but the latest (and last!) windows anywhere on my network is Win 7.

Part of the ugliness is the incomprehensible and misleading error message that portage put out. If, like other packages, portage had said "conflict, samba-xxx requires python-2.7, talloc-2.15 requires python-3.7, the problem would be obvious. Instead portage barfs word salad about "only one of x y z" which is already satisfied.

sao98021 · Post by **sao98021** » Thu Jan 24, 2019 4:46 pm

id like some ranch and parmasean cheese with my salad.

this made me think of and laugh at this horrendously old oriellys java2/sdk 1.2-1.3 book ive had for 10 years someone gave me as a handmedown.. it was seriously outdated then...but now? i dont even know why i have it.. guess sentiment even though it would make me prone to error if i attempt to use nearly anything in it for reference.

i never fully understood why human readable languages opted to go for this infrastructure of release cycles and deps, i get it... but good god it gets messy

as a species are we truly that incapable as a collective force, id say no.. not as a species.. but as a society? ¯\_(ツ)_/¯

then again i suppose its human nature... i consider if i had 100 clones... just how long would they work for me before they had their own ideas, or ideas of mutiny.. especially considering how easy it would be to get by - by doing nothing, because of all your worker drones.

i dont remember how that relates to my orig statement, but it probably does make sense to someone

Anon-E-moose · Post by **Anon-E-moose** » Thu Jan 24, 2019 7:04 pm

Tony0945 wrote:Eventually I will have to update samba which I have been avoiding because my existing configuration files are no longer valid on later samba's.
I suspect the changes in later samba's are to support windows 8/10, but the latest (and last!) windows anywhere on my network is Win 7.

*chuckle* I've long capped samba at 3.6.25 (along with associated tevent and talloc) ... because it works for me, and I don't need or use the later improvements, like you the latest on my internal network is win7 and neither of the kids will be upgrading past that point. Just copy everything samba related to your local repository and mask the appropriate packages.

If I were an org using samba that might be a different story, but I'm a home user, network of a few machines, I control everything.

Tony0945 · Post by **Tony0945** » Thu Jan 24, 2019 10:28 pm

Anon-E-moose wrote:If I were an org using samba that might be a different story, but I'm a home user, network of a few machines, I control everything.

Me too! Although sometimes I think portage controls me. Will take your suggestion to heart. Already had current samba in overlay to cut out all reference to systemd.