[gentoo-user] problem emerging new stable python

[gentoo-user] problem emerging new stable python

[allan gottlieb]

I have two systems that are close in both hardware and software.

Today I did eix-sync on each followed by
emerge --update --changed-use --with-bdeps=y @world 

On one system (dell 6430) I was presented with many packages to merge
   python-3.5.4 [ebuild NS]
   many to reinstall [ebuild R]

This was not surprising.

The other system (dell 7450) failed with the following

!!! Problem resolving dependencies for sys-process/systemd-cron from @selected
... done!

!!! The ebuild selected to satisfy "sys-process/systemd-cron" has unmet requirements.
- sys-process/systemd-cron-1.5.4::gentoo USE="-cron-boot -etc-crontab-systemd -minutely -setgid -test -yearly" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_4 python3_5 (-pypy3) (-python3_6)" PYTHON_TARGETS="python3_5 (-pypy3) -python3_4 (-python3_6)"

  The following REQUIRED_USE flag constraints are unsatisfied:
    exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_python3_4? ( python_targets_python3_4 )

  The above constraints are a subset of the following complete expression:
    exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_pypy3? ( python_targets_pypy3 ) python_single_target_python3_4? ( python_targets_python3_4 ) python_single_target_python3_5? ( python_targets_python3_5 ) python_single_target_python3_6? ( python_targets_python3_6 )

(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

Both 6430 and 7450 have the following content in
/etc/portage/package.use/systemd-cron

# systemd-cron needs PYTHON_SINGLE_TARGET = 3.x.
sys-process/systemd-cron python_single_target_python3_4

Those files are 2+ years old on each system

I have not let the 6430 proceed with the emerge update world.

Thanks in advance for any help.
allan

Re: [gentoo-user] problem emerging new stable python

[Alan McKinnon]

On 29/11/2017 21:48, allan gottlieb wrote:
> I have two systems that are close in both hardware and software.
> 
> Today I did eix-sync on each followed by
> emerge --update --changed-use --with-bdeps=y @world 
> 
> On one system (dell 6430) I was presented with many packages to merge
>    python-3.5.4 [ebuild NS]
>    many to reinstall [ebuild R]
> 
> This was not surprising.
> 
> The other system (dell 7450) failed with the following
> 
> !!! Problem resolving dependencies for sys-process/systemd-cron from @selected
> ... done!
> 
> !!! The ebuild selected to satisfy "sys-process/systemd-cron" has unmet requirements.
> - sys-process/systemd-cron-1.5.4::gentoo USE="-cron-boot -etc-crontab-systemd -minutely -setgid -test -yearly" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_4 python3_5 (-pypy3) (-python3_6)" PYTHON_TARGETS="python3_5 (-pypy3) -python3_4 (-python3_6)"
> 
>   The following REQUIRED_USE flag constraints are unsatisfied:
>     exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_python3_4? ( python_targets_python3_4 )
> 
>   The above constraints are a subset of the following complete expression:
>     exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_pypy3? ( python_targets_pypy3 ) python_single_target_python3_4? ( python_targets_python3_4 ) python_single_target_python3_5? ( python_targets_python3_5 ) python_single_target_python3_6? ( python_targets_python3_6 )
> 
> (dependency required by "@selected" [set])
> (dependency required by "@world" [argument])
> 
> Both 6430 and 7450 have the following content in
> /etc/portage/package.use/systemd-cron
> 
> # systemd-cron needs PYTHON_SINGLE_TARGET = 3.x.
> sys-process/systemd-cron python_single_target_python3_4
> 
> Those files are 2+ years old on each system
> 
> I have not let the 6430 proceed with the emerge update world.
> 
> Thanks in advance for any help.
> allan
> 

Your machines differ between PYTHON_TARGETS and PYTHON_SINGLE_TARGET,
either globally or for that one package. Compare:

emerge --info | grep PYTHON
list of installed pythons
eselect python list

The cause is likely in make.conf somewhere

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] problem emerging new stable python

[allan gottlieb]

On Wed, Nov 29 2017, Alan McKinnon wrote:

> On 29/11/2017 21:48, allan gottlieb wrote:
>> I have two systems that are close in both hardware and software.
>> 
>> Today I did eix-sync on each followed by
>> emerge --update --changed-use --with-bdeps=y @world 
>> 
>> On one system (dell 6430) I was presented with many packages to merge
>>    python-3.5.4 [ebuild NS]
>>    many to reinstall [ebuild R]
>> 
>> This was not surprising.
>> 
>> The other system (dell 7450) failed with the following
>> 
>> !!! Problem resolving dependencies for sys-process/systemd-cron from @selected
>> ... done!
>> 
>> !!! The ebuild selected to satisfy "sys-process/systemd-cron" has unmet requirements.
>> - sys-process/systemd-cron-1.5.4::gentoo USE="-cron-boot -etc-crontab-systemd -minutely -setgid -test -yearly" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_4 python3_5 (-pypy3) (-python3_6)" PYTHON_TARGETS="python3_5 (-pypy3) -python3_4 (-python3_6)"
>> 
>>   The following REQUIRED_USE flag constraints are unsatisfied:
>>     exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_python3_4? ( python_targets_python3_4 )
>> 
>>   The above constraints are a subset of the following complete expression:
>>     exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_pypy3? ( python_targets_pypy3 ) python_single_target_python3_4? ( python_targets_python3_4 ) python_single_target_python3_5? ( python_targets_python3_5 ) python_single_target_python3_6? ( python_targets_python3_6 )
>> 
>> (dependency required by "@selected" [set])
>> (dependency required by "@world" [argument])
>> 
>> Both 6430 and 7450 have the following content in
>> /etc/portage/package.use/systemd-cron
>> 
>> # systemd-cron needs PYTHON_SINGLE_TARGET = 3.x.
>> sys-process/systemd-cron python_single_target_python3_4
>> 
>> Those files are 2+ years old on each system
>> 
>> I have not let the 6430 proceed with the emerge update world.
>> 
>> Thanks in advance for any help.
>> allan
>> 
>
> Your machines differ between PYTHON_TARGETS and PYTHON_SINGLE_TARGET,
> either globally or for that one package. Compare:
>
> emerge --info | grep PYTHON
> list of installed pythons
> eselect python list
>
> The cause is likely in make.conf somewhere

Thanks for the help, but I still have the problem.

emerge --info showed the same for PYTHON_SINGLE_TARGET="python3_5" and
PYTHON_TARGETS="python2_7 python3_5"

eix -I python   shows 2.7.14 and 3.4.5  on both systems

grep -i python /etc/portage/make.conf
has no hits on either system

eselect python list showed the same two version (3.4 and 2.7)
but in *opposite* order.  I issued
  eselect python set 2
on the failing 7450 and now both report
Available Python interpreters, in order of preference:
  [1]   python3.4
  [2]   python2.7

I don't believe I need to "activate" this change, right?

However, after making the above change the 7450 still fails to emerge
update world saying

Calculating dependencies -

!!! Problem resolving dependencies for sys-process/systemd-cron from @selected
... done!

!!! The ebuild selected to satisfy "sys-process/systemd-cron" has unmet requirements.
- sys-process/systemd-cron-1.5.4::gentoo USE="-cron-boot -etc-crontab-systemd -minutely -setgid -test -yearly" ABI_X86="(64)" PYTHON_SINGLE_TARGET="python3_4 python3_5 (-pypy3) (-python3_6)" PYTHON_TARGETS="python3_5 (-pypy3) -python3_4 (-python3_6)"

  The following REQUIRED_USE flag constraints are unsatisfied:
    exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_python3_4? ( python_targets_python3_4 )

  The above constraints are a subset of the following complete expression:
    exactly-one-of ( python_single_target_pypy3 python_single_target_python3_4 python_single_target_python3_5 python_single_target_python3_6 ) python_single_target_pypy3? ( python_targets_pypy3 ) python_single_target_python3_4? ( python_targets_python3_4 ) python_single_target_python3_5? ( python_targets_python3_5 ) python_single_target_python3_6? ( python_targets_python3_6 )

(dependency required by "@selected" [set])
(dependency required by "@world" [argument])

Re: [gentoo-user] problem emerging new stable python

[Marc Joliet]

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

Am Mittwoch, 29. November 2017, 22:29:59 CET schrieb allan gottlieb:
> On Wed, Nov 29 2017, Alan McKinnon wrote:
[...]
> >> Both 6430 and 7450 have the following content in
> >> /etc/portage/package.use/systemd-cron
> >> 
> >> # systemd-cron needs PYTHON_SINGLE_TARGET = 3.x.
> >> sys-process/systemd-cron python_single_target_python3_4
[...]

Isn't this the problem?  PYTHON_TARGETS has switched to python3_5 but that's 
in conflict with the above (or should be, IIUC).  Remove that or change it to 
"python_single_target_python3_5" (I would remove it; according to my git log, 
I removed a similar line in August when I noticed that the profiles already 
default to Python 3.x in $PYTHON_SINGLE_TARGETS).

I admit, though, that I am surprised that one machine can apparently still go 
through with the upgrade.  Does it also have systemd-cron installed?  Or maybe 
I'm forgetting or missing something...

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] problem emerging new stable python

[allan gottlieb]

On Thu, Nov 30 2017, Marc Joliet wrote:

> Am Mittwoch, 29. November 2017, 22:29:59 CET schrieb allan gottlieb:
>> On Wed, Nov 29 2017, Alan McKinnon wrote:
> [...]
>> >> Both 6430 and 7450 have the following content in
>> >> /etc/portage/package.use/systemd-cron
>> >> 
>> >> # systemd-cron needs PYTHON_SINGLE_TARGET = 3.x.
>> >> sys-process/systemd-cron python_single_target_python3_4
> [...]
>
> Isn't this the problem?  PYTHON_TARGETS has switched to python3_5 but that's 
> in conflict with the above (or should be, IIUC).  Remove that or change it to 
> "python_single_target_python3_5" (I would remove it; according to my git log, 
> I removed a similar line in August when I noticed that the profiles already 
> default to Python 3.x in $PYTHON_SINGLE_TARGETS).
>
> I admit, though, that I am surprised that one machine can apparently still go 
> through with the upgrade.  Does it also have systemd-cron installed?  Or maybe 
> I'm forgetting or missing something...
>
> HTH

Bingo!

1. The 6430 does not have systemd-cron so was unaffected

2. I commented out the package.use line for systemd-cron in the 7450,
   which does use systemd-cron, and it seems willing to do the update
   world.  (The 6430 is a backup, I will do the update on it first.)

thank you very much.
allan